<biboc>
Hi, I'm wondering why, on mesh80211s, we can't open (iw dev $MESH_IFACE station set $MAC_TO_UNBLOCK plink_action open) a client which is BLOCKED. The only way to do so is to restart the wifi to look for client again. How can we solve this?
<biboc>
And we set a RSSI limit in wifi configuration so we ensure that the connection between two clients is good, this is why some client are BLOCKED. The problem is, it stays BLOCKED until wifi restarts even if the RSSI gets lower than the limit value
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
danitool has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
srslypascal has quit [Ping timeout: 480 seconds]
srslypascal has joined #openwrt-devel
arnd_ has quit [Read error: Connection reset by peer]
Vaughn has quit [Read error: Connection reset by peer]
Vaughn has joined #openwrt-devel
arnd_ has joined #openwrt-devel
dvn has joined #openwrt-devel
robimarko has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
cbeznea1 has quit [Quit: Leaving.]
cbeznea has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
Tapper has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
<stintel>
interesting, u-boot docs for hifive unmatched instruct to use a GPT partition table on the SPI NOR
<stintel>
then again it's just a block device, so why not
<robimarko>
Seems like a bit of an overkill
mzvd has quit [Read error: Connection reset by peer]
<stintel>
dunno, seems more flexible than defining partition layout in dts
<robimarko>
That for sure
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
mzvd has quit [Read error: Connection reset by peer]
Tapper has quit [Ping timeout: 480 seconds]
mzvd has joined #openwrt-devel
<f00b4r0>
sounds completely overkill indeed. Not to mention GPT uses LBA (not sure how that'd play with mtd devices) and takes 'significant' space (tens of KB)
robimarko_ has joined #openwrt-devel
robimarko_ has quit [Quit: Leaving]
robimarko has quit [Ping timeout: 480 seconds]
mzvd has quit [Read error: Connection reset by peer]
robimarko has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has quit [Read error: Connection reset by peer]
<Ansuel>
next step would be understand how to merge leds support for switch...
Gaspare has joined #openwrt-devel
<Ansuel>
but i'm working on getting ipq8064 stuff merged
<rmilecki>
Ansuel: did you backport dyn partition to OpenWrt? can't see it
<Ansuel>
rmileki there is a pr open i still have to rework it
<Ansuel>
anyway why we still have this?
<Ansuel>
Makefile 'package/utils/busybox/Makefile' has a dependency on 'libpam', which does not exist
<rmilecki>
Ansuel: is that safe to push commit ("generic: backport mtd dynamic partition patch")?
<rmilecki>
(so I can start testing / using it while you sort out specific targets)
<Ansuel>
rmilecki yes it's safe but i wanted to push all in one go since we have a patch for cmdlinepart that does the same exact thing
<rmilecki>
Ansuel: ok, I'll try to stay patient for few extra days :)
<Ansuel>
mhh can't you just cherry pick the commit ?
<Ansuel>
on rebase it will be ignored
<rmilecki>
i can, i thought you don't want that
<rmilecki>
right
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
nemesis-ninux has joined #openwrt-devel
nemesis-ninux has quit []
nemesis-ninux has joined #openwrt-devel
<nemesis-ninux>
Hi there, I wanted to inquire about the 60 GHz support. Since it's mentioned in the wiki, I would like to make sure OpenWISP can at least generate a configuration which allows to use this feature (if anyone is using it), but apart from setting band to 60 it is not very clear if anything else is required? Is there any LuCi developer which could help me understand how LuCi generates a configuration for the 60 GHz band?
Tapper has quit [Ping timeout: 480 seconds]
mzvd has joined #openwrt-devel
<mrkiko>
nemesis-ninux: should you not get help in there in some time, try the ML
<PaulFertser>
nemesis-ninux: every now and then shibboleth joins the channel, ask them.
<mrkiko>
there was the TP-Link AD7200 supporting it, right=
mzvd has quit [Read error: Connection reset by peer]
<PaulFertser>
Yes
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
<nemesis-ninux>
Thanks for the info, TP-Link AD7200 supports 60 GHz and is supported by OpenWrt?
<nemesis-ninux>
it looks like it, nice to know, I added that device to my shopping list
Gaspare has quit [Quit: Gaspare]
Guest4448 has quit [Quit: Page closed]
<stintel>
I fail to decipher the adtran bsap-3040 u-boot code to abort autoboot :/
<Ansuel>
raf just proposed a patch upstream just for you :D
<rmilecki>
now I have "u-boot-env" that can be parsed by NVMEM driver
<rmilecki>
Ansuel: right ;) just sent 2 little patches for that
<rmilecki>
Ansuel: just wanted to let you know
<Ansuel>
ok i'm stupid anyway thx!
<rmilecki>
huh?
mzvd has quit [Read error: Connection reset by peer]
<Ansuel>
i limited that just to nvmem as i could only test that with nvmem related thing but it seems really good
<rmilecki>
blah, you got the hardest part done
<rmilecki>
i just polished it a bit
<Ansuel>
honestly the only part i didn't liked was the partition- suffix but i really wanted something in DT to differenciate these 2 kind of partition
<rmilecki>
Ansuel: well, that part is confusing a bit indeed
<Ansuel>
yaml are evil
<rmilecki>
i think i suggested partition-* as a simplification to something else... or maybe I don't remember that correctly?
<rmilecki>
it was months ago I tihnk
<rmilecki>
I sent some suggestion regarding nodes I believe
<Ansuel>
yep i changed the node pattern 4 times
<Ansuel>
you were the one suggesting that partition should also be referenced by the node name instead of making the label mandatory
<rmilecki>
i see, you suggested using names like "art-dynamic"
<Ansuel>
my crazy mind at times was to put everything in a separate partitions {} node ahahaha
<rmilecki>
well, i'd say it's common in DT
<rmilecki>
to have maaaany iterations in order to handle DT syntax the way Rob likes it ;)
<rmilecki>
that partition-* maybe doesn't seem perfectly clean
<rmilecki>
but hey, it's there, accepted, works
<rmilecki>
not the worst thing :)
<rmilecki>
and *accepted* is crucial here, you managed to get it upstream
<rmilecki>
ok, i'm taking a break, going to eat sth, ttyl
<Ansuel>
important part is that we have the feature... now i have to fix billion dts on openwrt ahahaha
<Ansuel>
have fun!
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
Misanthropos has quit [Ping timeout: 480 seconds]
Gaspare has joined #openwrt-devel
Tapper has joined #openwrt-devel
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
<hauke>
xdarklight: thanks
mzvd has quit [Read error: Connection reset by peer]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
ekathva has joined #openwrt-devel
ekathva has quit [Remote host closed the connection]
<stintel>
hmmm console goes silent after Loading Device Tree to 03fe6000, end 03fff353 ... OK
Ansuel has quit [Read error: Connection reset by peer]
<xdarklight>
stintel: try adding earlycon as boot argument. if the kernel is crashing early (before serial console is initialized but after earlycon is available) you might see some kernel crash output
<stintel>
same :(
nemesis-ninux has quit [Quit: Leaving.]
<xdarklight>
what SoC is this? do you know if the serial driver has earlycon support? if not: adding it should be simple
<stintel>
fsl t1042, powerpc
<xdarklight>
seems like the compatible string contains ns16550 -> that one has earlycon support
<mrkiko>
cmonroe: I am happy to see new firmware + mt76 fixes backported to openwrt 22.03. Great news.
<mrkiko>
nbd: thanks for the backporting :D
<stintel>
doesn't seem to be working
<stintel>
oh well, would have been too easy if this thing would just work ...
<stintel>
but I'm going to call it a day, long drive tomorrow etc
<cmonroe>
mrkiko: me too :) so far seems to be working quite well. the current mt76 in 22.03/master doesn't seem to have any noticeable issues on mt7615 or mt7915 for me right now.
<mrkiko>
cmonroe: agree; I will try to keep thedevice up and running for a month or so and see if it continues working but I think so. did you experience nay delay in in push notification receiving? Today was first time, butmay depend on different factors
<cmonroe>
mrkiko: i've not seen anything like that but will keep an eye out.
Misanthropos has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
danitool has joined #openwrt-devel
Tapper has joined #openwrt-devel
nemesis-ninux has joined #openwrt-devel
Ansuel has joined #openwrt-devel
philipp64 has quit [Quit: philipp64]
mzvd has joined #openwrt-devel
mzvd has quit [Read error: Connection reset by peer]
gladiac has quit [Quit: k thx bye]
<xdarklight>
hauke: the kernel selftests will require some patches to be compatible with OpenWrt (mainly because getopt parsing works different in musl and glibc). I'll send patches upstream once I actually got it working. for the OpenWrt side everything should be ready: https://github.com/xdarklight/openwrt-packages/commits/wip-kernel-selftests-net-forwarding-20220707 - I'll wait with the final PR for the package until 1) I was able to test it 2) the
<xdarklight>
selftest patches have been accepted upstream so I can backport them to OpenWrt
<xdarklight>
Ansuel: yes, Vladimir (upstream DSA maintainer) mentioned it. we (OpenWrt downstream) have some issues with the GSWIP DSA driver - he found some issues and provided selftests to reproduce them. now it's my turn to get these tests to work in OpenWrt (which I am still struggling with)
<Ansuel>
i know vlad pretty nice guy
<Ansuel>
configure: error: you should not run configure as root (set FORCE_UNSAFE_CONFIGURE=1 in environment to bypass this check)
<Ansuel>
soo the container run as root?
<Ansuel>
that is bad
xes has quit [Quit: bye..]
T-Bone has joined #openwrt-devel
f00b4r0 has quit [Remote host closed the connection]
<Ansuel>
mhhh i'm using buildbot/buildworker-3.4.1
<Ansuel>
that runs under root
<Ansuel>
can't be that our buildbot runs as root
<Ansuel>
am i missing something?
xes has joined #openwrt-devel
<Ansuel>
ok there is a way in github actions to pass options to the container now i need to understand what user buildbot use
<Ansuel>
user is buildbot
<Ansuel>
well aparcar will hate me but i'm too curious to test this
<aparcar[m]>
Huh?
<Ansuel>
OH NO RUN !!! (i'm trying your kernel-ci branch and i'm pushing stuff)
ptudor_ is now known as ptudor
<Ansuel>
well nope better test it on my repo...
mzvd has joined #openwrt-devel
mzvd has quit [Remote host closed the connection]
mzvd has joined #openwrt-devel
aiyion_ has quit [Remote host closed the connection]
aiyion_ has joined #openwrt-devel
<stintel>
hurricos: ping
Ansuel has quit [Read error: Connection reset by peer]
<stintel>
or anyone else familiar with why some PowerPC stuff needs DTB padding?
Gaspare has quit [Quit: Gaspare]
T-Bone has quit [Ping timeout: 480 seconds]
Gaspare has joined #openwrt-devel
<stintel>
yeah ok nvm, it seems I can "fix" the FDT_ERR_NOSPACE errors I get when following the WS-AP3825i initrd boot sequence on the bsap-3040, but in the end it's still stuck at Loading Device Tree to ...
Tapper1 has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
Ansuel has joined #openwrt-devel
<Ansuel>
aparcar: ping ?
<dwfreed>
aparcar[m]: ^^^
srslypascal has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
<aparcar[m]>
Uhm Pong?
<aparcar[m]>
Feel free to push things in there
<Ansuel>
aparcar: mhh not that... using buildbot container is problematic since it does assume root user so some magic are needed with chainging user in each run or openwrt will complain of building as root (using the container with buildbot user is also problematic as the directory usable is /master but github actions require to use a different directory)
<aparcar[m]>
it's to late to think about it but i'll put some thought on that tomorrow
<Ansuel>
nha was just to alert you of the concern of using buildbot... probably something has to be changed on the buildbot anyway will push a fixed yml
<Ansuel>
current solution is to change user with su