digitalcircuit has quit [Quit: Signing off from Quassel - see ya!]
digitalcircuit has joined #openwrt-devel
ecrn has quit [Remote host closed the connection]
Tapper has joined #openwrt-devel
ecrn has joined #openwrt-devel
<ecrn>
hi, I have a linksys MR9600 router, which is based on bcm4908 - from what I found, there is no openwrt support for it as of now, but there is for some other routers based on the same soc
<ecrn>
for example, netgear R8000P
<ecrn>
the radio is based on bcm43684
<ecrn>
is there any hope to run openwrt on it? I have UART connected and the modules loaded are https://nopaste.net/ANj915WdRY
<ecrn>
the vendor firmware image which I downloaded from their website seems to have similar layout to the supported routers on bcm4908
<PaulFertser>
ecrn: you can try running initramfs image and see what works and wht doesn't.
<ecrn>
PaulFertser: with openwrt kernel and basing on some device tree from other bcm4908 routers?
<PaulFertser>
ecrn: yes
rua has quit [Quit: Leaving.]
<ecrn>
the CFE bootloader seems to be somewhat modified: https://nopaste.net/YmbDZapZ9X - I managed to load a file to RAM with tftp, so probably can try it
ecrn has quit [Remote host closed the connection]
ecrn has joined #openwrt-devel
<Tusker>
hmm... looks like cfg80211 doesn't like -fcommon and refuses to load. Is there a way in an individual device to specify gcc level and needed kernel modules ?
<mangix>
Nope. Just target
<slh64>
ecrn: there is zero support for bcm43684 and I wouldn't expect that to change either
<ecrn>
slh64: ok, thank you
<ecrn>
so the router purchase was a really terrible decision to make: the vendor firmware not only expects one to use a smartphone app for setup (normal web interface is available only after clicking a hidden button on the served page - we had to call product support for that), but also you can't set even the tx power and channel, not to mention client modes for wifi, wds or more advanced bridging
<ecrn>
and the USB is only for storage devices, no modem support, even with rndis/cdc_ecm modems
rua has joined #openwrt-devel
<russell-->
ecrn: sounds like you should return it while there is still time
<mrkiko>
ecrn: router name / model?
<mrkiko>
ecrn: sorry, I did read.
<rsalvaterra>
ecrn: Return that crap while there's still time.
<rsalvaterra>
Oh, russell-- already said it. :)
<dhewg>
rmilecki: do my patches fix the issue on your end?
rua has quit [Quit: Leaving.]
pmelange has joined #openwrt-devel
rua has joined #openwrt-devel
ecrn has quit [Quit: Page closed]
dangole has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
rua has joined #openwrt-devel
<stintel>
aparcar[m]: yes
<stintel>
Tusker: I solved it with rearranging things in dts
Tapper has quit [Ping timeout: 480 seconds]
rmilecki has quit [Quit: Konversation terminated!]
Tapper has joined #openwrt-devel
Guest2049 is now known as ynezz
ynezz is now known as Guest2868
Guest2868 is now known as ynezz
<pmelange>
Hi, is there any change of getting a 21.02.1 release in the near future?
<pmelange>
jow: we are already at 6 weeks, so I guess that means soon. We (freifunk-berlin) are looking forward to the kernel version and most of all the recent change to the olsrd init script in openwrt-routing. Thanks for the info.
hitech95 has joined #openwrt-devel
<hitech95>
Hi, how can I specify a dependency of a kernel module? The module has been implemented on 5.3+ so I would like to show (in menuconfig) that only on 5.3+
Tapper has quit [Read error: No route to host]
Tapper has joined #openwrt-devel
<jow>
hitech95: DEPENDS := @LINUX_X_Y or @!LINUX_X_Y or @(LINUX_X_Y||LINUX_X_Z)
<jow>
to make it future proof it is usually best to use inverted depends, so depend on Linux not being one of the older supported versions
<jow>
e.g. DEPENDS := @!LINUX_4_14
<hitech95>
jow: so for 5.3+ i should do @(LINUX_5_4||LINUX_4_10), what is the oldest version of the kernel on openwrt? 4.14?
<hitech95>
Typo @(LINUX_5_4||LINUX_5_10)
<jow>
that will fail once linux 5.11 is added
<jow>
better to rule out supported older kernels
<jow>
you can look those up in include/kernel-version.mk
<jow>
master currently defines 5.4 and 5.10
<jow>
21.02 defines 4.4, 4.9. 4.14 and 5.4
<jow>
so you likely want @!(LINUX_4_4||LINUX_4_9||LINUX_4_14)
<hitech95>
jow, yea, went with that. I'll see is this patch will work.
<hitech95>
BTW I'm having an issue with developing on luci. (modal rendering) I'll have to ask you some infos about why :)
<jow>
hitech95: sure, feel free to pm me
pmelange has left #openwrt-devel [#openwrt-devel]
<hitech95>
jow, I'll provide the sources once I will cleanup them. But the issue I'm facing is with the network configuration modal. The body is always white whatever I try to do.
<hitech95>
I've tried to add a new tab called "status", in this way a virtual protocols (yes I also have patched the Protocol class) can show some additional info.
<hitech95>
(I'm on MAP-T so a lot of stuff is hidden in the UI, so i'm adding them: https://ibb.co/Jtgzwtp)
<hitech95>
I've created a Status tab in the network configuration modal.
<hitech95>
Then I've tried to write something in it, but the modal is always white even if a console.log() functions showed me that the "body render" was called. https://ibb.co/D4JTbvp
indy has quit []
minimal has joined #openwrt-devel
indy has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
<jow>
hitech95: yeah, best is if you can provide some code to look at
<jow>
probably simple to fix
jbowen has joined #openwrt-devel
Ansuel has joined #openwrt-devel
Slimey has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
fda has joined #openwrt-devel
robimarko has joined #openwrt-devel
<robimarko>
I saw that somebody was mentioning Unifi 6 LR here
<robimarko>
What is the HW inside of it?
<robimarko>
I am looking for something decent to run AX until the IPQ807x is stable enough
fda- has quit [Ping timeout: 480 seconds]
<Ansuel>
robimarko mediatek probably
<stintel>
robimarko: Ansuel: yes Unifi 6LR is mediatek
<stintel>
few things to note: opening the case means breaking the case, afaik, and the 2.4GHz radio is wifi4
<Ansuel>
wth only 5ghz is wifi ax o.O
<robimarko>
stintel: Ok, so its not for me then as I always mess with stuff
<Ansuel>
that doesn't make sense considering the improevemtn done by ax on 2.4... who design these device LOL
<robimarko>
stintel: Is it MT7622 at least?
<Habbie>
stintel, somebody recently suggested to me, 'for recent mobile phones', take some cloth and a 70C iron to weaken the glue
<stintel>
Ansuel: yeah that's a bit of a bummer :(
<stintel>
robimarko: it's the mediatek target. not ramips
<stintel>
or did you mean wifi?
<Ansuel>
Habbie: hot air gun and pray that it doesn't melt ?
<robimarko>
Ansuel: I assume they reused existing SoC-s or a cheap radio fo 2G
<Habbie>
Ansuel, well that's the beauty of using something with a thermostat, i guess
<robimarko>
stintel: MT7622 is the ARM SoC, so I suppose it uses that then
<Habbie>
Ansuel, i haven't tried any of these things myself
<stintel>
mt7622-wmac and mt7915e is the wifi
<robimarko>
stintel: Ok, so they just use the SoC built-in radio
<robimarko>
Honestly, not that impresive for 180 EUR
<Ansuel>
robimarko yes considering the ax9000 is 200€ now
<robimarko>
mt7915e seems really good, but somehow they always crap out on the 2G radio or SoC
<Ansuel>
stintel i mean about cpu load
<blocktrron>
Ansuel: U6-LR does not require SW offload to saturate the ethernet uplink
<blocktrron>
Even a U6-Lite can saturate the gigabit uplink using sw flow-offload
<stintel>
hmmm
<stintel>
I might have to redo this image ... at some point I threw iptables and everything related out of my dumbap builds
<blocktrron>
unless someone figures out how to load firmware on the aquantia PHY to enable N-Base-T, i would opt for the U6-Lite (or Cudy X6 / Tenbay if 2.4GHz 802.11ax is required)
<stintel>
blocktrron: it's the reason I bought the U6LR - at home I have NBaseT so I can test stuff
<robimarko>
Which AQR is it using?
<robimarko>
I assume one of the Gen4?
<blocktrron>
No, older one
<blocktrron>
AQR112C afair
<robimarko>
Ok, that is fine for 2.5G
<robimarko>
But the FW is a bit of an issue
<blocktrron>
I'm not sure if they have even wired it up to the SoC. I was not able to find it on the MDIO bus and Ubiquiti does not interact with it neither in their bootloader, nor withing Linux
<Ansuel>
o.O they have hardware that is actually not usable ?
<blocktrron>
The Ubiquiti product selection is a mess
<Ansuel>
prograde pricevy stuff so i assume they don't care
<Ansuel>
having extra stuff not working
<blocktrron>
Their AX gear was discontinued while they were selling off the discontinued products to their loyal fans thru early access
<Ansuel>
robimarko: btw i think no luck about testing if switch interrupt is connected to ipq806x... don't know if i tested it right... but by enabling every interrupt trigger for the switch no interrupt was detected.... i added to qca8k every free interrupt for 32 to 400... 0 with everything.... (could be that i did something wrong)?
<Ansuel>
it's sad considering how good it would work with interrupt...
<Ansuel>
stupid move IMHO
<robimarko>
Ansuel: I dont think that they connected the pin on most boards at all
<Ansuel>
I will do it myself !??!?!... what if they connected the pin to the gmac interrupt ?
<Ansuel>
still can't understand why that much interrupts are output by the gmac
pmelange has joined #openwrt-devel
<Ansuel>
i mean i think nss have his separate interrupt... so whta it's used for ?
<Ansuel>
dma ?
Tapper has quit [Quit: Tapper]
fda- has joined #openwrt-devel
cp-- has quit [Quit: Disappeared in a puff of smoke]
fda has quit [Ping timeout: 480 seconds]
cp- has joined #openwrt-devel
<stintel>
jow: can we drop the luci-app-firewall dep from luci? I'd like to test firewall4 but keep luci
<mangix>
robimarko: I bought the Linksys E7350 precisely because of 2.4ghz ax
<mangix>
Fastest wifi I've had.
<robimarko>
That one looks interesting because of dual MT7915-s
Dgrey has joined #openwrt-devel
<mangix>
Yep. It's amazingly stable compared to the other mt76 wifi chips. Probably because mediatek employees work on the driver this time around.
<mangix>
I'm still unable to get 160MHz working though...
<stintel>
works for me on the U6LR
<stintel>
jinxed it
<stintel>
Thu Oct 14 17:30:08 2021 daemon.notice hostapd: dfs_downgrade_bandwidth: no DFS channels left, waiting for NOP to finish
<stintel>
and bye bye 5GHz bssid
<stintel>
sigh
<mangix>
I get a different DFS error
<stintel>
this was right after radar detection
<mangix>
Speaking of DFS, 6ghz will not have it AFAIK
<Ansuel>
can't wait for wifi 7 that will just use 2.4 5 and 6 at the same time...
<Ansuel>
datarate will be a meme
<stintel>
can't wait for 6E APs to arrive in EU
<stintel>
because yes, 5GHz is basically a joke due to DFS
<Habbie>
my ISP is currently widely advertising the next evolution in wifi
<Ansuel>
not if you.... hack the reg LOL
<Habbie>
they call it
<Habbie>
'wifi 2.0
<Habbie>
'
<stintel>
lolwut
<Habbie>
it's so dumb
<mangix>
It's funny. I'm the only one around my area that uses channel 100
<mangix>
Everyone uses non DFS channels
<mangix>
Which kinda kills the point.
<Habbie>
the point is using that capacity as long as it's safe?
<stintel>
does the mt7915 in the U6Lite support 2.4GHz?
<stintel>
could do a U6LR with 5GHz 11ax and then a U6Lite with 2.4GHz 11ax if that's the case
<stintel>
and keep the other radios for legacy non-11ax clients
<stintel>
ok, somewhat expensive, but at least no QCA junk needed then
<mangix>
stintel: wifi says yes. That's quite surprising though
<mangix>
All other mt7622 devices do not.
<mangix>
Habbie: the point is more bandwidth that 2.4ghz. but there are only 2 non DFS channels
<Habbie>
oh only 2, wow
<mangix>
36 and 149
<lemmi>
i rarely have dfs events here. and they should be more firmware issues than anything else
<lemmi>
there is just no radar here operating at that frequency
<lemmi>
(at least to my knowledge)
<PaulFertser>
If mt7915 is dbdc why not all the vendors are using it for 2.4 GHz?
f00b4r0 has joined #openwrt-devel
<PaulFertser>
Probably only MT7915D supports it.
<Slimey>
a good SDR can tell you if you have things in the 5Ghz band
<Habbie>
f00b4r0, don't think i've ever seen a chunkeey in here
<f00b4r0>
k
<f00b4r0>
thx
<PaulFertser>
mangix: thank you! stintel see, you probably do not want 2x2.
<stintel>
PaulFertser: why not ?
<stintel>
for 2.4GHz I could care less
<PaulFertser>
stintel: but it's for 5 GHz too.
<stintel>
PaulFertser: I have a U6LR for 5GHz
<stintel>
I am considering the U6LR for 2.4GHz 11ax
<PaulFertser>
stintel: ah, I see now
<stintel>
ehr. U6Lite*
<stintel>
for 2.4
<stintel>
actually, I've already ordered one :P
<mangix>
Wonder when mt7921 units will arrive.
<stintel>
so it looks like when I boot with HE160 it doesn't work, previously I was running with HE80 then changed to HE160 and then I got 160MHz working
<Slimey>
heh 00000000: BADB100D
<stintel>
ah, HE160 working again, I had channel 100, changed that to auto and now it's working
<robimarko>
stintel: Isnt U6 Lite also AX only on 5G
<robimarko>
And for 2.4 they are simply using the SoC which is N only
<stintel>
I will know soon :P
<robimarko>
stintel: Its for sure just old SoC WLAN, as its advertised as 300Mbps 2x2 so N norm
<stintel>
either way, the U6 Lite can stay at my parents' place to replace the crashing ath10k junk, I'll take the U6LR home where I have NBaseT
<stintel>
so fingers crossed someone can figure out how to make it work at 2.5GbE
<robimarko>
stintel: Have you seen the U6 Pro?
<robimarko>
They have only 2 terrible FCC internal pictures so I have no idea about the HW but it looks extremely similar to the LR
<stintel>
have not
<robimarko>
Its actually a bit cheaper then the LR
jbowen has quit [Remote host closed the connection]
<Slimey>
i should reply that im not sure if my ethernet cables are oxygen free for that
fda- has joined #openwrt-devel
<mangix>
PaulFertser: that’s not the ubiquiti unit
jbowen has joined #openwrt-devel
<PaulFertser>
mangix: but it's from mt7915d, right? So if the ubnt unit has the same chip it should be the same.
<mangix>
No idea if it’s the same. Mine does 2.4ghz. I don’t think the u6lr one does.
<PaulFertser>
mangix: interesting, I saw stintel asking "does the mt7915 in the U6Lite support 2.4GHz?" and you answered "stintel: wifi says yes." so I assumed it's an established fact.
<fda->
so its aa bug in wsdd2 - caused by a muslc bump?
<mangix>
so strange that llu is used. time_t is signed.
<mangix>
fda-: guess so
<stintel>
s/caused/exposed/ ;)
<mangix>
stintel: it's just more proof that format functions in C are trash
<fda->
mangix: i will test, compile+flash takes some minutes
<stintel>
mangix: or that people don't know how to write code :)
<stintel>
that includes myself lol
<mangix>
stintel: no they're actually trash. C++ projects have mostly transitioned to fmtlib, which implements Python style format strings. Much easier to use.
Ansuel has joined #openwrt-devel
<Ansuel>
robimarko: ping ?
<fda->
damn, openwrt does not automatically applies patches if there is a pathes/ directory was created :\
nindoja has quit [Remote host closed the connection]
Acinonyx has quit [Ping timeout: 480 seconds]
bluew has joined #openwrt-devel
<mangix>
fda-: -O0 is not needed
<fda->
mangix: im now compiling without for another device (avm1200) to test
pmelange has left #openwrt-devel [#openwrt-devel]
<Tusker>
hmm... are there any examples of a pinmux for gpio-led ? ie, two GPIO that control one LED, and it has various on/off states to control colour ?
<Tusker>
at the moment, the off state of one colour is opposite of the other, so that it causes the LED to light in one colour
<fda->
mangix: wsdd2 works for avm1200/ipq40xx/generic too again with your patch!
<Ansuel_>
any idea what would cause a missing watchdog ?
<Ansuel_>
i just notice ipq8064 doesn't have a watchdog defined at all...
<fda->
me? i dont know about the watchdog
<Ansuel_>
and the driver is used with the wrong reg
<Ansuel_>
just asking to everyone
<mangix>
Ansuel_: no idea
fda has joined #openwrt-devel
fda- has quit [Ping timeout: 480 seconds]
<fda>
a new error message during boot: "E8450 : jail: can't read from parent" just after pppoe module load and before collectd network plugin loading
<fda>
maybe interesting for dangole
<Ansuel_>
wow we are starting to use jail '
<Ansuel_>
?
<mangix>
it got enabled by default
<fda>
i have no idea from which package it is :\
<fda>
with dnsmasq i had also jail-proclems and i had to add a direcotry manually to init script
Ycarus_ has joined #openwrt-devel
<dangole>
fda: in default installation it would be either dnsmasq, hostapd/wpa_supplicant or sysntpd which use any jailing by now. umdns and transmission are optional packages which make use of jail with seccomp.
<mangix>
dangole: btw I tested transmission with that patch. works. I accidentally let the debiab mips ISO finish downloading
<fda>
thx dangole, i will restart these. i have no umdns or transmission. dnsmasq uses unbound, sysntpd a local ntp
<dangole>
mangix: beautiful. i didn't believe we would ever get it to work with wolfssl...
<mangix>
the more confusing part is why options.h is an external header
<dangole>
wolfssl is just weird
<fda>
sysntpd does not write anything to syslog, dnsmasq no erors now on restart. how can i restart wifi?
<dangole>
fda: /etc/init.d/wpad restart
<mangix>
dangole: weird history too.
<dangole>
mangix: i know it was called cyassl earlier and we had a long history of carrying it around before switching to use it by default. looking at the code I'd prefer mbedtls, by magnitudes.
Ycarus has quit [Ping timeout: 480 seconds]
<mangix>
dangole: I do too. Looking at the wolfSSL code it looks like at some point it was forked from OpenSSL.
<fda>
thx, also no jail errors, but multiple "hostapd: nl80211: Failed to remove interface wlanX-X from bridge br-lan: No such device" and "hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied" im not sure if they are "normal"
<mangix>
dangole: hah. even their docs suck. they say to include version.h first and in other places options.h should be first.