<nbd>
dhewg: thanks for confirming. yesterday i updated the fix commit for the mesh fast xmit code in my staging tree
<nbd>
can you please test that?
<nbd>
i found and fixed some more bugs in the code
<dhewg>
ok, so back to HEAD + your staging
<dhewg>
will do, is that a general issue or does it make sense that this is somehow related to wan reconnects/ip changes
<nbd>
i'm still not sure what exactly triggers it
<nbd>
so i just keep reviewing the code to look for discrepancies between mesh fast xmit path handling and regular mesh path handling
<dhewg>
yeah, it's a bit confusing, it may be some combination, the wan ip change might be a red herring, it may be time related with expired/stale arp/cache entries, but I can only guess
<dhewg>
I can't reproduce with a forced pppoe reconnect at least
Tapper has joined #openwrt-devel
rua has quit [Remote host closed the connection]
gladiac has quit [Quit: k thx bye]
<nbd>
dhewg: do you have any devices that connect switch between different nodes somehow (e.g. roaming)?
<dhewg>
no roaming, but notebook might pick up one of 2g/5g/6g, whatever it sees first
<dhewg>
the ipq router has quite some nets though, 3*2g, 2*5g (one beeing the mesh), 1*6g
<dhewg>
one of the 2g is a ap/wds one, because one older ath9k device doesn't support mesh
<dhewg>
and then multiple wireguard connections and a dsl pppoe
<dhewg>
and the mt mesh device has multiple wired clients, as does the wds one
<dhewg>
so not exactly easy to find out what exactly triggers this
<stintel>
ath9k device not supporting mesh? I would think all ath9k devices support mesh because there is no firmware that can get in the way
<dhewg>
hm, I may confuse it? Maybe I didn't want to setup yet another wifi net for 2g mesh and switched 2g ap to 2g wds?
<stintel>
(I have never used mesh, as I don't believe in it, but I would be really surprised if you have an ath9k device that doesn't support it)
<dhewg>
okay, so let's assume I chose wds to avoid adding another net
<dhewg>
;)
<dhewg>
and I basically use mesh to "bridge rooms", wired is unfortunately not an option
<stintel>
yeah, I get why people use mesh, but for me it's the other way around. not wired is not an option
<stintel>
my wifi works well because it's wired
<stintel>
:P
<dhewg>
hehe :P
<dhewg>
but then there's the WAF
<dhewg>
which plays a role here too
<stintel>
I would actually consider mesh now that there's 6G
<stintel>
5G between mesh nodes and 6G for clients
spyrral has joined #openwrt-devel
rua has joined #openwrt-devel
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
shoragan has quit [Quit: quit]
shoragan has joined #openwrt-devel
T-Bone has joined #openwrt-devel
f00b4r0 has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
f00b4r0 has joined #openwrt-devel
T-Bone has quit [Ping timeout: 480 seconds]
rua has quit [Remote host closed the connection]
danitool has joined #openwrt-devel
rua has joined #openwrt-devel
rua has quit [Quit: Leaving.]
radian has joined #openwrt-devel
<radian>
hi, is it possible to get a wiki account?
<radian>
hmm, will register a forum account, then see
djfe has joined #openwrt-devel
<djfe>
how is dsa supposed to be done for 1-port devices? I have to recover two devices now, because swport5 wasn't the right port-choice, or so it seems ^^
<djfe>
do I have to test all ports one by one and build up to 5 images?
<djfe>
or can I build an image for ipq40xx and set all 5 swports to okay, install, boot and then see which one of them works?
<tmn505>
djfe: basically yes, unless You know which port was it. I think phy-tools could be used to check which port was connected also wasn't it visible in kernel log which port was used on old swconfig? Anyway, don't build five images, simply enable all ports and see which gets connected.
djfe has quit [Ping timeout: 480 seconds]
djfe has joined #openwrt-devel
<djfe>
tmn505: thx for your answer :)
<djfe>
I still need a bouncer, but I won't miss any messages thx to irc log
<djfe>
I'll report back, when I know more. Your answer was very helpful
djfe has left #openwrt-devel [#openwrt-devel]
djfe has joined #openwrt-devel
<radian>
if a soc has two different processors, how should I list it in a table that is asking for cpu mhz? linux can be booted on either processor
<radian>
should I only list the ARM core?
<djfe>
You could ask the same for big.Little setups which are getting more common actually and I'm wondering myself
<djfe>
though for those you'd probably list the higher frequencies of the little cores
<radian>
well, I'm just going to list them both and specify the core count
<hauke>
radian: which device do you have?
<radian>
hauke: this is for bcm33xx
<hauke>
probably listing the CPU core you run OpenWrt on is fine
<hauke>
bcm33xx is a SoC family with multiple different SoCs
<radian>
I don't get why'd they let OEMs build bootloaders with no image validation enabled, though
<radian>
well, actually, no, they'd be building it, so ????
<radian>
*with secboot on
spyrral has joined #openwrt-devel
Rincewind_ has joined #openwrt-devel
Ryncewynd has quit [Read error: Connection reset by peer]
<Znevna>
hello
<djfe>
up to speculation. Did some boards get shipped with secure boot disabled?
<radian>
no, I read through the cmboot code
<radian>
if SECURE_BOOT is defined, it will only adjust an offset to compensate for the public key and stuff
<djfe>
Maybe some devs don't or didn't have any workflow for building with validation during development. Developers were lazy in the past. The boards are older, right?
<radian>
yeah, they'd be from 2009 or so
<radian>
I'm pretty sure this would apply to newer versions of that bootloader, though
<radian>
I think for 3390 they switched to bolt, not sure
<radian>
florian would know, but he's under an NDA
<radian>
the binary blobs for the ethernet drivers, anyway, is just creating a "virtual" link between ecos
<Rincewind_>
latest snapshot (and previous) keep giving me irq 23: nobody cared (try booting with the "irqpoll" option) and shuts down radio on Archer C7 V2. Can I fix something or go back top stable ?
Ryncewynd has joined #openwrt-devel
Rincewind_ has quit [Remote host closed the connection]
<radian>
with regards to bcm63xx, there is a whole new series of chips now
<radian>
bcm67xx
<hauke>
djfe: I am mostly ignoring the notifiations when I am getting mentioned on github
<radian>
hmm, no dsl core, I see
<radian>
part of what confuses me, is what to do when adding in a new target where every other soc is mips
<radian>
err, maybe I mean *device
<radian>
I think it'd need a new target, no? maybe something similar to bmips
djfe has quit [Ping timeout: 480 seconds]
Ryncewynd has quit [Quit: Leaving]
Lynx- has joined #openwrt-devel
Tapper has quit [Read error: Connection reset by peer]
Tapper has joined #openwrt-devel
djfe has joined #openwrt-devel
<djfe>
hauke: I see, is it possible then to help with moderation of issues on GitHub? I commented on many issues that have been fixed.
<djfe>
It would be nice reducing the number of open issues.
Tapper has quit [Read error: Connection reset by peer]
Tapper has joined #openwrt-devel
radian has joined #openwrt-devel
<aparcar[m]>
hauke: looks wrong to me
<aparcar[m]>
Master branch is there
Lynx- has quit [Quit: Going offline, see ya! (www.adiirc.com)]
spyrral has joined #openwrt-devel
<hauke>
aparcar[m]: it looks strange, I do not know what it did
<neoraider>
The log looks like the branches on the Github mirror had weird names before (with an origin/ prefix), and the mirror action has replaced them, so now the mirror actually matches the git.openwrt.org repo
Ryncewynd has joined #openwrt-devel
Ryncewynd has quit [Quit: Leaving]
fakuivan_ has joined #openwrt-devel
aiyion_ has joined #openwrt-devel
aiyion has quit [Remote host closed the connection]
fakuivan has quit [Remote host closed the connection]
aiyion_ has quit [Remote host closed the connection]
aiyion_ has joined #openwrt-devel
fakuivan has joined #openwrt-devel
fakuivan_ has quit [Remote host closed the connection]
cmonroe has quit [Ping timeout: 480 seconds]
cmonroe has joined #openwrt-devel
cmonroe has quit [Ping timeout: 480 seconds]
cmonroe has joined #openwrt-devel
cmonroe has quit [Ping timeout: 480 seconds]
cmonroe has joined #openwrt-devel
cmonroe has quit [Ping timeout: 480 seconds]
aiyion_ has quit [Remote host closed the connection]