Watch out though, the current snapshot is broken
Could you bit more specific and help openwrt devs to fix the issue?
I did, to some degree: A new dual 10G router based on Filogic 880 (Banana Pi BPi-R4) - #548 by buz - Hardware Questions and Recommendations - OpenWrt Forum
Sorry as this is my uplink router messing around with serial console to get details is not really an option 
but for upgrade you should do via console to get any error message that nails the problem a bit down
how should devs fix it when they have only a “upgrade did not work” description 
this is impossible and best way it will be not fixed soon
the more information they have the faster it can be solved. maybe the problem is related to latest increasing of root-partition? @dangowrt
I fully agree that a serial console log of the boot process would be a much more useful report but due to the way the router is attached to the fiber (and where the fiber comes into the apartment), that means unhooking everything (incl. not having internet during the debugging phase which kind of makes debugging tricky, not to mention the SO screaming at me). I should probably get a second R4 for these situations.
It’s however very easy to reproduce: just flash the current sdcard.img from firmware selector and the router never actually comes up. So I doubt it is related to the upgrade process…
why? just connect serial connection while router is active and connected? my r2 is connected to serial adapter all the time and when i work on it (kernel upgrade) i use an usb extender cable (my router hangs ~2m from floor) to connect to laptop no need to unplug anything
sounds like the sdcard-image itself is broken and does not boot from it - so not upgrade related because it does not come to this point
That’s point, I don’t have a long enough USB cable (or an extension to fix it) to do it in place 
Fair enough that I should get one.
sounds like the sdcard-image itself is broken and does not boot from it - so not upgrade related because it does not come to this point
That’s what I am trying to say: the build itself is broken, not the update process, as it also happens with a fresh image of that build on a fresh sdcard.
@buz are you using build r26556/26557?
You may have faced the rare situation that those builds are “broken”. (see: A new dual 10G router based on Filogic 880 (Banana Pi BPi-R4) - #548 by buz - Hardware Questions and Recommendations - OpenWrt Forum)
Update from running r26536 to r26557 via sysupgrade seems also not working.
EDIT: Problem still exists with build r26581
I tried to run r26557 yes.
By broken, do you mean something went wrong in the build (and should clean up next round) or a bad patch?
I can confirm that 26536 was smooth.
@buz by broken was ment that you can’t create a running (sysupdate and/or sdcard) image right now and that will be fixed (hopefully within the next builds).
If you want to ensure your observation about broken image generation will be heard/solved soon then please open a bug ticket for openwrt imagebuilder at github.
yup same issue I faced but sure the team will solve it …
I would like to ask some if someone can add these packages /or should be available on official OpenWrt / Snapshot
These packages : AT commands & Modem LTE/5G manager
The OpenWrt looks like a weak system for controlling 5G modems m.2 …maybe I’m wrong or right
Can’t managed to get the 6Ghz running, it always goes back in “disabled mode”
Edit: got it working under openwrt. Somehow you can’t use WPA2 PSK (TKIP, CCMP) You have to use WPA3 SAE (CCMP), otherwise radio doesn’t start
Yes, from a short Google search it looks like wpa3 is mandatory for 6GHz radios.
On new build (snapshot) via https://firmware-selector.openwrt.org/ the radio 2 (wifi7 6Ghz) is broken since about a week. It was working fine on previous build but those build doesn’t fonctionne well anymore as the opkg repos have been deleted and those build only support opkg… Sadly I updated and couldn’t rollback to a previous build.
I flashed my r4 yesterday with the current snapshot (used the firmware selector, tapped customized and added luci and iperf3 as well) and all 3 radios work for me, even 6g (with Macbook and iPhone as a client).
Only tweak I had to do: You need to set the wifi password encryption method to WPA3 - at least on the 6G band. Also I had to make sure the bandwidth was inside the allowed range for my country (eg in Switzerland 320 MHz as bandwidth did not work. Set it to 160 MHz and I could connect)
1 Like
That’s a great insight!
1 Like
Hello everyone. It looks like I got a problem instead of stability with 24.10.0 —very low speed on incoming connections in my gigabit home network. Meanwhile, outgoing connections are fine. Does anyone else have this issue?
From the access point to BPI-R4: root@AX6000_AP_ZAL:~# iperf3 -c 192.168.100.1
Connecting to host 192.168.100.1, port 5201
[ 5] local 192.168.100.8 port 59410 connected to 192.168.100.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 2.25 MBytes 18.9 Mbits/sec 0 204 KBytes
[ 5] 1.00-2.00 sec 1.62 MBytes 13.6 Mbits/sec 0 264 KBytes
[ 5] 2.00-3.00 sec 1.25 MBytes 10.5 Mbits/sec 0 315 KBytes
[ 5] 3.00-4.00 sec 1.62 MBytes 13.6 Mbits/sec 0 375 KBytes
[ 5] 4.00-5.00 sec 896 KBytes 7.34 Mbits/sec 0 437 KBytes
[ 5] 5.00-6.00 sec 896 KBytes 7.34 Mbits/sec 0 475 KBytes
[ 5] 6.00-7.00 sec 2.12 MBytes 17.8 Mbits/sec 0 518 KBytes
[ 5] 7.00-8.00 sec 1.12 MBytes 9.44 Mbits/sec 0 537 KBytes
[ 5] 8.00-9.00 sec 1.12 MBytes 9.44 Mbits/sec 0 537 KBytes
[ 5] 9.00-10.00 sec 1.12 MBytes 9.44 Mbits/sec 0 537 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 14.0 MBytes 11.7 Mbits/sec 0 sender
[ 5] 0.00-10.31 sec 11.6 MBytes 9.46 Mbits/sec receiver
From BPI-R4 to the access point:
root@Pi-R4:~# iperf3 -c 192.168.100.8
Connecting to host 192.168.100.8, port 5201
[ 5] local 192.168.100.1 port 47520 connected to 192.168.100.8 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 116 MBytes 969 Mbits/sec 0 635 KBytes
[ 5] 1.00-2.00 sec 112 MBytes 937 Mbits/sec 0 667 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 938 Mbits/sec 0 667 KBytes
[ 5] 3.00-4.00 sec 113 MBytes 945 Mbits/sec 0 704 KBytes
[ 5] 4.00-5.00 sec 113 MBytes 948 Mbits/sec 0 704 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 937 Mbits/sec 0 704 KBytes
[ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec 0 740 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 943 Mbits/sec 0 740 KBytes
[ 5] 8.00-9.00 sec 113 MBytes 946 Mbits/sec 0 776 KBytes
[ 5] 9.00-10.00 sec 112 MBytes 941 Mbits/sec 0 814 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.10 GBytes 944 Mbits/sec 0 sender
[ 5] 0.00-10.01 sec 1.10 GBytes 941 Mbits/sec receiver
Looks like I figured out this issue.
So, here’s the situation:
- LAN1 is connected to an access point (ASUS TUF AX6000)
- LAN2 is connected to an access point (ASUS TUF AX6000)
- LAN3 is connected to a PC
So, when the PC is turned off, LAN3 switches to 10Mbits mode, and (attention!) incoming connections to LAN1 and LAN2 also implicitly switch to this mode, even though ethtool shows 1Gbits Full-Duplex. As soon as I turn on the PC, everything works at full speed again.
Sounds a bit like these. Perhaps you could continue in one of these, or open a new topic…