To How did you reset? If not via telnet/ssh `erase nvram`, then try that,clarify, you had ran `erase nvram` from a command line, right? Did you try doing this in k2.6 (then manually set up) first? I've seen k3x do that before on my WNDR's, but `erase nvram` fixes it. However, since your router isn't properly recognized (assuming based on previous reports of the model showing up as the original default WRT54 series) then it's likely due to not clearing everything. I'll ask BS about it.
Is there no way to erease the whole nvram before flashing K3.X build? Or reset Wlan-Passoword..? Or get ports working with one of the builds (K2.6 or K3.X)
Quote:
Regarding VAPs, BS said that r36341 is to address those issues. Once a test build is available w/ it I'll try it out and report back.
Is there no way to erease the whole nvram before flashing K3.X build? Or reset Wlan-Passoword..? Or get ports working with one of the builds (K2.6 or K3.X)
My first reply to you said to run `erase nvram` from k26 telnet, then reboot and manually setup. Actually if you run `erase nvram && reboot` it will reboot autommatically. As I last said though, k3x probably isn't erasing everything cuz it's not recognizing the device properly.
You can manually set parameters too via:
`nvram {parameter}={value}`
To check all parameters, use `nvram show`. Add `| grep {string}` as needed. Rinse, lather, and repeat. _________________ #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: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Fri Jul 20, 2018 7:44 Post subject:
Router: 2x Linksys E3000
File: dd-wrt.v24-36330_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-36006_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d3 #20116 Mon Jul 16 18:34:44 CEST 2018 mips
Mode: Both client bridges
Status: Working so far, much better speedtests than my previous build. We get all the speed we pay for.
Router: Trendnet TEW811DRU
File: DD-WRT v3.0-r36330 mini (07/16/1 Kernel: Linux 4.4.140 #3519 Mon Jul 16 12:20:11 CEST 2018 armv7l
Mode: AC only client bridge
Status: No problems so far. Speed is pretty decent, overall seems like a good build. _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Fri Jul 20, 2018 15:43 Post subject:
spurgeonspooner wrote:
I've always just used the build from the router database, and been disappointed. I had no idea the community here had newer builds.
After reading through the peacock thread, I'm still a bit confused. Is this a recommended build for the E2500?
Build threads are posted when a public beta / test build is released. It's up to the user whether or not they take the chance of flashing their device and bricking it, and if they don't brick it, testing to see what does and doesn't work, etc. At least that's been my understanding
Try this one make sure the file is always under 7995392 bytes or less in future builds. If you do not care for VAP or Virtual Access Point. This should function fine as a router with AP like other routers on the market do. Without major issues. The router database is totally outdated.
Fair warning. The 5 GHz radio does not function* on this device when running dd-wrt because the 5 GHz radio USB interface (not PCI) 'brcmfmac' driver does not support the BCM43236 rev2 chip, only the rev3 'B' variant.
Try this one make sure the file is always under 7995392 bytes or less in future builds.
Hi, to help myself understand the layout of the FTP site and the discussion of k3.x and k2.6 builds, please tell me if I understand correctly: my device (Asus AC-68U) has its own folder in the FTP tree, and that build works fine for me and reports a k4.x kernel. The fact that it has a broadcom chip *doesn't* mean that I can consider using builds form the broadcom* folders, because those builds are for older or smaller devices that can't handle the larger flashes of k4.x roms. So I can ignore discussions of k3.x and k2.x. Right? :-)
Try this one make sure the file is always under 7995392 bytes or less in future builds.
Hi, to help myself understand the layout of the FTP site and the discussion of k3.x and k2.6 builds, please tell me if I understand correctly: my device (Asus AC-68U) has its own folder in the FTP tree, and that build works fine for me and reports a k4.x kernel. The fact that it has a broadcom chip *doesn't* mean that I can consider using builds form the broadcom* folders, because those builds are for older or smaller devices that can't handle the larger flashes of k4.x roms. So I can ignore discussions of k3.x and k2.x. Right?
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Sun Jul 22, 2018 1:30 Post subject: Re: Linksys E4200 v1
kernel-panic69 wrote:
Router/Version: Linksys E4200 v1
Firmware: DD-WRT v3.0-r36330 mega ( 07/16/18 )
Kernel: Linux 3.10.108-d3 #20116 Mon Jul 16 18:34:44 CEST 2018 mips
Previous: DD-WRT v3.0-r36168 mega ( 06/20/18 )
Firmware file used: dd-wrt.v24-36330_NEWD-2_K3.x_mega-e4200.bin
Reset; Yes; Reset via webUI (reboot), Firmware upgrade (httpd crash!), 30/30/30 (reboot), configured previous settings manually (reboot)
Mode: Gateway/AP
Status: OK
Uptime:~3 days, 13:03 hours* Issues/Errors:
Woke up to no music, and checked syslog, and the garbage is back that preceded the previous nas crash issue. Guess I need to enable a remote syslog server to catch more info than I did, but.
EDIT: Caught a full loop and a partial that stopped at line #487 (due to me hitting some key(s) that stopped the feed, it is in a continual loop*). Wondering if this is related to ntp cyclic update or GTK re-key. This behavior was quieted when I set GTK re-key interval to 0 previously.
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Sun Jul 22, 2018 10:21 Post subject: DD-WRT BS build 36333 and Asus RT-N18U
Router/Version: Asus RT-N18U
Firmware: DD-WRT v3.0-r36330 std (07/16/18)
Kernel: Linux 4.4.140 #3520 Mon Jul 16 12:22:40 CEST 2018 armv7l
Previous: DD-WRT v3.0-r36168 std (06/20/18)
Mode: Access Point (AP, not using IPv6, VPN, NAS nor USB)
Status: Working, no major problems
Reset: NO reset during firmware upgrade
1. No LAN LEDs... all off though there were physical cables.
2. Error(s) logged:
Code:
grep -i err /var/log/messages
Jan 1 00:00:13 DD-WRT kern.err kernel: bcmsflash: found no supported devices
Jul 23 09:35:26 DD-WRT daemon.err httpd[959]: Request Error Code 404: File style/elegant/logo.png not found.
Jul 23 09:35:27 DD-WRT daemon.err httpd[959]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jul 23 09:35:31 DD-WRT daemon.err httpd[959]: Request Error Code 404: File style/elegant/logo.png not found.
Jul 23 09:35:33 DD-WRT daemon.err httpd[959]: Request Error Code 404: File style/elegant/logo.png not found.
3. Warning(s) logged:
Code:
grep -i warn /var/log/messages | grep -v DROP
Jan 1 00:00:13 DD-WRT kern.warn kernel: Sector size: 512B
Jan 1 00:00:13 DD-WRT kern.warn kernel: Spare size: 16B
Jan 1 00:00:13 DD-WRT kern.warn kernel: ECC level: 8 (8-bit)
Jan 1 00:00:13 DD-WRT kern.warn kernel: Device ID: 0x 1 0xf1 0x 0 0x1d 0x 1 0xf1
Jan 1 00:00:13 DD-WRT kern.warn kernel: PCI: no core
Jan 1 00:00:13 DD-WRT kern.warn kernel: PCI: no core
Jan 1 00:00:13 DD-WRT kern.warn kernel: PCI: Fixing up bus 0 domain 0
Jan 1 00:00:13 DD-WRT kern.warn kernel: PCI: Fixing up bus 0 domain 1
Jan 1 00:00:13 DD-WRT kern.warn kernel: PCI: Fixing up bus 1 domain 1
Jan 1 00:00:13 DD-WRT kern.warn kernel: Boot partition size = 524288(0x80000)
Jan 1 00:00:13 DD-WRT kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x200000 size = 0x1e00000, 0x20000
Jan 1 00:00:13 DD-WRT kern.warn kernel: nf_conntrack_rtsp v0.7 loading
Jan 1 00:00:13 DD-WRT kern.warn kernel: nf_nat_rtsp v0.7 loading
Jan 1 00:00:13 DD-WRT kern.warn kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan 1 00:00:13 DD-WRT 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 DD-WRT kern.warn kernel: Available 7 bytes at (off,len):
Jan 1 00:00:13 DD-WRT 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 DD-WRT kern.warn kernel: Bad eraseblock 356 at 0x000002c80000
Jan 1 00:00:13 DD-WRT kern.warn kernel: Options: NO_SUBPAGE_WRITE,
Jan 1 00:00:13 DD-WRT kern.warn kernel: et: module license 'Proprietary' taints kernel.
Jan 1 00:00:13 DD-WRT kern.warn kernel: Disabling lock debugging due to kernel taint
Jan 1 00:00:13 DD-WRT kern.warn kernel: et_module_init: passivemode set to 0x0
Jan 1 00:00:13 DD-WRT kern.warn kernel: et_module_init: txworkq set to 0x0
Jan 1 00:00:13 DD-WRT kern.warn kernel: et_module_init: et_txq_thresh set to 0x400
Jan 1 00:00:13 DD-WRT kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan 1 00:00:13 DD-WRT kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan 1 00:00:13 DD-WRT kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan 1 00:00:13 DD-WRT kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
Jan 1 00:00:13 DD-WRT kern.warn kernel: wl_module_init: passivemode set to 0x0
Jan 1 00:00:13 DD-WRT kern.warn kernel: wl_module_init: txworkq set to 0x0
Jan 1 00:00:13 DD-WRT kern.warn kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
Jan 1 00:00:13 DD-WRT kern.warn kernel: eth0: mixed HW and IP checksum settings.
Jan 1 00:00:13 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Jan 1 00:00:13 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Jan 1 00:00:15 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Jan 1 00:00:16 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Jan 1 00:00:17 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Jan 1 00:00:18 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Jul 23 08:58:59 DD-WRT kern.warn kernel: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs
Other users' comments:
- WiFi broken in k3.x editions since build 35531 for modes other than AP?
- 5GHz problem can be solved by adding delay (boot wait?) in init process?
- Setting WPA re-key interval if not 99999 and rebooting router daily fixed nas (network authentication service) crash problems?
- Setting WPA re-key interval to 0 could prevent wifi clients from disconnecting?
- VAP still not fixed by this build 36333
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 (also something related to blank Source Net?)
e. The "Source Net" field in Port-Forwarding screen displayd blank field as "¸ÖÁv",
from builds 32667 to 32767. Possibly null-pointer assignment?
f. Blank Source Net in Port Forwarding cripped WAN in builds 35831-35874! Needed to be "0.0.0.0/0" or no internet!
g. Running "cat /proc/mtd" in Administration -> Commands for builds before 35916 didn't escape HTML special characters.
h. K3X BS Builds 36233 and 36242 might brick your routers (Kernel CPU patch went kaboom?). And VAP was not working. Bypass them!
speedtest.net result for DD-WRT BS build 36333 and Asus RT-N18U.png
Description:
speedtest.net result for DD-WRT BS build 36333 and Asus RT-N18U (2nd try)
Filesize:
14.27 KB
Viewed:
2742 Time(s)
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
The fact that it has a broadcom chip *doesn't* mean that I can consider using builds form the broadcom* folders, because those builds are for older or smaller devices that can't handle the larger flashes of k4.x roms. So I can ignore discussions of k3.x and k2.x. Right?
Joined: 11 Apr 2010 Posts: 311 Location: San Francisco Bay Area
Posted: Tue Jul 24, 2018 22:31 Post subject:
I have an R7000 with VAPs for my Guest network on both the 2.4Ghz and 5Ghz radios and have problems with physical 2.4Ghz connectivity to my main network. Is there a recent recommended BS release that does not have this bug?
I have an R7000 with VAPs for my Guest network on both the 2.4Ghz and 5Ghz radios and have problems with physical 2.4Ghz connectivity to my main network. Is there a recent recommended BS release that does not have this bug?
Last good normal build for bcm VAPs is 36168, at least for k3x builds (both NOR and NAND flash). Latest (not public) test build (r36381) has VAPs working after restarting wlconf, but not by default, so BS is getting closer...but he's been focused on non-bcm issues atm. _________________ #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
