Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.2 and newer 2. 'KRACK' vulnerability fixes were completed in r33678 for Broadcom, including k26 (33655) & k24 (33656); use build 33772 or later.
3. Bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead as WDS doesn't work with Broadcom ARM either (see Issues below).
4. Since 39469, udhcpd was removed and replaced with the already present dnsmasq, and PIE qdisc was added for some builds.
5. Policy-Based Routing with SFE enabled was fixed in r39556: 5986 and 5900 6. k2.4 (broadcom/) builds were fixed in 39715 (broken in 39144 through 39654)
Issues, observations, and/or workarounds reported: 1.Trendnet 81*DRU models are missing factory-to-flash 2.DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:6246 3.WDS does not work on Broadcom ARM devices (only MIPS<->MIPS) 4.K2.6 builds are broken since 38253(?); GUI issues:6538 5.VAPs not working at boot; workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
This appears to be fixed for some routers (different kernels, modes, and radios) since build 39508.
Important: if any issues are found, please provide log info (GUI syslog, `dmesg`, `cat /var/log/messages`).
Or put into SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).
Template to copy (after "Code:") for posting issues, be sure to include the mode in use (gateway, AP, CB, etc.):
WARNING:This thread is to report on flashing this experimental test build, providing important info for both developers and users. Always state your hardware model, version, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Please avoid discussions and create a new thread to discuss specific problems or questions, as this thread is for reporting, not support. Posts may be deleted or moved to keep this thread manageable and useful. If you don't understand the risks or what to flash and how, 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
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r39944 std (06/04/19)
Kernel: Linux 4.4.180 #181 SMP PREEMPT Tue Jun 4 07:01:53 CEST 2019 armv7l
Previous: r39927
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working so far.
Uptime: 15m
Temperatures: CPU 66.9 °C / WL0 47.5 °C / WL1 53.2 °C
What those VAP changes related to broadcom MIPS in this build from 39927 actually?
The commit in particular is not architecture-specific, as best I can tell. I just haven't felt the need to bump from 39927 yet.
So that architecture-specific thing is just copy/paste function in the web page?
BTW the change from 39927 is, yes as you said, faster (not so much) and stabler. Evidently faster and stabler in the beginning few hours after just flashed, but then hangs come out again, although less than before. After a few hours of hangs coming out, it become stabler again, but longer response delay time than the beginning hours.
Strange, for the DD-WRT builds in these 2 years, each of them almost run through this process: flash -> stable and fast -> hangs coming out -> hangs gone but slower response. Every time! I really have no ideas about why.
39927 is evidently better now, but still not perfect, not completely solved yet, so things are still going to have to be fixed. But I think the problem is related to data transportation like SFE, rather than DNS.
Another strange found: seems like turning off RFC4039 Rapid Commit support and using long preamble is stabler than turning on RFC4039 and using auto preamble size. I have no ideas, maybe some of my wireless devices are old machines, and not too compatible with the new protocols, huh...
Joined: 26 Mar 2013 Posts: 1856 Location: Hung Hom, Hong Kong
Posted: Thu Jun 06, 2019 6:53 Post subject: DD-WRT BS build 39944 and Asus RT-N18U
Router/Version:Asus RT-N18U(rev. A1)
Firmware: DD-WRT v3.0-r39944 std (06/04/19)
Kernel: Linux 4.4.180 #185 PREEMPT Tue Jun 4 07:27:26 CEST 2019 armv7l
Previous: DD-WRT v3.0-r39884 std (05/30/19)
Mode: WAN @ DHCP, Wireless @ AP
Status: Working (not 24/7 & not using IPv6, VAP, VPN, NAS nor USB)
Reset: NO reset during firmware upgrade but cold boot
1, 2 are related to front panel LAN LEDs. Skipped!
3. With USB Service enabled but no Automatic Mount,
LED of USB flash drive kept flashing
4. Error(s) logged:
Code:
grep -i err /var/log/messages
Jan 1 08:00:15 RT-N18U kern.err kernel: bcmsflash: found no supported devices
Jan 1 08:00:15 RT-N18U kern.err kernel: hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
Jan 1 08:00:26 RT-N18U daemon.err process_monitor[1185]: cyclic NTP Update failed (servers time.hko.hk)
Jan 1 08:00:26 RT-N18U daemon.err process_monitor[1185]: Last update failed, we need to re-update after 30 seconds
Jan 1 08:00:29 RT-N18U daemon.err httpd[998]: Request Error Code 404: File style/elegant/logo.png not found.
Jan 1 08:00:31 RT-N18U daemon.err httpd[998]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 1 08:00:34 RT-N18U daemon.err httpd[998]: Request Error Code 404: File style/elegant/logo.png not found.
Jan 1 08:00:36 RT-N18U daemon.err httpd[998]: Request Error Code 404: File style/elegant/logo.png not found.
5. Warning(s) logged:
Code:
grep -i warn /var/log/messages | grep -v DROP
Jan 1 08:00:15 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 0
Jan 1 08:00:15 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 1
Jan 1 08:00:15 RT-N18U kern.warn kernel: PCI: Fixing up bus 1 domain 1
Jan 1 08:00:15 RT-N18U kern.warn kernel: Boot partition size = 524288(0x80000)
Jan 1 08:00:15 RT-N18U kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x200000 size = 0x1e00000, 0x20000
Jan 1 08:00:15 RT-N18U kern.warn kernel: nf_conntrack_rtsp v0.7 loading
Jan 1 08:00:15 RT-N18U kern.warn kernel: nf_nat_rtsp v0.7 loading
Jan 1 08:00:15 RT-N18U kern.warn kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan 1 08:00:15 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 08:00:15 RT-N18U kern.warn kernel: Available 7 bytes at (off,len):
Jan 1 08:00:15 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 08:00:15 RT-N18U kern.warn kernel: Bad eraseblock 356 at 0x000002c80000
Jan 1 08:00:15 RT-N18U kern.warn kernel: Options: NO_SUBPAGE_WRITE,
Jan 1 08:00:15 RT-N18U kern.warn kernel: et: module license 'Proprietary' taints kernel.
Jan 1 08:00:15 RT-N18U kern.warn kernel: Disabling lock debugging due to kernel taint
Jan 1 08:00:15 RT-N18U kern.warn kernel: et_module_init: passivemode set to 0x0
Jan 1 08:00:15 RT-N18U kern.warn kernel: et_module_init: txworkq set to 0x0
Jan 1 08:00:15 RT-N18U kern.warn kernel: et_module_init: et_txq_thresh set to 0x400
Jan 1 08:00:15 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan 1 08:00:15 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan 1 08:00:15 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan 1 08:00:15 RT-N18U kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
Jan 1 08:00:15 RT-N18U kern.warn kernel: wl_module_init: passivemode set to 0x0
Jan 1 08:00:15 RT-N18U kern.warn kernel: wl_module_init: txworkq set to 0x0
Jan 1 08:00:15 RT-N18U kern.warn kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
Jan 1 08:00:15 RT-N18U kern.warn kernel: eth0: mixed HW and IP checksum settings.
6. Kernel debugging messages:
Code:
grep -i debug /var/log/messages
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:03.0: [14e4:4715] type 00 class 0x020000
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:03.0: reg 0x10: [mem 0x18024000-0x18024fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:03.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:04.0: [14e4:4715] type 00 class 0x020000
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:04.0: reg 0x10: [mem 0x18025000-0x18025fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:04.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:05.0: [14e4:4715] type 00 class 0x020000
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:05.0: reg 0x10: [mem 0x18026000-0x18026fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:05.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:06.0: [14e4:4715] type 00 class 0x020000
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:06.0: reg 0x10: [mem 0x18027000-0x18027fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:06.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:07.0: [14e4:0501] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:07.0: reg 0x10: [mem 0x18012000-0x18012fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:07.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:08.0: [14e4:0501] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:08.0: reg 0x10: [mem 0x18013000-0x18013fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:08.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:09.0: [14e4:0501] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:09.0: reg 0x10: [mem 0x18014000-0x18014fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:09.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0a.0: [14e4:0510] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x10: [mem 0x1800b000-0x1800bfff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x14: [mem 0x1800c000-0x1800cfff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.0: [14e4:471a] type 00 class 0x0c0310
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.0: reg 0x10: [mem 0x18022000-0x18022fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.1: [14e4:471a] type 00 class 0x0c0320
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.1: reg 0x10: [mem 0x18021000-0x18021fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0b.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0c.0: [14e4:472a] type 00 class 0x0c0330
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0c.0: reg 0x10: [mem 0x18023000-0x18023fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0c.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0d.0: [14e4:0503] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0d.0: reg 0x10: [mem 0x18020000-0x18020fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0d.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0e.0: [14e4:0506] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0e.0: reg 0x10: [mem 0x18210000-0x1821ffff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0e.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0f.0: [14e4:0507] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0f.0: reg 0x10: [mem 0x18010000-0x18010fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:10.0: [14e4:0508] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:11.0: [14e4:0509] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:11.0: reg 0x10: [mem 0x18028000-0x18028fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:11.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:12.0: [14e4:050a] type 00 class 0xffffff
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:12.0: reg 0x10: [mem 0x18029000-0x18029fff]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0000:00:12.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0001:00:00.0: [14e4:8011] type 01 class 0x060400
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0001:01:00.0: [14e4:4360] type 00 class 0x028000
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0001:01:00.0: reg 0x10: [mem 0x08000000-0x08007fff 64bit]
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci 0001:01:00.0: supports D1 D2
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
Jan 1 08:00:15 RT-N18U kern.debug kernel: pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 01
Jan 1 08:00:15 RT-N18U kern.warn kernel: Disabling lock debugging due to kernel taint
Jan 1 08:00:23 RT-N18U daemon.debug ntpclient[1187]: Connecting to time.hko.hk [118.143.17.82] ...
Jan 1 08:00:26 RT-N18U daemon.debug ntpclient[1187]: Timed out waiting for time.hko.hk [118.143.17.82].
Jan 1 08:00:26 RT-N18U daemon.debug process_monitor[1185]: We need to re-update after 3600 seconds
Jan 1 08:00:56 RT-N18U daemon.debug ntpclient[1360]: Connecting to time.hko.hk [223.255.185.2] ...
Jun 5 03:10:11 RT-N18U daemon.debug process_monitor[1185]: Restarting cron (time sync change)
Jun 5 03:10:11 RT-N18U daemon.debug process_monitor[1454]: We need to re-update after 3600 seconds
Jun 5 03:10:17 RT-N18U user.debug : ttraff: data collection started
Firmware Size
From 30515200 (b.31277) to 24711168 (b.33555) = -5804032 bytes
From 24711168 (b.33555) to 27054080 (b.34929) = 2342912 bytes
From 27054080 (b.34929) to 26640384 (b.35531) = -413696 bytes
From 26640384 (b.35531) to 25022464 (b.36995) = -1617920 bytes
From 25022464 (b.36995) to 25427968 (b.37961) = 405504 bytes
From 25427968 (b.37961) to 25804800 (b.38570) = 376832 bytes
From 25804800 (b.38570) to 27574272 (b.38840) = 1769472 bytes
From 27574272 (b.38840) to 27774976 (b.39031) = 200704 bytes
From 27774976 (b.39031) to 27779072 (b.39137) = 4096 bytes
From 27779072 (b.39137) to 27779072 (b.39144) = 0 byte
From 27779072 (b.39144) to 28672000 (b.39267) = 892928 bytes
From 28672000 (b.39267) to 27926528 (b.39296) = -745472 bytes
From 27926528 (b.39296) to 27918336 (b.39494) = -8192 bytes
From 27918336 (b.39494) to 27918336 (b.39508) = 0 byte
From 27918336 (b.39508) to 28147712 (b.39572) = 229376 bytes
From 28147712 (b.39572) to 28151808 (b.39654) = 4096 bytes
From 28151808 (b.39654) to 28151808 (b.39715) = 0 byte
From 28151808 (b.39715) to 27938816 (b.39800) = -212992 bytes
From 27938816 (b.39800) to 27938816 (b.39884) = 0 byte
From 27938816 (b.39884) to 27942912 (b.39944) = 4096 bytes
speedtest.net result for DD-WRT BS build 39944 and Asus RT-N18U.png
Description:
speedtest.net result for DD-WRT BS build 39944 and Asus RT-N18U
Filesize:
13.46 KB
Viewed:
2649 Time(s)
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
for my cell phone devices, now, youtube app is always alright, whatsapp app usually still hangs in connection, for facebook app, loading text contents and comments is always alright, but multimedia contents like photos and video streaming usually hangs in connection when loading. anyone has any ideas?
And one more strange: wifi transportation is usually better when 1 or more wired Windows PC is running...
Check the changelog to see if anything is relevant to you.
