Hi...
No issues.
I am using Firefox (raspberypi 4) Bookworm SO. Forcing https-dns.
TP-Link Archer C7 v5
OpenWrt 24.10.0-rc7 r28417-daef29c75d / LuCI openwrt-24.10 branch 25.027.83426~170375e
So when the browser is set to "Use Secure DNS" and "Select DNS Provider" is set to "OS Default", the browser can't resolve any names. /etc/resolv.conf on my machine is set to the routers IP. nslookup works alright.
When I select Cloudflare or any provider, the browser starts to work. If I set "Use Secure DNS" off, the browser stops working too.
this only occurs with rc7, it works on 23.05.5
I have https-dns-proxy and adblock. Any pointers?
I actually always wondered how that would work on DSA. in the switch screen you could see both CPU ports and assign them to VLANs, similar to LAN and WAN.
Is the WAN hard wired to eth0 maybe?
It's from Home Assistant. I've OpenWrt connected with it using collectd mqtt plugin.
1 Like
I Have mqtt stats also from HA and I have only the absolute mem free, no % mem usage available. Those also show now problems.
The screenshot shows a config page for a swconfig based switch, so you're device does not run DSA.
it does not now, but it will once i upgrade to 24.10 (its the R7800)
On R7800 the lan ports have their conduits on eth1, the wan port has its conduit on eth0 (hardwired?). The wan port can be bridged with a bridge(-vlan) on one or more lan ports. So, create a bridge of the lan ports, optionally create one or more bridge-vlan on that bridge and use that bridge bridge(-vlan) as one of the list ports options as well as wan(.vlan) in another bridge.
An example that bridges a vlan on wan with a vlan the lan ports:
config device
option comment 'switch, conduit eth1'
option type 'bridge'
option name 'sw1'
option rpfilter 'strict'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
config bridge-vlan
option device 'sw1'
option vlan '9'
list ports 'lan1:u*'
list ports 'lan3:t'
config device
option type 'bridge'
option name 'br9'
list ports 'wan.9'
list ports 'sw1.9'
It works pretty well and an interface on such a bridge can nicely be used with a separate AP SSID. But whether such a setup is as it should be done, no idea. I
The Ubiquiti flash write-protect bug is back. Tested on Nanostation AC loco.
Edit: The bug seems to be in all 24.10 including rc1.
1 Like
Your hunch about "a bug in the whole IPQ8064" makes sense (at least to me). I have a Netgear EA7500v1 (IPQ8064) that had a problem after upgrading to 24.10.0-rc6 (dsa) from 23.05.5 (sw switch). The problem was the wan port and the lan ports were programmed with the same mac address and until I manually changed the wan port's mac address to a different address, I couldn't get on-line. I reverted back to 23.05.5 and will stay with it until the whole thing is clear.
1 Like
After removing default ct drivers to non ct drivers, kernel warning has gone.
Dear developers (not in a ironic way), maybe will be better use non ct drivers as default.
6 Likes
@hauke , Thanks for you and OpenWrt Team for a great efforts ..
I tested OpenWRT 24.10.0-rc7 but still WIFI issue is there..
looking head for OpenWRT team support and solution ... I'm sure it will be not difficult
Issue :
There is speeds limitations due to OpenWRT WIFI packages doesn't support devices that has Qualcomm WCN6856 Wi-Fi Driver
This issue reported previously
Maybe this is solution :
Widely reported 
I am pleased to see an Archer C6 upgraded with no issues and I know to have very limited understanding of sofware developing, but considering the known issue in OP and no commit that I can find about solving the issue with C6 5GHz Wifi, I don't understand how is it possible that it works fine. I have 4 C6 EU and they seem to have the same chipset as your C6 US. I was waiting to upgrade them. Did you apply any workaround after upgrade or it just went fine without additional modifications?
Worked fine without modification. I used attended sysupgrade.
As a precaution I created an image on 23.05.5 and a backup of the config. That way if the upgrade was unsuccessful and 5ghz didn't work, I could restore back to normal.
I'd recommend doing the same and testing it out and reporting back.
3 Likes
I have an BPI-R4 and installed RC7. I thought (because I saw commit messages in github) the eth1 and eth2 sfp-ports have been renamed in December (to sfp-lan and sfp-wan).
I have now flashed (formatted & written new rc7 img) my SD-card and booted OpenWrt and it states it now runs rc7. But my ports are still labeled confusingly "eth2" and "eth1" as before when I was running an older snapshot.
Did we roll-back that change in rc-builds?
1 Like
OK, it looks this change only made it into snapshot and was not picked for rc7 (or other rc builds)... perhaps it would be a good idea to include that commit into initial 24.10.0 build, otherwise all devices will get a port rename&confusion when they upgrade to 24.10.1 in the future, when this commit would presumably be added.
1 Like
I have just created the wiki page for this device. Instructions are easy and quick.
https://openwrt.org/toh/cudy/wr3000s_v1
EDIT : also notice that the WR3000H has receveid the Cudy signed version of OpenWrt, in order to install the official one. The WR3000H has a snapshot release, but has not made it to 24.10.0-rc7 yet. It will certainly be supported in a next minor version.
4 Likes
which version of 24.10 have switch to controll the vlan or works with igmp
I have migrated https://github.com/darkxst/erx-migration from 23 to 24.10.rc2 on my er-x.
Now I wanted to upgrade to rc7, but I get na error:
Fri Jan 31 17:29:21 CET 2025 upgrade: The device is supported, but this image is incompatible for sysupgrade based on the image version (1.1->2.0).
Fri Jan 31 17:29:21 CET 2025 upgrade: Partition table has been changed due to kernel size restrictions. Refer to the wiki page for instructions to migrate to the new layout: https://openwrt.org/toh/ubiquiti/edgerouter_x_er-x_ka
Image check failed.