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 r33678, including k26 (33655) & k24 (33656); use build 33772 or later.
Tickets closed as 'fixed' (Broadcom-related and general):
Important: if any issues are found, please provide log info (GUI syslog, `dmesg`, `cat /var/log/messages`).
Or put in 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 a reply, be sure to include the mode in use (gateway, AP, CB, etc.):
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, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Create a new thread to discuss 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 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
Joined: 18 Jul 2017 Posts: 45 Location: Wisconsin, USA
Posted: Fri Jun 01, 2018 17:41 Post subject:
Router/Version: Linksys EA6500 v1
Firmware: DD-WRT v3.0-r36079 giga ( 06/01/18 )
Kernel: Linux 3.10.108-d2 #19444 Fri Jun 1 13:06:35 CEST 2018 mips
Previous: DD-WRT v3.0-r36006 giga ( 05/23/18 )
Mode/Status: Gateway/AP
Setup: Using IPv6 via DNSMasq, DDNS, & Port Range Forward.
Reset: No
Issues/Errors: None so far
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Fri Jun 01, 2018 18:27 Post subject: Linksys E4200v1
Router/Version: Linksys E4200 v1
Firmware: DD-WRT v3.0-r36079 mega ( 06/01/18 )
Kernel: Linux 3.10.108-d2 #19460 Fri Jun 1 13:23:21 CEST 2018 mips
Previous:DD-WRT v3.0-r36006 mega ( 05/23/18 )
Firmware file used:dd-wrt.v24-36079_NEWD-2_K3.x_mega-e4200.bin
Reset;No
Mode: Gateway/AP
Status: OK
Issues/Errors: None so far, except wireless settings for mode and channel were a little screwy couldn't select anything but auto on 5GHz in NA-Mixed mode, and Mixed only allowed 2.4GHz channel selects (I suspect because I didn't do a soft reset!), will continue to test and check syslog. Figured out my previous problems thanks to jwh7. Intel wireless adapter advanced settings on Win10v1803 were as much culprit as anything else. I guess I didn't find or read anything about that in my previous research, but if anyone has a question, let me know.
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r36079 std ( 06/01/18 )
Kernel: Linux 4.4.134 #3155 SMP Thu May 31 10:03:20 CEST 2018 armv7l
Previous: r36006
Mode/Status: Gateway / working
Reset: no
Issues/Errors: None so far, but the paint's still wet.
Uptime: 39m
Temperatures: CPU 65.8 °C / WL0 46.5 °C / WL1 50.0 °C
Router/Version: Netgear WNDR4000
Firmware: DD-WRT v3.0-r36079 mega ( 06/01/18 )
Kernel: Linux 3.10.108-d2 #19460 Fri Jun 1 13:23:21 CEST 2018 mips
Mode: 2.4 GHz CB to 5 GHz AP + guest VAP
Status: Working fine
Router/Version: Linksys WRT54GSv6
Firmware: DD-WRT v3.0-r36079 micro ( 06/01/18 )
Kernel: Linux 2.4.37 #49626 Fri Jun 1 06:33:33 CEST 2018 mips
Mode: CB
Status: Working fine
Got overzealous and tried to wget/mtd update the 4500v2 since it's in use as a CB for the back yard...it no likey. _________________ #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
Joined: 02 Jan 2015 Posts: 69 Location: Gdansk, Poland
Posted: Fri Jun 01, 2018 22:07 Post subject:
sorry for lame question but i don't have success with update thru web gui interfacie on EA6900 (it's normal? I alway must make update thru recovery mode...)
Router/Version: Buffalo WZR-1750DHP/DHPD Firmware: DD-WRT v3.0-r36079 std (06/01/18 Kernel: Linux 4.4.134 #3155 SMP Thu May 31 10:03:20 CEST 2018 armv7l Previous: BSr34760 Mode/Status: Gateway / WIFI = AP / Seems ok CPU overclocked to 1200mhz from default 800mhz via r33006 Reset: yes via webGUI and via telnet erase nvram Issues/Errors: DNSCrypt V1 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 and unit must be power cycled after flash or the Buffalo logo would blink 3 times every ten seconds or so indicating bad/corrupt flash
Know that all IP and or MAC addresses do coinside with my network but i will change of leave out any IP/MAC addresses for the following requested data. From running dmesg i found out that my router is a prostitute because it states "device br0 entered promiscuous mode"......filing divorce papers soon.
1) cat/var/log/messages
sh: eval: line 1: cat/var/log/messages: not found <-----please correct me if i did the code wrongly
2) dmesg
pci 0000:00:0a.0: [14e4:0510] type 00 class 0xffffff
pci 0000:00:0a.0: reg 0x10: [mem 0x1800b000-0x1800bfff]
pci 0000:00:0a.0: reg 0x14: [mem 0x1800c000-0x1800cfff]
pci 0000:00:0a.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0b.0: [14e4:471a] type 00 class 0x0c0310
pci 0000:00:0b.0: reg 0x10: [mem 0x18022000-0x18022fff]
pci 0000:00:0b.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0b.1: [14e4:471a] type 00 class 0x0c0320
pci 0000:00:0b.1: reg 0x10: [mem 0x18021000-0x18021fff]
pci 0000:00:0b.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0c.0: [14e4:472a] type 00 class 0x0c0330
pci 0000:00:0c.0: reg 0x10: [mem 0x18023000-0x18023fff]
pci 0000:00:0c.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0d.0: [14e4:0503] type 00 class 0xffffff
pci 0000:00:0d.0: reg 0x10: [mem 0x18020000-0x18020fff]
pci 0000:00:0d.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0e.0: [14e4:0506] type 00 class 0xffffff
pci 0000:00:0e.0: reg 0x10: [mem 0x18210000-0x1821ffff]
pci 0000:00:0e.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:0f.0: [14e4:0507] type 00 class 0xffffff
pci 0000:00:0f.0: reg 0x10: [mem 0x18010000-0x18010fff]
pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:10.0: [14e4:0508] type 00 class 0xffffff
pci 0000:00:10.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:11.0: [14e4:0509] type 00 class 0xffffff
pci 0000:00:11.0: reg 0x10: [mem 0x18028000-0x18028fff]
pci 0000:00:11.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:12.0: [14e4:050a] type 00 class 0xffffff
pci 0000:00:12.0: reg 0x10: [mem 0x18029000-0x18029fff]
pci 0000:00:12.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
PCI: Fixing up bus 0 domain 0
PCIE1 link=1
PCIE1 switching to GEN2
PCIE1 link=1
PCI host bridge to bus 0001:00
pci_bus 0001:00: root bus resource [mem 0x08000000-0x0fffffff]
pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0001:00:00.0: [14e4:8011] type 01 class 0x060400
pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
PCI: Fixing up bus 0 domain 1
PCI: bus0: Fast back to back transfers disabled
pci 0001:01:00.0: [14e4:4360] type 00 class 0x028000
pci 0001:01:00.0: reg 0x10: [mem 0x08000000-0x08007fff 64bit]
pci 0001:01:00.0: Max Payload Size set to 512 (was 128, max 512)
pci 0001:01:00.0: supports D1 D2
PCI: Fixing up bus 1 domain 1
PCI: bus1: Fast back to back transfers disabled
pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 01
pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
pci 0001:00:00.0: PCI bridge to [bus 01]
pci 0001:00:00.0: bridge window [mem 0x08000000-0x080fffff]
PCIE2 link=1
PCIE2 switching to GEN2
PCIE2 link=1
PCI host bridge to bus 0002:00
pci_bus 0002:00: root bus resource [mem 0x40000000-0x47ffffff]
pci_bus 0002:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0002:00:00.0: [14e4:8011] type 01 class 0x060400
pci 0002:00:00.0: PME# supported from D0 D3hot D3cold
PCI: Fixing up bus 0 domain 2
PCI: bus0: Fast back to back transfers disabled
pci 0002:01:00.0: [14e4:4331] type 00 class 0x028000
pci 0002:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
pci 0002:01:00.0: can't set Max Payload Size to 512; if necessary, use "pci=pcie_bus_safe" and report a bug
pci 0002:01:00.0: supports D1 D2
PCI: Fixing up bus 1 domain 2
PCI: bus1: Fast back to back transfers disabled
pci_bus 0002:01: busn_res: [bus 01-ff] end is updated to 01
pci_bus 0002:00: busn_res: [bus 00-ff] end is updated to 01
pci 0002:00:00.0: BAR 8: assigned [mem 0x40000000-0x400fffff]
pci 0002:01:00.0: BAR 0: assigned [mem 0x40000000-0x40003fff 64bit]
pci 0002:00:00.0: PCI bridge to [bus 01]
pci 0002:00:00.0: bridge window [mem 0x40000000-0x400fffff]
PCIE3 link=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
io scheduler noop registered (default)
io scheduler cfq registered
serial8250_init
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
console [ttyS0] disabled
serial8250.0: ttyS0 at MMIO 0x18000300 (irq = 117, base_baud = 6250000) is a 16550
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x18000400 (irq = 117, base_baud = 6250000) is a 16550
brd: module loaded
loop: module loaded
Boot partition size = 2097152(0x200000)
Creating 3 MTD partitions on "bcmsflash":
0x000000000000-0x000000200000 : "boot"
mtd: partition "boot" extends beyond the end of device "bcmsflash" -- size truncated to 0x100000
0x0000000f0000-0x000000100000 : "nvram_cfe"
0x0000000e0000-0x0000000f0000 : "nvram"
Found a Esmt NAND flash:
Total size: 128MB
Block size: 128KB
Page Size: 2048B
OOB Size: 64B
Sector size: 512B
Spare size: 16B
ECC level: 8 (8-bit)
Device ID: 0x92 0xf1 0x80 0x95 0x40 0x7f
lookup_nflash_rootfs_offset: offset = 0x0 size = 0x2000000, 0x20000
found TRX Header on nflash!
nflash: squash filesystem with lzma found at block 13
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "linux"
0x0000001a0000-0x000002000000 : "rootfs"
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
GACT probability NOT on
Mirror/redirect action on
Simple TC action Loaded
netem: version 1.3
u32 classifier
Performance counters on
input device check on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (8036 buckets, 32144 max)
nf_conntrack_rtsp v0.7 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.7 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Registering SWP/SWPB emulation handler
found cfe nvram
check if nvram copy is required CFE Size is 65536
nvram copy magic is 48534C46
max nvram space = 131072
read 65536 bytes to offset 0
Key type encrypted registered
Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
nand: Eon NAND 128MiB 3,3V 8-bit
nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Spare area=64 eccbytes 56, ecc bytes located at:
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
Available 7 bytes at (off,len):
(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)
Scanning device for bad blocks
Bad eraseblock 1023 at 0x000007fe0000
Options: NO_SUBPAGE_WRITE,
Creating 1 MTD partitions on "brcmnand":
0x000002000000-0x000008000000 : "ddwrt"
VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
Freeing unused kernel memory: 344K
et: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
et_module_init: passivemode set to 0x0
et_module_init: txworkq set to 0x0
et_module_init: et_txq_thresh set to 0x400
et_module_init: et_rxlazy_timeout set to 0x3e8
et_module_init: et_rxlazy_framecnt set to 0x20
et_module_init: et_rxlazy_dyn_thresh set to 0
ET Corerev 5
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
roboswitch: Probing device 'eth0'
roboswitch: trying a 53011! at eth0
detected CPU Port is 5
roboswitch: found a 53011! at eth0
detected CPU Port is 5
wl_module_init: passivemode set to 0x0
wl_module_init: txworkq set to 0x0
eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
PCI: Enabling device 0002:01:00.0 (0140 -> 0142)
eth2: Broadcom BCM4331 802.11 Wireless Controller 7.14.89.21 (r524987)
eth0: mixed HW and IP checksum settings.
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device eth1 entered promiscuous mode
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entered forwarding state
br0: port 3(eth2) entered forwarding state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device vlan2 entered promiscuous mode
IMQ: use 2 as queue number
IMQ driver loaded successfully. (numdevs = 2, numqueues = 2, imq_dev_accurate_stats = 1)
Hooking IMQ before NAT on PREROUTING.
Hooking IMQ after NAT on POSTROUTING.
random: dnsmasq: uninitialized urandom read (128 bytes read, 58 bits of entropy available)
random: dnsmasq: uninitialized urandom read (48 bytes read, 58 bits of entropy available)
device vlan2 left promiscuous mode
random: dnsmasq: uninitialized urandom read (128 bytes read, 66 bits of entropy available)
random: dnsmasq: uninitialized urandom read (48 bytes read, 66 bits of entropy available)
random: httpd: uninitialized urandom read (32 bytes read, 71 bits of entropy available)
IMQ driver unloaded successfully.
IMQ: use 2 as queue number
IMQ driver loaded successfully. (numdevs = 2, numqueues = 2, imq_dev_accurate_stats = 1)
Hooking IMQ before NAT on PREROUTING.
Hooking IMQ after NAT on POSTROUTING.
random: scc: uninitialized urandom read (127 bytes read, 83 bits of entropy available)
random: scc: uninitialized urandom read (1024 bytes read, 83 bits of entropy available)
random: scc: uninitialized urandom read (127 bytes read, 89 bits of entropy available)
random: scc: uninitialized urandom read (1024 bytes read, 89 bits of entropy available)
random: nas: uninitialized urandom read (16 bytes read, 101 bits of entropy available)
random: nonblocking pool is initialized
br0: port 1(vlan1) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 3(eth2) entered forwarding state
Got overzealous and tried to wget/mtd update the 4500v2 since it's in use as a CB for the back yard...it no likey.
....
Whoops.
Well, all part of the fun...see below
adasch wrote:
sorry for lame question but i don't have success with update thru web gui interfacie on EA6900 (it's normal? I alway must make update thru recovery mode...)
From running dmesg i found out that my router is a prostitute because it states "device br0 entered promiscuous mode"......filing divorce papers soon.
C'mon now, just cuz your router is promiscuous doesn't make it a prostitute. Unless it is selling itself to other modems...in which case your ISP will be hella pissed. Or maybe your router identifies as Nelly Furtado and/or Timbaland?
Router/Version: Netgear WNDR4500v2
Firmware: DD-WRT v3.0-r36079 giga ( 06/01/18 )
Kernel: Linux 3.10.108-d2 #19444 Fri Jun 1 13:06:35 CEST 2018 mips
Mode: 2.4 GHz CB to 5 GHz AP + guest VAP
Status: Reset? Um, ya. After the aforementioned `mtd` fail and subsequent numerous reset and TFTP attempts... I remembered how much I love the simplicity of Netgear case design, and had serial hooked up and flashed back to latest OEM in 5 minutes. Then, eff it, after all this I'll try flashing straight to latest K3X...no problem diggity.
Then, I did a `erase nvram` (backing up and copying the parameters off before and after for later review if needed), and noticed it rebooted twice (and I'll reiterate how effing slow this thing is to boot, thanks to it's NAND CRC check at boot*), but still came back fine and got it set back up as before. That's the last time (maybe...) I try `mtd write` w/o a valid `mtd unlock linux` response (just `write {file} linux` works though). Note to self: if the latter fails, use the device node directly, i.e. `mtd unlock /dev/mtd1` !!!
*PuTTY wrote:
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes
Device eth0: hwaddr C4-04-15-52-78-A2, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Checking crc...
And then wait a several minutes. _________________ #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 Nov 28, 2018 15:50; edited 1 time in total
I have noticed that erase nvram gives a different result via telnet than in the WebGUI, in the GUI it just clears most settings and reboots but the overclock stays intact while via telnet, it erases everything, including the overclock, i don't like that.
