Cudy M3000 2.5G no link

Hi there,
I'm currently using a AVM Fritz3000 AP with openwrt and wanted to upgrade to a (somewhat) newer AP that was recommended by a colleague: Cudy M3000

I've installed the openwrt kernel 24.10 and wanted to use the 2.5G (WAN) Port as the uplink.

I've tried almost everything:
added wan to default lan bridge, create new standalone bridge (added lan firewall zone) etc. but no matter what I do I get no link with the 2.5G Port.

I've also upgraded to 25.12-rc2 and just (tried) to go to the snapshot kernel version. Both with no luck, on the snapshot version I get an IP from the LAN port but can't access the webinterface. SSH and Ping works fine.

I also saw some "PHY Generic" in the Kernel log when I was on 25.12-rc2 but can't post the full log as I'm currently unable to access the AP.

Question: Has anyone a Cudy M3000 and uses the WAN (2.5G) Port as a LAN Uplink?

PS: I saw the recent Thread about Hardware changes but I'm in the EU and got a EU Serial Number which looks like it's different.

1 Like

Newer M3000 v2s apparently have a different 2.5Gbit PHY chip than the earlier v2 units (which work fine with the v1 images as is). See issue 21051 which has a comment describing a way to identify whether your device is affected - yes this issue was closed, but as a side effect of another device being fixed; some additional changes to rectify the problem are being looked at in this pull request.

Good morning everyone,
I'm having the same problem with the WAN port (red).
As for the 1GBps LAN port (white), there are no problems.
It's not a problem for me since I use it as a Wi-Fi repeater (connected to another AP via Wi-Fi).
We're waiting for the fix for the 2.5 WAN port issue to be made...

I did some more testing but nothing changed. Kernel still labels labels the 2.5G

[  221.969065] mtk_soc_eth 15100000.ethernet eth0: PHY [mdio-bus:01] driver [Generic Clause 45 PHY] (irq=POLL)
[  221.979256] mtk_soc_eth 15100000.ethernet eth0: configuring for phy/2500base-x link mode

the mdio command shows both as link up

0x00  0x03a29461  up
0x01  0x4f51ea19  up

I think I'll stick with the 1G for now and hope that some stable or rc release fixes the 2.5G port.
Thanks!

EDIT:
just looked into the pr and found the phy-id. Looks like I really got the v2 (SN ends with 1689 EU2.0)

AFAIK it won't be in the upcoming stable, but the one after and snapshots, unless it gets back ported.