<djfe>
has anyone seen the following errors on any TP-Link/Mercusys devices, yet? (TP-Link safeloader)
<djfe>
[NM_Debug](nm_getSoftVer) 01008: soft version ▒ ret 12
<djfe>
<djfe>
[NM_Error](nm_getSoftVer) 01012: failed to read soft version from flash!
<djfe>
[NM_Error](nm_upgradeFwupFile) 01510: pre get no soft version failed!
<djfe>
Flashing Mercusys Firmware for the MR70X v1 to recover the device doesn't work either and there is no special firmware on their homepage for v1.20
<djfe>
[NM_Error](nm_tpFirmwareCheck) 01419: The file's length is bad(buf:2477726 2 fileLen24777262)
<djfe>
different error though
lemoer has joined #openwrt-devel
n3ph has joined #openwrt-devel
lemoer has quit [Ping timeout: 480 seconds]
lemoer has joined #openwrt-devel
lemoer has quit [Ping timeout: 480 seconds]
lemoer has joined #openwrt-devel
danitool has joined #openwrt-devel
lemoer has quit [Ping timeout: 480 seconds]
lemoer has joined #openwrt-devel
n3ph_ has joined #openwrt-devel
n3ph has quit [Ping timeout: 480 seconds]
lemoer has quit [Ping timeout: 480 seconds]
gromero has joined #openwrt-devel
gromero has quit []
gromero has joined #openwrt-devel
lemoer has joined #openwrt-devel
valku has joined #openwrt-devel
lemoer has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
valku has quit [Quit: valku]
valku has joined #openwrt-devel
goliath has joined #openwrt-devel
<djfe>
interesting: I booted the Mercusys MR70X as an initramfs from RAM and flashed a sysupgrade
<djfe>
afterwards the bootloader complains
<djfe>
NM_Error 00332: factory boot check integer flag is not 1.
<djfe>
and then starts the recovery :/
<djfe>
does anyone know how to set this flag to 1 from either the uboot console or from an initramfs?
<djfe>
this is a tp-link safeloader design and very similar to the TP-Link Archer AX23
* f00b4r0
wonders if the MT7531 switch has a (low) limit to the number of cached arp entries.
<f00b4r0>
I've raised gc_thresh1 to 512 and it seems wifi clients sometimes do not "seeing" DHCP replies, in a scenario where the reply goes through one MT7531 onboard switch
minimal has joined #openwrt-devel
nixuser has quit [Read error: Connection reset by peer]
nixuser has joined #openwrt-devel
rockbox has joined #openwrt-devel
n3ph_ has quit [Quit: WeeChat 4.5.2]
n3ph has joined #openwrt-devel
cmonroe has joined #openwrt-devel
n3ph has quit [Ping timeout: 480 seconds]
dermoth has quit [Remote host closed the connection]
n3ph has joined #openwrt-devel
n3ph has quit [Ping timeout: 480 seconds]
n3ph has joined #openwrt-devel
<enyc>
I'm getting some IPv6 routing sillyness bug/regression with 24.10.1 (image built OK, not yet properly released I know!) over 24.10.0 where it works consistently fine on same config
<enyc>
Somehow, this EA8300 with 24.10.1 can ping6 the static configure upstream gateway fine, but gives 'unreachable' error trying to actually *use* it for outgoing -or- forwarded traffig
<enyc>
# ping6 2001:8b0:0:81::51bb:51bb
<enyc>
PING 2001:8b0:0:81::51bb:51bb (2001:8b0:0:81::51bb:51bb): 56 data bytes
<enyc>
ping6: sendto: Network unreachable
<enyc>
default via 2001:8b0:c1::1 dev br-wan proto static metric 1024 pref medium
<enyc>
gateway working for other devices on that outer netork etc
<Habbie>
is that 'default' output from ip r, or ip r get?
Lynx- has joined #openwrt-devel
<enyc>
Habbie: ip -6 ro
<Habbie>
can you try ip -6 ro get 2001:8b0:0:81::51bb:51bb
<enyc>
will do in a moment; however I ip -6 ro add 2000::/3 via 2001:8b0:c1::1 dev br-wan as hacky workaround (successful), can delete that and do the route get
<Habbie>
do the get before and after you delete it :)
rockbox has quit [Ping timeout: 480 seconds]
<enyc>
Habbie: root@blue:~# ip -6 ro get 2001:8b0:0:81::51bb:51bb
<enyc>
2001:8b0:0:81::51bb:51bb from :: via 2001:8b0:c1::1 dev br-wan src 2001:8b0:c1::190 metric 1024 pref medium
<enyc>
root@blue:~# ip -6 ro del 2000::/3 via 2001:8b0:c1::1 dev br-wan
<enyc>
root@blue:~# ip -6 ro get 2001:8b0:0:81::51bb:51bb
<enyc>
2001:8b0:0:81::51bb:51bb from :: via 2001:8b0:c1::1 dev br-wan proto static src 2001:8b0:c1::190 metric 1024 pref medium
<enyc>
should pastebin hrrm anyhow
<enyc>
ping6 2001:8b0:0:81::51bb:51bb
<enyc>
PING 2001:8b0:0:81::51bb:51bb (2001:8b0:0:81::51bb:51bb): 56 data bytes
<enyc>
ping6: sendto: Network unreachable
<Habbie>
except for 'proto static' that seems identical?
<enyc>
To *me* this is some regression between 24.10.0 and 24.10.1 in my somewhat-unusial config
<Habbie>
this is real 'ip' btw? not the busybox version?
<enyc>
ip-full - 6.11.0-r1
<Habbie>
ok
<enyc>
Habbie: just thought I'd bring it up here quickly as might be important
<Habbie>
ack
<enyc>
Habbie: anything else I can do to debug further ? I'm using routed traffic e.g. talking to you now via upstream 24.10.1 fine, honouring ipv6 routing.
<enyc>
Habbie: but this particular EA8300 which has wan ethernet interface changed to a "br-wan" (with a wifi on the wan-side of that downstream router, etc) is now struggling, IPv6 fails as above, but only in 24.10.1
<enyc>
Habbie: I'm going to check it isn't an mwan3 package interference
rockbox has joined #openwrt-devel
<enyc>
OH AIRGH it proabbly is
<enyc>
Habbie: I haven't submitted a PR, I really need mwan3 so it doesn't interefere ith IPv6 by default
<Habbie>
ah
<enyc>
** sorry all **
<enyc>
Habbie: default behaviour should have "no" on all interefaces and default behaviour to use "default" routing table not "unreachable" etc
Lynx- has quit [Ping timeout: 480 seconds]
<enyc>
else having the package in your list breaks other config, just like this *vmmgh*
<enyc>
SOryr all, false alarm I think.
wvdakker has quit [Quit: Ping timeout (120 seconds)]