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).
Tickets closed as 'fixed' (Broadcom-related and general):
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.Many router builds too big to flash: http://svn.dd-wrt.com/ticket/6144 4. (Brimmy) WZR-1750DHP/DHPD DNSCrypt kills internet connection, no overclocking, NTP does not load 5.Various reports of wireless and VAP (repeater/guest) issues: tickets 6258, 6259, 6260 (Magnetron1.1) Workaround: Add a Startup Script with `sleep 5;stopservice lan;startservice lan`
[and/or to fix in runtime, use those stop and start commands from telnet/ssh/Commands]
Template to copy (after "Code:") for posting a reply:
WARNING:This build thread is for reporting success and/or problems 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 refrain to respond as this thread is for reporting, not support. 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 Fri Apr 20, 2018 12:13; edited 3 times in total
Joined: 18 Jul 2017 Posts: 45 Location: Wisconsin, USA
Posted: Thu Apr 19, 2018 21:32 Post subject: Still No WiFi
Router/Version: Linksys EA6500 v1
Firmware:DD-WRT v3.0-r35767 giga ( 04/19/18 )
Kernel: Linux 3.10.108-dd #18712 Thu Apr 19 12:13:18 CEST 2018 mips
Previous: DD-WRT v3.0-r35531 giga ( 03/26/18 )
Mode/Status: Gateway/AP
Setup: Using IPv6 via DNSMasq, DDNS, & Port Range Forward.
Reset: No
Issues/Errors: No WiFi
Same issue still persist that first occurred in r35667 ( 04/04/18 )
Radios appear on but devices still don't see the network and refuse to connect. Rolling back to DD-WRT v3.0-r35531 giga ( 03/26/18 ) for a third time. _________________
Posted: Thu Apr 19, 2018 23:06 Post subject: same with WNDR4500v2
wicket wrote:
Issues/Errors: No WiFi
Same issue still persist that first occurred in r35667 ( 04/04/18 )
Radios appear on but devices still don't see the network and refuse to connect. Rolling back to DD-WRT v3.0-r35531 giga ( 03/26/18 ) for a third time.
Dammit I meant to double-check this thread before flashing my WNDR4500v2 (was on 35531).
Same thing on 35767; broke my Client Bridge (plus 5 GHZ AP plus guest VAP). NAS kept crashing:
Jan 1 00:13:16 WNDR4500v2 user.info : nas : NAS daemon successfully stopped
Jan 1 00:13:18 WNDR4500v2 user.info : nas : NAS daemon hanging, send SIGKILL
Jan 1 00:13:18 WNDR4500v2 user.info : NAS : NAS wan (wl0 interface) successfully started
Jan 1 00:13:19 WNDR4500v2 user.info : NAS : NAS lan (wl1 interface) successfully started
Jan 1 00:13:19 WNDR4500v2 user.info : NAS : NAS lan (wl1.1 interface) successfully started
Jan 1 00:14:19 WNDR4500v2 daemon.err httpd[1434]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 00:16:19 WNDR4500v2 user.info : nas : NAS daemon successfully stopped
Jan 1 00:16:21 WNDR4500v2 user.info : nas : NAS daemon hanging, send SIGKILL
Jan 1 00:16:21 WNDR4500v2 user.info : NAS : NAS wan (wl0 interface) successfully started
Jan 1 00:16:21 WNDR4500v2 user.info : NAS : NAS lan (wl1 interface) successfully started
Jan 1 00:16:21 WNDR4500v2 user.info : NAS : NAS lan (wl1.1 interface) successfully started
Reverted to 35531, all good(-ish). Still need ntpclient in the Startup Commands to get time updated. _________________ #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
Router/Version: Buffalo WZR-1750DHP/DHPD Firmware: DD-WRT v3.0-r35767 std (04/19/18 Kernel: Linux 4.4.128 #2954 SMP Thu Apr 19 06:34:21 CEST 2018 armv7l Previous: BSr34760 Mode/Status: same as r35531-r35681 Reset: yes via webGUI and via telnet erase nvram CPU overclocked to 1200mhz from default 800mhz Issues/Errors: DNSCrypt kills internet connection only if i use a resolver that is not IPV6, no overclocking support and NTP does not load only if i use a DNSCrypt resolver that is not IPV6
On the up side, TX and TX errors are non-existent after flash.
The channel setting of my AP (WNDR4500v1) for wl0 (2G) and wl1 (5G) can be changed under the wireless tab but regardless of setting it is always set to channel 1 (2G) and channel 36 (5G). I've attached pictures that reflect this and confirmed (at least on the 2G) using a WiFi analyzer on my Samsung Galaxy smartphone.
I have two WNDR4500 boxes: one set up as an AP and one as a router. The AP has the referenced version whereas the router has firmware build version v3.0-r33215M giga (08/25/17). The channel settings on the router box appear to work properly. I don't know if the broken channel setting is a result of the access point/router selection or if it has to do with the firmware build version.
As to earlier comments regarding channels, in the US the 2.4 GHz spectrum has 11 channels:
while channels 12 and 13 can ONLY be used under low power conditions. Based on that, I believe the prior comments regarding disappearance of channels 12 and 13 are not warranted.
I tried the last two builds on a Linksys 320N and I used the k2.6 kernel ones with that and WIFI was broken still so its not tied to the kernel versions.
The only one that works on Netgear 3700v3 and Linksys 320N is r35531.
Router Model: Buffalo WZR-1750DHP
Firmware: DD-WRT v3.0-r35767 std (04/19/18)
Kernel: Linux 4.4.128 #2954 SMP Thu Apr 19 06:34:21 CEST 2018 armv7l
CPU Model: Broadcom BCM4708
Uptime: 2:02
Temperatures: CPU 90.8 °C / WL0 59.0 °C / WL1 51.0 °C
Previous: DD-WRT v3.0-r35531 (03/26/18)
Status:: AP / QoS HTB & HFSC - FQ-CODEL
Errors: Your proxy or firewall does not support byte-range requests. Test anyway, possibly with errors?
During upload the measured speed went to zero and stayed there error:1
QoS Erratic with all tested thresholds. No improvement over disabled despite high upload bufferbloat.
Router/Version: TP-Link Archer C9 v2
Firmware: DD-WRT v3.0-r35767 std (04/19/18
Kernel: Linux 4.4.128 #2956 SMP Thu Apr 19 06:48:35 CEST 2018 armv7l
Reset?/Mode: Reset to factory defaults
Issues/Errors: Router makes PPPoE connection and reports an IP address, but there is no internet access via wifi or ethernet
Reverting back to DD-WRT v3.0-r35244 std 03/05/18.
Joined: 10 Apr 2008 Posts: 100 Location: Chinese Mainland
Posted: Fri Apr 20, 2018 8:28 Post subject:
Router/Version: Netgear R7000 Firmware: 04-19-2018-r35767 Kernel: Linux 4.4.128 #2954 SMP Thu Apr 19 06:34:21 CEST 2018 armv7l Reset?/Mode: No reset Issues/Errors: Port Range Forwarding not working
Sorry for my English.
After upgrade from r35244 to r35767, The port range forwarding is not working.
I try to delete all config and re-config, But after click save button, The config looks not correct.
Am only one have this issue? If just me I think I need wipe and reconfigure again.
Screenshot:
config.png = My Config
update.png = After click save button
EDIT: I think I figure out what happens here, The "Application" input box can't have " - " symbol, This never happened before.
Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Fri Apr 20, 2018 13:22 Post subject: [b]Router/Version:[/b] Asus RT-N18U
Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r35767 std (04/19/18 )
Kernel: Linux 4.4.128 #2958 Thu Apr 19 06:54:23 CEST 2018 armv7l
Previous: DD-WRT v3.0-r35531 std (03/26/18 )
Mode/Status: Access Point (AP), Wired Working
Reset: NO reset during firmware upgrade
Issues/Errors: Yes, port-forwarding UI bug. Might roll back to 35531 after a few days of further testing. Wifi NOT broken for my RT-N18U.
1. Port-forwarding setup screen bug! A null-pointer assignment in the column "Source Net"?
The field was auto-magically filled with "¸ÖÁv" whenever I tried to blank it then hit Save.
It seemed that the field was actually blank when saving, but the WEBUI had a bug to *display* a blank "Source Net" field.
Null-pointer assignment?
See attachment 2!
2. syslog error messages:
Code:
root@RT-N18U:/tmp/var/log# grep -i err messages
Jan 1 00:00:13 RT-N18U kern.err kernel: bcmsflash: found no supported devices
Jan 1 00:00:17 RT-N18U daemon.err httpd[928]: Request Error Code 404: File not found.
Apr 20 08:20:56 RT-N18U daemon.err httpd[1062]: Request Error Code 408: No request appeared within a reasonable time period.
Apr 20 08:20:56 RT-N18U daemon.err httpd[1062]: Request Error Code 404: File not found.
Apr 20 08:23:12 RT-N18U daemon.err ntpclient[1571]: Failed resolving address to hostname --help: Name does not resolve
Apr 20 08:23:12 RT-N18U daemon.err ntpclient[1571]: Failed resolving server --help: Network is down
root@RT-N18U:/tmp/var/log# grep -i warn messages | grep -v DROP
Jan 1 00:00:13 RT-N18U kern.warn kernel: Device ID: 0x 1 0xf1 0x 0 0x1d 0x 1 0xf1
Jan 1 00:00:13 RT-N18U kern.warn kernel: PCI: no core
Jan 1 00:00:13 RT-N18U kern.warn kernel: PCI: no core
Jan 1 00:00:13 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 0
Jan 1 00:00:13 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 1
Jan 1 00:00:13 RT-N18U kern.warn kernel: PCI: Fixing up bus 1 domain 1
Jan 1 00:00:13 RT-N18U kern.warn kernel: Boot partition size = 524288(0x80000)
Jan 1 00:00:13 RT-N18U kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x200000 size = 0x1e00000, 0x20000
Jan 1 00:00:13 RT-N18U kern.warn kernel: nf_conntrack_rtsp v0.7 loading
Jan 1 00:00:13 RT-N18U kern.warn kernel: nf_nat_rtsp v0.7 loading
Jan 1 00:00:13 RT-N18U kern.warn kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan 1 00:00:13 RT-N18U kern.warn kernel: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Jan 1 00:00:13 RT-N18U kern.warn kernel: Available 7 bytes at (off,len):
Jan 1 00:00:13 RT-N18U kern.warn kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0)
Jan 1 00:00:13 RT-N18U kern.warn kernel: Bad eraseblock 356 at 0x000002c80000
Jan 1 00:00:13 RT-N18U kern.warn kernel: Options: NO_SUBPAGE_WRITE,
Jan 1 00:00:13 RT-N18U kern.warn kernel: et: module license 'Proprietary' taints kernel.
Jan 1 00:00:13 RT-N18U kern.warn kernel: Disabling lock debugging due to kernel taint
Jan 1 00:00:13 RT-N18U kern.warn kernel: et_module_init: passivemode set to 0x0
Jan 1 00:00:13 RT-N18U kern.warn kernel: et_module_init: txworkq set to 0x0
Jan 1 00:00:13 RT-N18U kern.warn kernel: et_module_init: et_txq_thresh set to 0x400
Jan 1 00:00:13 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan 1 00:00:13 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan 1 00:00:13 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan 1 00:00:13 RT-N18U kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
Jan 1 00:00:13 RT-N18U kern.warn kernel: wl_module_init: passivemode set to 0x0
Jan 1 00:00:13 RT-N18U kern.warn kernel: wl_module_init: txworkq set to 0x0
Jan 1 00:00:13 RT-N18U kern.warn kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
Jan 1 00:00:13 RT-N18U kern.warn kernel: eth0: mixed HW and IP checksum settings.
Jan 1 00:00:13 RT-N18U kern.warn kernel: COEX: downgraded chanspec 0x1904 to 0x1006: channel 1 used by exiting BSSs
Jan 1 00:00:13 RT-N18U kern.warn kernel: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Miscellaneous:
- Router not using IPv6, VPN nor USB
- Router is NOT working 24/7
- LAN LED ... too lazy to check! Meow... >@.@<
Old problems:
a. DDNS (inadyn) crashed in build 31722
b. Testing port-forwarding via WAN IP from within LAN not working in builds 34411-34760. Needed external proxy server.
c. NTP client not working in builds 34886-34876,35034 (affecting process_monitor?)
d. The ping to www.google.com increased from 2ms to 13ms after setting a defunct
WINS server in Setup->Basic Setup->DHCP->WINS
e. The "Source Net" field in Port-Forwarding screen was filled with "¸ÖÁv" auto-magically whenever I tried to blank it since BS build 33667!!!
dd_wrt_35767port_forwardbug_191.jpg
Description:
The "Source Net" field in Port-Forwarding screen was filled with "¸ÖÁv" automagically after saving. After further testing, the field was actually blank when saving, but the WEBUI was unable to display the blank. (null-pointer assign
Filesize:
33.57 KB
Viewed:
6090 Time(s)
dd-wrt-35767.asus.rt-n18u.jpg
Description:
Speedtest.net result
Filesize:
9.21 KB
Viewed:
6088 Time(s)
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Router/Version: Linksys EA6500V2/EA6700
Firmware: DD-WRT v3.0-r35767 std ( 04/19/18 )
Kernel: Linux 4.4.128 #2954 SMP Thu Apr 19 06:34:21 CEST 2018 armv7l
Reset?/Mode: No Reset/AP mode
Issues/Errors: Both 2.4/5 GHz Wi-Fi working, the 'wl1' interface will disappeared from GUI but still working, this is become known issue since last year. Got pages long errors as following from syslog:
Jan 1 14:55:46 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:01:00 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:01:38 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:02:02 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:05:36 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:05:57 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:07:47 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:14:40 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:16:56 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:16:59 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:27:46 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:28:10 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:31:20 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:31:53 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:32:35 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:32:37 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:35:52 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:36:25 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:36:51 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:37:33 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:37:38 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:38:00 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:38:18 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:41:03 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:41:41 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:46:05 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:46:29 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:46:45 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:47:13 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:49:02 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:50:20 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:50:29 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:50:57 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:51:07 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Jan 1 15:57:49 router daemon.err httpd[1471]: Request Error Code 408: No request appeared within a reasonable time period.
Posted: Fri Apr 20, 2018 14:16 Post subject: Re: [b]Router/Version:[/b] Asus RT-N18U
mwchang wrote:
Issues/Errors: Yes, port-forwarding UI bug. Might roll back to 35531 after a few days of further testing. Wifi NOT broken for my RT-N18U.
1. Port-forwarding setup screen bug! A null-pointer assignment in the column "Source Net"?
The field was auto-magically filled with "¸ÖÁv" whenever I tried to blank it then hit Save.
It seemed that the field was actually blank when saving, but the WEBUI had a bug to *display* a blank "Source Net" field.
Null-pointer assignment?