Do you know which ethN relates to which DP node?
If I remember correctly:
DP1 - eth0
DP2 - eth1
DP3 - eth2
DP4 - eth4
DP5 - eth5
only the DP regs are in an unusual order (highest to lowest)
I'm getting this (Dynalink DL-WRX36):
# ls -l /sys/class/net/eth*/device
lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth0/device -> ../../../3a007000.dp1
lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth1/device -> ../../../3a001600.dp2
lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth2/device -> ../../../3a001400.dp3
lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth3/device -> ../../../3a001200.dp4
lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth4/device -> ../../../3a001000.dp5
Thanks, that makes it easy.
I do plan to use the traditional OpenWrt wan/lan naming for it as well.
Using the printed ETHN makes no sense
Only EAP102 remains.
Hi, When I try to do sysupgrade version 63ba272 I receive a message "Image check failed:
Sun Jan 1 19:20:17 CET 2023 upgrade: The device is supported, but the config is incompatible to the new image (1.0->1.1). Please upgrade without keeping config (sysupgrade -n). Sun Jan 1 19:20:17 CET 2023 upgrade: Network interface names have changed Image check failed."
Should I use force upgrade?
PS Of course, it depends on me to keep the settings
The message is self explanatory.
Few posts above the author even notify about that change - Adding OpenWrt support for Xiaomi AX3600 - #9596 by robimarko
You're right, I read it before, but not carefully enough. Thx
I no longer have the device in my possession, but almost certain that for the EAP102, dp6 maps to eth0 (uplink-PoE) and dp5 maps to eth1 (LAN)
Thanks, will roll with that for now.
Flashing OpenWrt in both partition is a bit risky, i've always kept a partition with the stock firmware in cases like this so i can restore it with the MiWiFi recovery.
Just set the network adapter with:
IP: 192.168.31.100
Mask: 255.255.255.0
DNS: 192.168.31.1
I'm having problems using the todays' build.
It don't give me access to Internet. I can access the device in local network, but can't ping outsite.
It is as an access point, using fixed ip address 192.168.1.17 with gateway 192.168.1.1
Other devices, using openwrt (Xiaomi 4g) are working as expected, only ax3600 not.
May you give me an advice?
Thanks
Today's 63ba272 is working well for me on AX3600, thanks.
Before running sysupgrade, I edited /etc/config/* to update the few references to eth[0-3], used uci set compat_version appropriately and otherwise preserved configuration in-place.
For anyone else building: my first build in an old workarea came up with eth[0-3], despite 'make clean' and removing the tmp folder. Build and update were outwardly successful, but seemingly still with the old DT. I nuked the workarea and built from scratch rather than investigating: wan/lan* then came up as expected.
Hi,
looks like I got me into trouble: updated to the latest image 63ba272, as requested with -n.
After the usual 3-5 tries it worked and I could connect to 192.168.1.1.
Then I made the mistake of restoring the config I took right before the upgrade.
The device does not show up as 192.168.1.1 nor with the ip from the config.
What is the best way to get out of this now?
With my second ax3600: how can I transfer the old config as much as possible and avoid this?
solved it.
What robimarco meant with "broken networking" is that lan interfaces are renamed from eth0-eth3 to wan, lan1-lan3.
So, for anyone with not enough background knowledge to know what that means, like me:
- Save current router config (*.tgz) as usual (luci or sysupgrade -k -b)
- untar resulting *.tgz
- edit etc/config/network (and all other files where eth0-3 might show up in your config) to adapt to the new interface names
- tar modified files again
- update router without preserving config -> will boot with lan interface ip 192.168.1.1
- connect to the router, restore the modified config and reboot
That did it for me...
Another option:
- Do a backup of your config files
- Edit etc/config/network (and all other files where eth0-3 might show up in your config) to adapt to the new interface names, directly in your router:
eth0 -> wan
eth1 -> lan1
eth2 -> lan2
eth3 -> lan3
- Update the config version with:
uci set system.@system[0].compat_version="1.1"
uci commit system
- sysupgrade as habitual
I have a lot of:
daemon.err hostapd: nl80211: kernel reports: integer out of range
messages in the log. All seems to be working but I have this messages. Someone more?
I have a problem with the newest build: The 2,4 GHZ Wireless Chip and the 5 GHz Wireless chip are nor correctly recognized (they are named as Generic (look at the photo). Therefore, i caanot connect with 5 GHZ and 2,4 GHZ rates are low. Has anybody an idee what the problem is ?
The generic name is nothing to care about, those names are just fetched from iwinfo and for anything not listed there it will just say generic
but problem is, that there is no connection with 5 ghz. I erased the config and made after sysupgrade the config new. Do i have to edit any config file etc = i remember there was something with nss or like this.
config is good - country code too. Iphone and other diveices do connect but not the Windows Pc. that was with the other patches no problem