Changelogs: SVN Changelog:through34760 (last build was 34578)
Summary: (deprecated after 29739)
Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.10 and newer 2. krack fixes for Broadcom were completed in 33678, including k26 (33655) & k24 (33656).
3. The fix for DIR-868L & DIR-880L was done in 34093 (34311 build): see 5518 and 5963 - thanks to quarkysg
Tickets (Broadcom-related and general) closed as 'fixed' in this build: 1.
Issues, observations, and/or workarounds reported: 1. (egc) Policy-Based Routing broken if SFE enabled: http://svn.dd-wrt.com/ticket/5900 quarkysg's PBR+SFE fix: http://svn.dd-wrt.com/ticket/5986 2. (egc) "OpenVPN 2.4 is stable but you have to tweak your config" with: `mtu-disc yes` & `proto udp4` 3. (wicket) "Port Forwarding, Port Range Forwarding and DMZ are all broken...since build 34411" http://svn.dd-wrt.com/ticket/6162 4. (wicket) "the significant TX errors I experienced in the last few builds on the wl0 interface have ceased"
Template to copy (after "Code:") for posting a reply:
WARNING:This build thread is for reporting successes and problem with loading this experimental test build.
This is important info for developers and users. Always state your hardware model, version, and SPECIFIC build (e.g. dd-wrt.v24-33555_NEWD-2_K3.x_mega-nv64k.bin). Create your own thread to discuss any specific problems or questions, and please do not respond to such questions. This thread is to report info, not to seek answers, so posts not meeting this criteria may be deleted or moved. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless. If you don't understand the risk or know what build to flash and how to flash properly, with a means of recovery if it bricks, do NOT flash this experimental test build. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Last edited by jwh7 on Sat Feb 10, 2018 15:46; edited 4 times in total
Router/Version: Archer C9 v1
Firmware: DD-WRT v3.0-r34760 std (01/30/1 Kernel: Linux 4.4.114-rc1 #2552 SMP Tue Jan 30 10:55:29 CET 2018 armv7l
Previous: r34578
Mode/Status: WAN disabled and DHCP set to forwarding; using as AP only.
Reset: No
Issues/Errors: Noticed in my logs that I get a dhcpfwd restart every two minutes. I don't notice any performance issues though. This was also happening on r34578. Is that normal when running as an AP?
Code:
Jan 30 20:20:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 30 20:20:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Jan 30 20:22:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 30 20:22:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Jan 30 20:24:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 30 20:24:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Jan 30 20:26:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 30 20:26:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Jan 30 20:28:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 30 20:28:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Jan 30 20:30:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 30 20:30:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
...
Jan 31 00:52:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 31 00:52:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Jan 31 00:54:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 31 00:54:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Jan 31 00:56:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 31 00:56:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Jan 31 00:58:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 31 00:58:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Posted: Wed Jan 31, 2018 1:32 Post subject: Netgear R6300
pekkleminer wrote:
Issues/Errors: Noticed in my logs that I get a dhcpfwd restart every two minutes. I don't notice any performance issues though. This was also happening on r34578. Is that normal when running as an AP?
Code:
Jan 30 20:20:00 Archer C9 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jan 30 20:20:00 Archer C9 user.info : dhcpfwd : dhcp forwarder daemon successfully started
Are you forwarding dhcp to another subnet? Normal AP mode should not use DHCP Forwarder.
Router/Version: Netgear R6300
Firmware: DD-WRT v3.0-r34760 giga ( 01/30/18 )
Kernel: Linux 3.10.108-dd #17540 Tue Jan 30 16:30:11 CET 2018 mips
Previous: 33772 giga
Mode/Status: Gateway router inside my LAN for testing
Reset: No
Issues/Errors: UPDATE: used 5 GHz this morning before work, still no issues; uptime was 10 hrs at that time. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Last edited by jwh7 on Wed Jan 31, 2018 16:47; edited 1 time in total
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r34760 std ( 01/30/18 )
Kernel: Linux 4.4.114-rc1 #2550 SMP Tue Jan 30 10:30:35 CET 2018 armv7l
Previous: r34578
Mode/Status: Gateway / working
Reset: no
Issues/Errors: None so far, except my Nest thermostat couldn't connect to wl0 until after a second reboot of the router, however the significant TX errors I experienced in the last few builds on the wl0 interface have ceased.
Last edited by flyzipper on Wed Jan 31, 2018 1:52; edited 2 times in total
Joined: 18 Jul 2017 Posts: 45 Location: Wisconsin, USA
Posted: Wed Jan 31, 2018 1:44 Post subject: Port Forwarding Still Broken!!!
Router/Version: Linksys EA6500 v1
Firmware: DD-WRT v3.0-r34760 giga ( 01/30/18 )
Kernel: Linux 3.10.108-dd #17540 Tue Jan 30 16:30:11 CET 2018 mips
Previous: DD-WRT v3.0-r34311 giga (12/29/17)
Mode/Status: Gateway/AP
Reset: No
Issues/Errors: Port Forwarding is broken.
Port Forwarding, Port Range Forwarding and DMZ are all broken, and have been broken since build 34411 will be rolling back to 34311 again.
Update ( 02-02-2018 )
Upon reading following comments I've decided to test port forwarding from another connection and found my TS3 server operating properly, it appears I'm just unable to connect via WAN IP from any machine with in the LAN. Will continue to test DD-WRT v3.0-r34760 giga hoping when hosting Steam game servers clients within the LAN can still connect.
Update 2 - 06 - 2018
Teamspeak works normally and steam game servers come up and connect friends can join but I am unable to join or see my own servers within said games. I need lan devices to be able to connect to WAN addresses. _________________
Last edited by wicket on Tue Feb 06, 2018 14:20; edited 3 times in total
Router/Version: Buffalo WZR-1750DHP/DHPD Firmware: DD-WRT v3.0-r34760 std (01/30/1 Kernel: Linux 4.4.114-rc1 #2550 SMP Tue Jan 30 10:30:35 CET 2018 armv7l Previous: BSr34578 Mode/Status: Working Reset: nope Issues/Errors: none so far
Running good and the firmware flashed without any issues.
Questions, how come the build uses the longterm 4.4.114 Linux kernel version and not the longterm: 4.9.79 Linux Kernel version? Isn't the 4.9.79 newer or has more fixes than the 4.4.114?
Requesting one of you to kindly make a ticket to add CTCP to the TCP Congestion Control list please.
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Wed Jan 31, 2018 15:31 Post subject: Port-forwarding not working if tested from within
Router is Asus RT-N18U.
Both single-port and port-range forwarding are NOT working. Might fall back to 34311. I had deleted old rules and added the new rules.
Should I open a ticket? For all 3 recent builds?
(Um... having problem creating an account in Trac)
FYI, most other functions are working OK, as an AP.
update: I changed the port number to forward to 8008 to escape existing service name for port "8080". Still didn't work.
update again:
It seemed that the usual method I was using to test port-forwarding no longer worked the same way as build 34311. I am going to open a new thread on this.
After I used an external public proxy server to test the port-forwarding, it was just working!
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Thu Feb 01, 2018 8:26 Post subject: nvram erase
I just found that `nvram erase` followed by `nvram commit` did NOT erase settings in port-forwarding. Is this normal?
In fact, it seemed that the command didn't do anything. It's not exactly the same as clicking "Restore Factory Default" in the WebUI. _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Thu Feb 01, 2018 9:38 Post subject: Asus RT-N18U and DD-WRT BS Build 34760
Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r34760 (01/30/18 )
Kernel: Linux 4.4.114-rc1 #2554 Tue Jan 30 11:09:09 CET 2018 armv7l
Previous: DD-WRT v3.0-r34311 std (12/29/17)
Mode/Status: Access Point (AP), Wired Working, Wireless working
Reset: NO reset during firmware upgrade
Issues/Errors: None (not using IPV6, VPN nor USB)
1. LAN LED ... too lazy to check! Meow... >@.@<
2. DDNS function working normally and didn't crash like 31722
3. My router is NOT working 24/7
4. When the router rebooted right after firmware upgrade via Web GUI, the ping to www.google.com no longer increased from 2ms to 14ms as in build 33772 and older!
5. Testing port-forwarding via WAN IP from within LAN no longer worked since build 34411! Needed to use external proxy server.
Posted: Fri Feb 02, 2018 17:03 Post subject: ASUS RT-AC68U & Linksys E2000
Asus RT-AC68U
Firmware: DD-WRT v3.0-r34760 std (01/30/1 - (previous r34578)
Kernel: Linux 4.4.114-rc1 #2550 SMP Tue Jan 30 10:30:35 CET 2018 armv7l
5Ghz (Mixed) with 80Mhz channel width: Ok
SSH: Ok
Telnet: Disabled but tested to work
Site Survey: Ok
Wi-viz Survey 2.4Ghz & 5Ghz: Ok
Reset: No
Status: Ok
Uptime: 1 day, 20:07
CPU Temperature: CPU 65.8 °C / WL0 45.3 °C / WL1 45.3 °C
2 x E2000
Firmware: DD-WRT v3.0-r34760 mega (01/30/1 - (previous r34578)
Kernel: Linux 3.10.108-dd #17556 Tue Jan 30 16:48:47 CET 2018 mips
2.4Ghz (NG-mixed) with 40Mhz channel width: Ok
SSH: Ok
Telnet: Disabled but tested to work
Site Survey: Ok
Wi-viz Survey 2.4Ghz: Ok
Reset: No
Status: Ok
Uptime: 1 day, 20:50
CPU Temperature: WL0 53.0 °C
All devices working as AP's each with individual 1Gb wired connections to main firewall
Router Model: Linksys E3000
Firmware Version: DD-WRT v3.0-r34760 mega (01/30/1
Kernel VersionLinux 3.10.108-dd #17556 Tue Jan 30 16:48:47 CET 2018 mips
Previous: BSr34578
Mode/Status: AP /Working
Reset: 30/30/30
Issues/Errors: NTP Client working again after 30/30/30, 2.4G wifi speed is very slow, with setting Channel Width at 40MHz, but 20MHz is better.
