Thanks for replying to my question. I tried WDS before with 23.05, and iirc the performance was good. But one (or both) of my routers would freeze sporadically with DAWN running in the background. Will try and see if 24.10 + WDS + DAWN will coexist happily. Thanks again.
Hmmm one more thing... I now have VLAN up and running over the 802.11s link (by following this tutorial https://www.youtube.com/watch?v=WIKwOPwtTJU). But I am not sure if VLAN-over-wifi is supported with WDS.
Yes, WDS does support VLAN-over-WiFi. WDS is basically a transparent VLAN-unaware Ethernet bridge. The only advantage of 802.11s is that it allows dynamic topology changes, ie. AP/STA roles are not assigned.
For whatever it's worth, I've used three of these devices all linked by WDS on 5GHz to offer main and guest WiFi networks with 802.11r (I experimented with the other extensions but they gave no discernible benefit) on both 2.4GHz and 5GHz for many years now and it's been rock solid. I use VXLANs to pass e.g. the 2.4GHz data over the 5GHz link. Works really well.
I'm now curious what the difference between VXLAN and VLAN-over-WiFi might be.
Just to report back - tried WDS, it didn't play well with DAWN at least in my setup (it brings down the entire wireless network for a few seconds every couple of minutes). But I have found DAWN to be the only way to successfully enable active steering to the best AP. Decided to retain DAWN, and set the 802.11s to "no encryption". This magically gives me back the normal bandwidth between the mesh nodes (~300mbps), so except for the obvious security concern, my problem is now solved. I plan on adding wireguard and shove the underlying mesh link to its own firewall zone to address the security issue. But for now everything works well once again, VLAN + performance + active steering wise.
I think this is still broken on 25.12.
On 24.10.4 and 24.10.5 I was getting 400/500 when my MX4300 was getting 700-800/700-800.
On 25.12 I’m getting 500/800 when my MX4300 is still getting 700-800/700-800, so it seems AX is still broken for TX still. All tests are on 1200/1200 PHY.
Just wondering, is it safe to use attended sysupgrade from 24.10 to 25.12?
Cheers.
I used owut instead of Attended Sysupgrade that is almost basically the same in the end (create a custom build with the installed packages in the ASU Server) and it worked fine.
I’ve been upgrading from 24.10.5 to all the RC releases of 25.12 and they have worked fine for me.
So yes, it’s safe. We don’t need installers or anything else.
hello everyone.
i may have bricked my router.
i make the customized build for my rt3200 with these packages
uci-app-https-dns-proxy https-dns-proxy wireguard-tools luci-app-sqm block-mount e2fsprogs kmod-usb-storage-uas kmod-usb3 luci-app-hd-idle kmod-fs-exfat luci-app-ksmbd unbound-daemon
and also with 1st boot script
uci set system.@system[0].hostname='macbook'
uci set system.@system[0].timezone='AST-3'
uci set system.@system[0].zonename='Asia/Riyadh'
uci delete system.ntp.server
uci add_list system.ntp.server='time.google.com'
uci set system.ntp.enable_server='1'
uci set system.ntp.use_dhcp='0'
uci set wireless.default_radio0.disabled='0'
uci set wireless.default_radio0.ssid='Bee'
uci set wireless.default_radio0.encryption='psk2'
uci set wireless.default_radio0.key=''
uci set wireless.default_radio1.disabled='0'
uci set wireless.default_radio1.ssid='Bee'
uci set wireless.default_radio1.encryption='psk2'
uci set wireless.default_radio1.key=''
uci set network.lan.ipaddr='10.0.1.1'
uci commit system
uci commit wireless
uci commit network
/etc/init.d/system restart
/etc/init.d/network restart
exit 0
now my router is still booting but not assigning any ipv4 to my laptop therefore i cant access luci.
even reset from button doesnt help.
anyone can guide me how to get it back working?
OpenWRT 25.12 now uses CIDR notation. So, manually assign an IP to your computer with the 10.0.1.1 as gateway and it should let you access Luci ot SSH; and now that command should be:
uci set network.lan.ipaddr='10.0.1.1/24'
When you can finally access Luci or SSH, modify your /etc/config network to add the netmask in the ipaddr field.
the main problem is that i cant access luci and ssh..how i can do it from with ssh?
Setting a manual IP from your computer still doesn’t allow you to log in to Luci or to SSH??? If so, that’s a bigger issue. The you might need to use the serial cable and reflash a vanilla sysupgrade (without additional packages or custom init script).
EDIT: scratch that! You can enter recovery mode in this router by pressing and holding the reset button and then powering on the device. It will be in initramfs mode and you can flash the vanilla sysupgrade there. It will be accessible at 192.168.1.1.
EDIT 2: you need to press and hold and power the device and release the Reset button when the led turns orange to enter the Recovery environment at 192.168.1.1.
thank you so much recovery mode solved my problem ![]()
Is it also true for the configuration file like /etc/config/network?
I think it was like
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
So we will need to change it to
option ipaddr '192.168.1.1/24'
? I thought it is supposed to be converted automatically if it is no longer backward compatible.
Yes and no.
You can leave the 2 line config (ippaddr and netmask) and it’ll work fine. In fact, that’s what I have on 25.12 on both my RT3200s. But @Aisfkhan tried to set up a different default IP for the router and didn’t specify the netmask, so it was softbricked because Luci/SSH couldn’t be accessed.
If you flash openwrt 25.12 without keeping configs, the default in /etc/config/network should be:
list ipaddr ‘192.168.1.1/24‘
But the old method still works:
option ipaddr ‘192.168.1.1‘
option netmask ‘255.255.255.0‘
So, to have a different IP for LAN at first boot, the correct way should be to add the CIDR notation in a single line or explicitly add a second line specifying the netmask in the firstboot script.
For example:
uci set network.lan.ipaddr='192.168.10.2/24'
or
uci set network.lan.ipaddr='192.168.10.2'
uci set network.lan.netmask='255.255.255.0'
Both ways should work. I explicitly tested the first one on a WiFi extender that I have in case of emergency. It boots properly at 192.168.10.2
Cheers!
weirdly, my client gets 480 down / 930up on 1200/1200 PHY on my E8450 on 5ghz on 25.12.1
I think the TX is still broken at the very least
just reposting here as well since github is not the official place for openwrt discussion
My two RT3200s might be oddballs because I don’t experience speed decrease in AX on both my main router and dumb AP.
I’ve tested iPerf3 bewteen my laptop (Qualcomm FastConnect 6900) as server connected to my main router and my dumb AP as client and I still get around 900ish Mbps on both download and upload.
I also tested a public iPerf3 server and get similar speeds.
However, on regular speed test sites, I usually get downloads to around 600 to 700Mbps, not only on 25.12.1, but like forever. I’ve never reached 900 or similar on a speedtest site. Uploads are unaffected, I always get around 900Mbps.
For example:
C:\Users\crodr>iperf3 -c spd-uswb.hostkey.com -p 5201-5209 -R
Connecting to host spd-uswb.hostkey.com, port 5201
Reverse mode, remote host spd-uswb.hostkey.com is sending
[ 5] local 192.168.1.226 port 51852 connected to 139.60.160.88 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.01 sec 45.0 MBytes 374 Mbits/sec
[ 5] 1.01-2.01 sec 106 MBytes 895 Mbits/sec
[ 5] 2.01-3.01 sec 109 MBytes 912 Mbits/sec
[ 5] 3.01-4.01 sec 112 MBytes 942 Mbits/sec
[ 5] 4.01-5.01 sec 105 MBytes 883 Mbits/sec
[ 5] 5.01-6.01 sec 112 MBytes 943 Mbits/sec
[ 5] 6.01-7.01 sec 112 MBytes 941 Mbits/sec
[ 5] 7.01-8.01 sec 113 MBytes 944 Mbits/sec
[ 5] 8.01-9.01 sec 114 MBytes 949 Mbits/sec
[ 5] 9.01-10.02 sec 76.5 MBytes 641 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.09 sec 1017 MBytes 846 Mbits/sec 1 sender
[ 5] 0.00-10.02 sec 1005 MBytes 842 Mbits/sec receiver
iperf Done.
Hello all,
I recently upgraded my e8450 router to version 25.12 from 24.10. everything is working well except the 5g wifi. Where I need to reboot the router every 3 or 5 days. Since it will completely stop working.
On the previous version it was working just fine for months.
Is this a known issue on the latest version?
What especific version of 25.12 did you install? There was an issue with some Mediatek chipsets on 25.12.1 that was fixed on the current 25.12.2 version.
I haven’t faced any issues on any of the 25.12 releases, for that matter. Maybe a bad wifi channel/width/encryption combination?
I'm using 25.12.2. also I'm using WPA entreprise with a radius server. But these are the exact settings that I was using on version 24.10 and were working fine.
