Router/Version: Netgear R7000 Firmware: DD-WRT v3.0-r49418 std (07/04/22) Kernel: Linux 4.4.302-st14 #6590 SMP Thu Jun 30 14:24:10 +07 2022 armv7l Mode: Gateway, Wireless AP, Static Leases. CTF & FA Enabled. NAT and QOS Off. All services off under Status>Sys-info. Reset: Nope. Previous: 06-29-2022-r49392 Status: Working really, really well so far; still testing. wl: 14E4:4360 Temperatures: CPU 68.0 °C / WL0 54.5 °C / WL1 56.0 °C Base CFE: Modified Asus ASUS RT-AC68P/ASUS RT-AC68U (C0 Model CFE V1.3.0.7) Configured as a stock R7000.
Speedtest-1.jpg
Description:
Speedtest Over 5.8GHz Wireless.
Filesize:
63.35 KB
Viewed:
3685 Time(s)
Logs.txt
Description:
Full system logs. MAC scrubbed, password scrubbed, the fun stuff at the bottom as usual!
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Tue Jul 05, 2022 16:46 Post subject:
IONK wrote:
ho1Aetoo wrote:
IONK wrote:
cosmetic issue on /Management.asp > Network Stack Tuning
CTRL+F5
I've just Ctrl-F5 in Internet Explorer InPrivate mode and Google Chrome Incognito mode, but the issue is still there.
Correction: the section "Network Stack Tuning" shows up 2 time, one of them is strange. Screenshot is updated.
When this was changed/fixed and because the defaults about maximum connection issue was fixed, all the outdated webconfig for all routers were removed and now all devices use only one webconfig file, before there were several all duplicates of each other, not needed really.
For the less technically minded, the webconfig file is essentially what has the HTML for this specific portion.
What browser did you use to flash from stock and from initial to current firmware image? IE/Chromium may have corrupted something or the base.nvramconfig file may be bunked. These older routers and older firmware were a little more forgiving with older versions of Firefox.
Such a large jump in versions, no telling if there was a commit that is amiss, but a hard reset may fix any nvram corruption that may be culprit, but everything in /etc is written on flashing and survives a reboot to the best of my knowledge. Can anyone verify?
Router/Version: R7000P
File/Kernel: factory to ddwrt
Previous/Reset: 49113. No reset. Power cycle only
Mode/Status: upgrade successfully done
Issues/Errors: random reboots. Reverted back to 49113
I just realized i enabled CTF after upgrade and didn't disable it to see if this is the cause of random reboots. Will try again later if i have time
Router/Version: Archer C9 V1
Firmware: DD-WRT v3.0-r49418 std (07/04/22)
Kernel: Linux 4.4.302-st14 #6590 SMP Thu Jun 30 14:24:10 +07 2022 armv7l
Mode: Gateway, Wireless AP (2.4Ghz + 1 VAP / 5Ghz), IPV4 + IPV6, dnsmasq as DHCP server, client Wireguard Tunnel exposed on VAP only. SFE activated (not CTF).
Reset: No.
Previous: 06-29-2022-r49392
Status: Cannot access any IPV4 machine/website except the router itself. Cannot ping any IPV4 website. Temperatures: CPU 72.0 °C / WL0 55.0 °C / WL1 56.0 °C
Base CFE: Stock
Did not collect logs as this is my main router and I had critical need to restore Internet access ASAP - reverted back to previous build (49392) which works OK.
Edit - Seems that there is an issue with Changeset 49404 (https://svn.dd-wrt.com/changeset/49404). My endpoint is an IPv6 URL of type [aaaa:bbbb:...]. The new code only handles IPv4.
With an IPv6 address as endpoint, it thinks it is an URL, calculate endp variable incorrectly and deletes a critical route.
Last edited by belotv on Wed Jul 06, 2022 15:21; edited 4 times in total
What browser did you use to flash from stock and from initial to current firmware image? IE/Chromium may have corrupted something or the base.nvramconfig file may be bunked. These older routers and older firmware were a little more forgiving with older versions of Firefox.
Such a large jump in versions, no telling if there was a commit that is amiss, but a hard reset may fix any nvram corruption that may be culprit, but everything in /etc is written on flashing and survives a reboot to the best of my knowledge. Can anyone verify?
Joined: 18 Mar 2014 Posts: 12915 Location: Netherlands
Posted: Wed Jul 06, 2022 16:13 Post subject:
belotv wrote:
Router/Version: Archer C9 V1
Firmware: DD-WRT v3.0-r49418 std (07/04/22)
Kernel: Linux 4.4.302-st14 #6590 SMP Thu Jun 30 14:24:10 +07 2022 armv7l
Mode: Gateway, Wireless AP (2.4Ghz + 1 VAP / 5Ghz), IPV4 + IPV6, dnsmasq as DHCP server, client Wireguard Tunnel exposed on VAP only. SFE activated (not CTF).
Reset: No.
Previous: 06-29-2022-r49392
Status: Cannot access any IPV4 machine/website except the router itself. Cannot ping any IPV4 website. Temperatures: CPU 72.0 °C / WL0 55.0 °C / WL1 56.0 °C
Base CFE: Stock
Did not collect logs as this is my main router and I had critical need to restore Internet access ASAP - reverted back to previous build (49392) which works OK.
Edit - Seems that there is an issue with Changeset 49404 (https://svn.dd-wrt.com/changeset/49404). My endpoint is an IPv6 URL of type [aaaa:bbbb:...]. The new code only handles IPv4.
With an IPv6 address as endpoint, it thinks it is an URL, calculate endp variable incorrectly and deletes a critical route.
Did not know anybody was actually using IPv6 but I see the problem.
Will fix this later this week, fix meaning if endpoint is IPv6 nothing will happen as it does not set routes either for IPv6 yet.
Can you share how you have setup?
you can PM me about it so that I might add it to the guides.
Thanks egc, I did nothing special for configuration, you can actually use IPv6 endpoint by enclosing the IP in brackets, which is the same syntax as to access an IPv6 in a web browser so can be added to the guide quite easily.
Reason for IPv6 use is that some ISP in France now use CGNAT for IPv4, meaning that IPs are being shared between clients... and you lose the ability to expose a service on a specific port.
For the moment I am only using an IPv6 endpoint, but I do not route IPv6 traffic through the VPN. For IPv6 routing, I am working on it but did not really got the time to finish that config. I got it working with Android/iOS/OpenWRT clients but unfortunately not yet with DDWRT.
Joined: 18 Mar 2014 Posts: 12915 Location: Netherlands
Posted: Wed Jul 06, 2022 17:01 Post subject:
belotv wrote:
Thanks egc, I did nothing special for configuration, you can actually use IPv6 endpoint by enclosing the IP in brackets, which is the same syntax as to access an IPv6 in a web browser so can be added to the guide quite easily.
Reason for IPv6 use is that some ISP in France now use CGNAT for IPv4, meaning that IPs are being shared between clients... and you lose the ability to expose a service on a specific port.
For the moment I am only using an IPv6 endpoint, but I do not route IPv6 traffic through the VPN. For IPv6 routing, I am working on it but did not really got the time to finish that config. I got it working with Android/iOS/OpenWRT clients but unfortunately not yet with DDWRT.
Thanks yes it is the routing I am interested in.
WireGuard itself will place the brackets, I think, so probably not necessary.
Will also see how to proper delete the endpoint if it is ipv6 for future use.
But at least I will make it so that the default route is note deleted if IPv6 is encountered because that is what is happening
Router/Version: Netgear Nighthawk AC1750 R6700v3 File/Kernel: netgear-r6700v3-webflash.bin/ Linux 4.4.302-st14 #6590 SMP Thu Jun 30 14:24:10 +07 2022 armv7l
Previous/Reset: DD-WRT v3.0-r46979 std (06/21/21) / no
Mode/Status: Client Bridge on 2.4GHz radio, 5GHz radio as Access Point / working
Issues/Errors: Mostly minor!
- After updating, upstream bandwidth was abysmal. I think it's related to the Security > Firewall > Filter multicast checkbox, which was unchecked after update. (Firewall is off for client bridge mode.) "Filter multicast" has previously caused problems with WAN traffic. It also won't stay checked when I save, apply, or reboot, which makes me think the setting isn't correctly represented in the UI.
- Setup > Basic Setup > Update Interval (NTP setting) was named "undefined" after the update, but the field value was still there.
- "Client" and "Client bridge" mode now seem to be named "Station" and "Station bridge", respectively, but it doesn't seem like any documentation has been updated.
After updating without a reset, I did the reset and reconfigured. Everything still works fine, and the NTP field name is fixed.
