Does the fw available from the selector: https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=qualcommax%2Fipq60xx&id=linksys_mr7500 include your code (i.e. NSS)? Also wondering if the dependency packages for ksmbd and DLNA will ever be made available to install (or if there is a workaround/manual way to do this). These are pretty standard features.
Booting router with some devices plugged into LAN ports solved the problem, so I decided not to fight further. Thanks a lot!
By the way the WAN port seems to drop randomly every 20hrs+. Any reasons and any way to walk around? Causing cameras and speakers to drop...
@pppig236 In the case of Linksys devices, the kernel partition overlaps the rootfs partition. If you do not define all partitions this way manually, then partition overlap does not occur:
[ 1.228654] Creating 20 MTD partitions on "qcom_nand.0":
[ 1.234914] 0x000000000000-0x000000180000 : "0:sbl1"
[ 1.242480] 0x000000180000-0x000000280000 : "0:mibib"
[ 1.246741] 0x000000280000-0x000000600000 : "0:qsee"
[ 1.254421] 0x000000600000-0x000000680000 : "0:devcfg"
[ 1.256256] 0x000000680000-0x000000700000 : "0:rpm"
[ 1.261352] 0x000000700000-0x000000780000 : "0:cdt"
[ 1.266018] 0x000000780000-0x000000800000 : "0:appsblenv"
[ 1.270893] 0x000000800000-0x000000980000 : "0:appsbl"
[ 1.277326] 0x000000980000-0x000000a00000 : "0:art"
[ 1.281529] 0x000000a00000-0x000000a80000 : "0:ethphyfw"
[ 1.286200] 0x000000a80000-0x000000b00000 : "u_env"
[ 1.291815] 0x000000b00000-0x000000b40000 : "s_env"
[ 1.296143] 0x000000b40000-0x000000b80000 : "devinfo"
[ 1.301033] 0x000000b80000-0x000001380000 : "kernel"
[ 1.313348] 0x000001380000-0x000005d80000 : "rootfs"
[ 1.386409] 0x000005d80000-0x000006580000 : "alt_kernel"
[ 1.399094] 0x000006580000-0x00000af80000 : "alt_rootfs"
[ 1.468373] 0x00000af80000-0x00000b380000 : "sysdiag"
[ 1.472684] 0x00000b380000-0x00001f080000 : "syscfg"
[ 1.767622] 0x00001f080000-0x00001f580000 : "app_data"
and all serial port installation steps do not apply.
This is currently an issue with the MR7350 and MR7500.
so whats the issue, is it causing any problems
In general, this is not a issue, it's just that these instructions from the commit message cannot be executed:
Flash instructions (With Serial):
========
1. Installation using serial connection from OEM firmware (default login: root, password: admin):
...
After first boot install firmware on second partition:
- mtd -r -e kernel -n write openwrt-qualcommax-ipq60xx-linksys_mr7500-squashfs-factory.bin kernel
or:
- mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq60xx-linksys_mr7500-squashfs-factory.bin alt_kernel
2. Installation from initramfs image using USB drive:
...
Write firmware to the flash from initramfs:
- mtd -e kernel -n write openwrt-qualcommax-ipq60xx-linksys_mr7500-squashfs-factory.bin kernel
and:
- mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq60xx-linksys_mr7500-squashfs-factory.bin alt_kernel
3. Back to the OEM firmware:
- mtd -e kernel -n write FW_MR7500_1.1.12.211919_prod.img kernel
and:
- mtd -r -e alt_kernel -n write FW_MR7500_1.1.12.211919_prod.img alt_kernel
1 Like
Upon reading your post, I configured a rsyslog server and connected MR7500 to remotely logging to it (mostly to filter the "BEACON-REQ-TX-STATUS" and "BEACON-RESP-RX" spam). Since then the ethernet ports have been seamlessly up for 40hrs+ with no drop at all.
I don't remember anything else being changed except for the remote logging (port 514 UDP). Could this be related? I do remember all previous drops happened when there was very little LAN activities (at sleep, or no one at home). Could UDP logging keep some powersave features from kicking in? I did solve some similar situations with MTK switches by disabling EEE and Tx-LPI.
Finally some logs caught here, WAN went down when nothing happened to it. No one was even touching the entire home network:
May 11 18:13:28 OpenWRT-MR7500 netifd: Network device 'wan' link is down
May 11 18:13:28 OpenWRT-MR7500 kernel: nss-dp 3a003000.dp5-syn wan: PHY Link is down
May 11 18:13:28 OpenWRT-MR7500 kernel: br-lan: port 5(wan) entered disabled state
May 11 18:13:32 OpenWRT-MR7500 kernel: nss-dp 3a003000.dp5-syn wan: PHY Link up speed: 2500
May 11 18:13:32 OpenWRT-MR7500 kernel: br-lan: port 5(wan) entered blocking state
May 11 18:13:32 OpenWRT-MR7500 kernel: br-lan: port 5(wan) entered forwarding state
May 11 18:13:32 OpenWRT-MR7500 netifd: Network device 'wan' link is up
May 11 18:13:38 OpenWRT-MR7500 watchcat[4151]: Could not reach 8.8.8.8 for 60. Rebooting after reaching 21600
[233465.009039] nss-dp 3a003000.dp5-syn wan: PHY Link is down
[233465.009278] br-lan: port 5(wan) entered disabled state
[233469.159425] nss-dp 3a003000.dp5-syn wan: PHY Link up speed: 2500
[233469.159590] br-lan: port 5(wan) entered blocking state
[233469.164511] br-lan: port 5(wan) entered forwarding state
Luckily also found some older logs:
Sun Apr 27 13:58:25 2025 daemon.notice netifd: Network device 'wan' link is down
Sun Apr 27 13:58:25 2025 kern.info kernel: [679459.525885] nss-dp 3a003000.dp5-syn wan: PHY Link is down
Sun Apr 27 13:58:25 2025 kern.info kernel: [679459.526116] br-lan: port 5(wan) entered disabled state
Sun Apr 27 13:58:27 2025 daemon.notice hostapd: phy0-ap0: AP-STA-POLL-OK 88:88:88:88:88:88
Sun Apr 27 13:58:28 2025 daemon.notice hostapd: phy2-ap0: BEACON-REQ-TX-STATUS 11:11:11:11:11:11 209 ack=1
Sun Apr 27 13:58:35 2025 kern.info kernel: [679468.886122] nss-dp 3a003000.dp5-syn wan: PHY Link up speed: 2500
Sun Apr 27 13:58:35 2025 kern.info kernel: [679468.886280] br-lan: port 5(wan) entered blocking state
Sun Apr 27 13:58:35 2025 kern.info kernel: [679468.891200] br-lan: port 5(wan) entered forwarding state
Sun Apr 27 13:58:35 2025 daemon.notice netifd: Network device 'wan' link is up
[679459.525885] nss-dp 3a003000.dp5-syn wan: PHY Link is down
[679459.526116] br-lan: port 5(wan) entered disabled state
[679468.886122] nss-dp 3a003000.dp5-syn wan: PHY Link up speed: 2500
[679468.886280] br-lan: port 5(wan) entered blocking state
[679468.891200] br-lan: port 5(wan) entered forwarding state
I plugged it into a Linux server with a soft bridge when these logs are generated. Here are what's logged from the server:
[2134471.822276] igc 0000:05:00.0 enp5s0: NIC Link is Down
[2134471.822645] br0: port 2(enp5s0) entered disabled state
[2134476.058471] igc 0000:05:00.0 enp5s0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[2134476.058653] br0: port 2(enp5s0) entered blocking state
[2134476.058666] br0: port 2(enp5s0) entered forwarding state
[2134477.830252] igc 0000:05:00.0 enp5s0: NIC Link is Down
[2134477.830589] br0: port 2(enp5s0) entered disabled state
[2134487.102013] igc 0000:05:00.0 enp5s0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[2134487.102201] br0: port 2(enp5s0) entered blocking state
[2134487.102218] br0: port 2(enp5s0) entered forwarding state
[2134488.093660] igc 0000:05:00.0 enp5s0: NIC Link is Down
[2134488.105615] br0: port 2(enp5s0) entered disabled state
[2134497.325370] igc 0000:05:00.0 enp5s0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX/TX
[2134497.325437] br0: port 2(enp5s0) entered blocking state
[2134497.325440] br0: port 2(enp5s0) entered forwarding state
The WAN port drop/reset happens where ever it is plugged into though.
(post deleted by author)