Joined: 05 Oct 2008 Posts: 793 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Sun May 18, 2025 15:51 Post subject:
@IONK:
What happens if you disable NSS-ECM-SFE and reboot?
From what I've read on this forum for previous builds, there's a good chance that the router will get a wan IP in that case. The R7800 apparently suffers from such a feature, too.
With the new Port Status, I am showing all my connections has Half Duplex (HD) on two MX4300s and one EA8500. The switches they are connected to are showing Full Duplex, but the routers are only showing Half Duplex. I would guess this is a cosmetic thing only as it doesn't seem to have any effect so far over the speed.
Selection_016.png
Description:
Filesize:
8.82 KB
Viewed:
1904 Time(s)
_________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
I have two r7800 routers with wifi radio scheduling (I stop them over night). One router connects to the other using Station mode over 5GHz, however with this build the connection is not established automatically in the morning; I need to restart the router. I tried several 60k and 61k builds and all seems to have the same issue. _________________ Router: Netgear R7800
Router/Version: Netgear R7800
File/Kernel: Linux 6.1.138-rt28 #577 SMP Fri May 16 03:00:12 +07 2025 armv7l
Update method: wget + cli
Previous/Reset: 05-16-2025-r61298 / no reset
Mode/Status: Gateway / Working
Issues/Errors: SFE only software
Pretty simple setup, just main home router with wired and wireless access.
No fancy VLANs nor anything.
Connected to the ISP HFC router, in bridge mode, so acting only as cable modem.
Status:
- Speed OK, on wire I get the official 600/100 speeds of my connection (see lest point below)
- Wifi LEDs: 5GHz always work, 2.4GHz sometimes (I missed it, but think that both
worked on first reboot)
- Setup->Networking->Port status: now show correct full duplex info (previous did not)
- No feedback info during flash, and reboot broken right after flash, rebooted via
/proc/sysrq-trigger, works after first boot on new firmware.
- WRT flow acceleration, at least software SFE works, so I get full 600Mb/s download rates.
Any combination with hardware NSS or ECM makes the router unable to get WAN setup.
Also have a Netgear R6250 as wireless access point, no problem with it.
Do you happen to have the WAN connected to anything, or only the LAN ports?
The WAN port on the 862L is assigned to the LAN switch and another PC is connected to it, but the PC was turned off at the time.
No double NAT here, routers all have their own fixed IP at x.x.x.1, x.x.x.2 and x.x.x.3 with the main gateway being .1
What I forgot to mention was that I do have it set up for https web access only, and seeing others were reporting issues with slow interfaces with https, that might be a contributing factor.
Last edited by sumbuddie on Tue May 27, 2025 19:05; edited 1 time in total
Router/Version: Linksys MX4300
File/Kernel: dd-wrt-webflash.bin / Linux 6.6.90-rt29 #3315 SMP Sat May 17 10:54:40 +07 2025 aarch64
Previous/Reset: r60121 / Reset: no
Mode/Status: Gateway, AP, NSS-ECM, OpenVPN client, SmartDNS
Issues/Errors: crond doesn't start
After booting, crond is not running. Running "service cron restart" generates the following lines in /var/log/messages:
May 19 18:52:49.017 DD-WRT cron.info cron[9261]: (CRON) STARTUP (fork ok)
May 19 18:52:49.018 DD-WRT user.info : [cron] : successfully started
But cron actually isn't running, as "ps | grep cron" doesn't list it. Starting cron manually by running "/usr/sbin/cron" does successfully start it, and it then shows up in the output of ps.
After booting, crond is not running. Running "service cron restart" generates the following lines in /var/log/messages:
May 19 18:52:49.017 DD-WRT cron.info cron[9261]: (CRON) STARTUP (fork ok)
May 19 18:52:49.018 DD-WRT user.info : [cron] : successfully started
But cron actually isn't running, as "ps | grep cron" doesn't list it. Starting cron manually by running "/usr/sbin/cron" does successfully start it, and it then shows up in the output of ps.
It is working on both of my MX4300s.
Code:
root@MX4300-garage:~# ps | grep cron
3744 root 5924 S cron
root@MX4300-GreatRoom:~# ps | grep cron
3947 root 5924 S cron
_________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
On my MR7350 (also on this release) I use the RADV daemon to advertise an IPv6 ULA adress in my network.
The custom config is basic and looks like this:
Yesterday I came home from work, my mobile connected to wifi and seemingly everything worked fine.
Later I wanted to connect to an ipv6 only tunnel of mine through a gateway and this mobile could not connect. Seemingly the router only provided an ipv4, not an ipv6 to this device.
Restarting my mobile (nothing phone 2a) did not solve this, but restarting the router did the trick.
There were no entries regarding any problems in syslog during my tries.
Also other devices like my (android) tablets or PCs received IPv4 and IPv6 from this router during this time.
Only my nothing phone did not.
How do I debug this further?
And of course many subsequent tries yesterday after the router was restarted, till late at night did not show this behaviour anymore .