Your reports for Broadcom units are greatly appreciated !
Router:
Firmware:
Kernel:
Status:
Reset:
Errors:
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 and SPECIFIC build (e.g. 33525_NEWD-2_K2.6_mega-nv64k.bin). Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved. Please also do not respond to such questions. This thread is to report info, not to seek it. Posts that do not add to understanding this build will be deleted. Make sure you know how to flash properly and the risk before using this build. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless.
If you don't know what build to flash and how to flash properly and have a means of recovery if things should go wrong, do NOT flash this experimental test build.
Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Fri Nov 17, 2017 12:51 Post subject: Asus RT-N18U and DD-WRT BS Build 33772
Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r33772 std (11/16/17)
Kernel: Linux 4.4.98 #2253 Thu Nov 16 09:47:55 CET 2017 armv7lx
Previous: DD-WRT v3.0-r33679 std (11/04/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 increased from 2ms to 14ms!!
I needed to disdable DNSmasq, Save, then Reboot to fix the ping. DNSmasq was enabled automagically after a reboot.
Appendix:
Code:
System Log
Jan 1 08:00:17 RT-N18U syslog.info syslogd started: BusyBox v1.27.2
Jan 1 00:00:17 RT-N18U kern.notice kernel: klogd started: BusyBox v1.27.2 (2017-11-16 09:50:33 CET)
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:08.0: [14e4:0501] type 00 class 0xffffff
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:08.0: reg 0x10: [mem 0x18013000-0x18013fff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:08.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:09.0: [14e4:0501] type 00 class 0xffffff
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:09.0: reg 0x10: [mem 0x18014000-0x18014fff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:09.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0a.0: [14e4:0510] type 00 class 0xffffff
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x10: [mem 0x1800b000-0x1800bfff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x14: [mem 0x1800c000-0x1800cfff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0b.0: [14e4:471a] type 00 class 0x0c0310
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0b.0: reg 0x10: [mem 0x18022000-0x18022fff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0b.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0b.1: [14e4:471a] type 00 class 0x0c0320
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0b.1: reg 0x10: [mem 0x18021000-0x18021fff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0b.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0c.0: [14e4:472a] type 00 class 0x0c0330
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0c.0: reg 0x10: [mem 0x18023000-0x18023fff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0c.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0d.0: [14e4:0503] type 00 class 0xffffff
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0d.0: reg 0x10: [mem 0x18020000-0x18020fff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0d.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0e.0: [14e4:0506] type 00 class 0xffffff
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0e.0: reg 0x10: [mem 0x18210000-0x1821ffff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0e.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0f.0: [14e4:0507] type 00 class 0xffffff
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0f.0: reg 0x10: [mem 0x18010000-0x18010fff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:10.0: [14e4:0508] type 00 class 0xffffff
Jan 1 00:00:17 RT-N18U kern.info kernel: pci 0000:00:10.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:11.0: [14e4:0509] type 00 class 0xffffff
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:11.0: reg 0x10: [mem 0x18028000-0x18028fff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:11.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:12.0: [14e4:050a] type 00 class 0xffffff
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:12.0: reg 0x10: [mem 0x18029000-0x18029fff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0000:00:12.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 00:00:17 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 0
Jan 1 00:00:17 RT-N18U kern.info kernel: PCIE1 link=1
Jan 1 00:00:17 RT-N18U kern.info kernel: PCIE1 switching to GEN2
Jan 1 00:00:17 RT-N18U kern.info kernel: PCIE1 link=1
Jan 1 00:00:17 RT-N18U kern.info kernel: PCI host bridge to bus 0001:00
Jan 1 00:00:17 RT-N18U kern.info kernel: pci_bus 0001:00: root bus resource [mem 0x08000000-0x0fffffff]
Jan 1 00:00:17 RT-N18U kern.info kernel: pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0001:00:00.0: [14e4:8011] type 01 class 0x060400
Jan 1 00:00:17 RT-N18U kern.debug kernel: pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
Jan 1 00:00:17 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 1
speedtest.net.assus.rt-n18u.dd-wrt.bs.33772.png
Description:
speedtest.net result for Asus RT-N18U and DD-WRT BS Build 33772
Filesize:
10.61 KB
Viewed:
55056 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: RT-AC87U A1
Firmware: DD-WRT v3.0-r33772 std (11/16/17)
Kernel: Linux 4.4.98 #2256 SMP Thu Nov 16 10:08:54 CET 2017 armv7l
Previous: DD-WRT v3.0-r33679 std (11/04/17)
Mode/Status: Gateway/working
Reset: No
Issues/Errors: OK
Router/Version: RT-AC68R A1
Firmware: DD-WRT v3.0-r33772 std (11/16/17)
Kernel: Linux 4.4.98 #2249 SMP Thu Nov 16 09:16:32 CET 2017 armv7l
Previous: DD-WRT v3.0-r33492 std (10/10/17)
Mode/Status: Gateway/working
Reset: No
Issues/Errors: OK
Router/Version: RT-AC66U A1
Firmware: DD-WRT v3.0-r33772 giga (11/16/17)
Kernel: Linux 3.10.108 #16609 Thu Nov 16 14:22:03 CET 2017 mips
Previous: DD-WRT v3.0-r33492 giga (10/10/17)
Mode/Status: Repeater Bridge 5Ghz (AC/N-Mixed)/working
Reset: No
Issues/Errors: Yes, need the following command(s) for 5 Ghz connection and NTP time sync
sleep 5; startstop lan;
stopservice process_monitor && startservice process_monitor;
Router/Version: E4200 V1
Firmware: DD-WRT v3.0-r33772 mega (11/16/17)
Kernel: Linux 3.10.108 #16625 Thu Nov 16 14:36:31 CET 2017 mips
Previous: DD-WRT v3.0-r33492 mega (10/10/17)
Mode/Status: Repeater Bridge 5Ghz (N-Only 5 GHz) /working
Reset: No
Issues/Errors: Yes, need the following command(s) for 5 Ghz connection and NTP time sync
sleep 5; startstop lan;
stopservice process_monitor && startservice process_monitor;
Edit: Rolling repeaters back to 33492 devices on repeater have a hard time connecting to the internet
Include command for repeater bridge
*** Since 27343 the following command needs to be included in the Start-up script, ‘sleep 5; startstop lan;’ to allow the 5 Ghz to connect to the main AP in Repeater Bride mode when rebooting. Thanks to Magnetron 1.1 for putting in forum topic ***
*** If NTP time sync is not working on reboot include in the Start-up script ‘stopservice process_monitor && startservice process_monitor;’ *** _________________ Netgear XR500, R7800
Asus AC87Ua1
Repeater Bridge
Netgear R6400v2otp
Last edited by jrscs on Sat Nov 18, 2017 15:32; edited 2 times in total
Joined: 13 Aug 2013 Posts: 6858 Location: Romerike, Norway
Posted: Fri Nov 17, 2017 14:16 Post subject:
Router/Version: RT-AC66U A1
Firmware: DD-WRT v3.0-r33772 giga (11/16/17)
Kernel: Linux 3.10.108 #16609 Thu Nov 16 14:22:03 CET 2017 mips
Previous: DD-WRT v3.0-r33607
Mode/Status: IPv6 from wifi-client is working again.
Reset: No
Issues/Errors:
Router:WZR-600DHP2 WZR-1750DHP
Errors: Wireless and OpenVPN services do not start automatically after reboot.
Exactly the same error as http://svn.dd-wrt.com/ticket/6017
Similar errors also occur in Kong firmware,
but the problem does not occur because the recovery process starts automatically.
Posted: Fri Nov 17, 2017 17:21 Post subject: Re: NEW BS Build 11-16-2017-33772
Router: E3000
Firmware: dd-wrt.v24-33772_NEWD-2_K3.x_mega-e3000.bin
Old firmware: dd-wrt.v24-33555_NEWD-2_K3.x_mega-e3000.bin
Reset: No
Errors:
Wireless clients fail to automatically reconnect when the router is rebooted or power-cycled. This can be a huge problem if you can't get to each client to make it reconnect. Do I need to get a UPS now just for the router? This behavior is new. Tested several times with wireless printers and a client bridge.
Edit: Found the reason. Automatic channel selection fails (again), 20MHz setting attempts to use two channels, and using the wrong combination of channels, too, resulting in zero throughput for some devices... Sigh. Manual channel selection "fixes" this, but forget being a "good neighbor" and letting others use this channel.
Router:WZR-600DHP2 WZR-1750DHP
Errors: Wireless and OpenVPN services do not start automatically after reboot.
Exactly the same error as http://svn.dd-wrt.com/ticket/6017
Similar errors also occur in Kong firmware,
but the problem does not occur because the recovery process starts automatically.
I don't see an error, it is normal in the startup process, that openvpn is restarted. You only show 3 lines that tell us nothing. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Router: Netgear WNDR3400v1
Firmware: dd-wrt.v24-33772_NEWD-2_K3.x_mega-nv64k.bin
Kernel: Linux 3.10.107 #15794
Previous: dd-wrt.v24-33555_NEWD-2_K3.x_mega-nv64k.bin
Status: Bricked
Reset: No, and then yes on follow-up attempts
Errors: Bricked. Resets and downrev'ing with earlier mini builds beforehand did not help like it sometimes does for me.
Joined: 18 Jul 2017 Posts: 45 Location: Wisconsin, USA
Posted: Fri Nov 17, 2017 19:07 Post subject:
Router/Version: Linksys EA6500 v1
Firmware: DD-WRT v3.0-r33772 giga (11/16/17)
Kernel: Linux 3.10.108 #16609 Thu Nov 16 14:22:03 CET 2017 mips
Previous: DD-WRT v3.0-r33555 giga (10/20/17)
Mode/Status: Gateway/AP
Reset: No
Issues/Errors:
IPv6 doesn't appear to be forwarding properly. I didn't notice at first as I had Radvd and Dhcp6s both enabled as such the LAN devices forward properly, but WLAN devices do not seem to be receiving IPv6 addresses.
Disabling Dhcp6s seems to disable IPv6 on LAN devices as well.
I dug deeper with wireshark and the adverts were being broadcast but my android devices still failed to obtain an ipv6 address.
I was able to correct this by using DNSMasq to provide IPv6 addresses with the following commands so far it seems to be working fine.