DD-WRT :: View topic - New Build 36168 (BS): 06-20-2018-r36168

New Build 36168 (BS): 06-20-2018-r36168

DD-WRT Forum Index -> Broadcom SoC based Hardware

Goto page Previous 1, 2, 3

View previous topic :: View next topic

Author

Message

kernel-panic69
DD-WRT Guru

Joined: 08 May 2018
Posts: 14215
Location: Texas, USA

Posted: Sun Jun 24, 2018 18:50 Post subject: Re: Linksys E4200 v1

kernel-panic69 wrote:

Router/Version: Linksys E4200 v1
Firmware: DD-WRT v3.0-r36168 mega ( 06/20/18 )
Kernel: Linux 3.10.108-d2 #19640 Wed Jun 20 18:06:53 CEST 2018 mips
Previous: DD-WRT v3.0-r36154 mega ( 06/16/18 )
Firmware file used:dd-wrt.v24-36168_NEWD-2_K3.x_mega-e4200.bin
Reset;No
Mode: Gateway/AP
Status: OK
Issues/Errors:

Uptime is around 3 days, 22:04 hours. Not entirely sure what to make of the following syslog excerpts, as I have not been doing any changes or applying settings on the fly since it's been up:

Code:

Jun 21 11:41:53 DD-WRT daemon.debug ntpclient[13379]: Connecting to us.pool.ntp.org [166.70.136.35] ...
Jun 21 11:41:53 DD-WRT daemon.info ntpclient[13379]: Time set from us.pool.ntp.org [166.70.136.35].
Jun 21 11:41:53 DD-WRT daemon.info process_monitor[1538]: cyclic NTP Update success (servers us.pool.ntp.org)
Jun 21 12:01:42 DD-WRT daemon.info httpd[1382]: Authentication fail
Jun 21 12:01:42 DD-WRT daemon.err httpd[1382]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jun 21 12:26:34 DD-WRT user.info : nas : NAS daemon successfully stopped
Jun 21 12:26:34 DD-WRT kern.info kernel: br0: port 3(eth2) entered disabled state
Jun 21 12:26:34 DD-WRT kern.info kernel: br0: port 2(eth1) entered disabled state
Jun 21 12:26:34 DD-WRT kern.info kernel: br0: port 1(vlan1) entered disabled state
Jun 21 12:26:34 DD-WRT user.info : interface deleted successfully
Jun 21 12:26:34 DD-WRT kern.info kernel: device vlan1 left promiscuous mode
Jun 21 12:26:34 DD-WRT kern.info kernel: br0: port 1(vlan1) entered disabled state
Jun 21 12:26:34 DD-WRT user.info : bridge deleted successfully
Jun 21 12:26:34 DD-WRT user.info : interface deleted successfully
Jun 21 12:26:34 DD-WRT kern.info kernel: device eth1 left promiscuous mode
Jun 21 12:26:34 DD-WRT kern.info kernel: br0: port 2(eth1) entered disabled state
Jun 21 12:26:34 DD-WRT user.info : interface deleted successfully
Jun 21 12:26:34 DD-WRT kern.warn kernel: Hooks already unregistered
Jun 21 12:26:34 DD-WRT kern.warn kernel: Hooks already unregistered
Jun 21 12:26:34 DD-WRT kern.info kernel: device eth2 left promiscuous mode
Jun 21 12:26:34 DD-WRT kern.info kernel: br0: port 3(eth2) entered disabled state
Jun 21 12:26:34 DD-WRT user.info : bridge deleted successfully
Jun 21 12:26:34 DD-WRT kern.warn kernel: Interface br0 doesn't exist
Jun 21 12:26:34 DD-WRT kern.warn kernel: Interface br0 doesn't exist
Jun 21 12:26:34 DD-WRT user.info : bridge added successfully
Jun 21 12:26:34 DD-WRT user.info : bridge added successfully
Jun 21 12:26:34 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jun 21 12:26:34 DD-WRT user.info : interface added successfully
Jun 21 12:26:34 DD-WRT kern.info kernel: device vlan1 entered promiscuous mode
Jun 21 12:26:34 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jun 21 12:26:34 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jun 21 12:26:35 DD-WRT user.info : interface added successfully
Jun 21 12:26:35 DD-WRT kern.info kernel: device eth1 entered promiscuous mode
Jun 21 12:26:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jun 21 12:26:35 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jun 21 12:26:35 DD-WRT user.info : interface added successfully
Jun 21 12:26:35 DD-WRT kern.info kernel: device eth2 entered promiscuous mode
Jun 21 12:26:35 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jun 21 12:26:35 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jun 21 12:26:35 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jun 21 12:26:35 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jun 21 12:26:35 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jun 21 12:26:36 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jun 21 12:26:37 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jun 21 12:26:37 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jun 21 12:26:38 DD-WRT user.info : NAS : NAS lan (wl0 interface) successfully started
Jun 21 12:26:38 DD-WRT user.info : NAS : NAS lan (wl1 interface) successfully started

Code:

Jun 21 18:41:55 DD-WRT daemon.debug ntpclient[23100]: Connecting to us.pool.ntp.org [173.230.144.109] ...
Jun 21 18:41:55 DD-WRT daemon.info ntpclient[23100]: Time set from us.pool.ntp.org [173.230.144.109].
Jun 21 18:41:55 DD-WRT daemon.info process_monitor[1538]: cyclic NTP Update success (servers us.pool.ntp.org)
Jun 21 18:51:43 DD-WRT user.info : nas : NAS daemon successfully stopped
Jun 21 18:51:43 DD-WRT kern.info kernel: br0: port 3(eth2) entered disabled state
Jun 21 18:51:43 DD-WRT kern.info kernel: br0: port 2(eth1) entered disabled state
Jun 21 18:51:43 DD-WRT kern.info kernel: br0: port 1(vlan1) entered disabled state
Jun 21 18:51:43 DD-WRT user.info : bridge deleted successfully
Jun 21 18:51:43 DD-WRT kern.warn kernel: Hooks already unregistered
Jun 21 18:51:43 DD-WRT kern.warn kernel: Hooks already unregistered
Jun 21 18:51:43 DD-WRT kern.info kernel: device eth2 left promiscuous mode
Jun 21 18:51:43 DD-WRT kern.info kernel: br0: port 3(eth2) entered disabled state
Jun 21 18:51:43 DD-WRT kern.info kernel: device eth1 left promiscuous mode
Jun 21 18:51:43 DD-WRT kern.info kernel: br0: port 2(eth1) entered disabled state
Jun 21 18:51:43 DD-WRT kern.info kernel: device vlan1 left promiscuous mode
Jun 21 18:51:43 DD-WRT kern.info kernel: br0: port 1(vlan1) entered disabled state
Jun 21 18:51:43 DD-WRT user.info : interface deleted successfully
Jun 21 18:51:43 DD-WRT kern.warn kernel: Interface br0 doesn't exist
Jun 21 18:51:43 DD-WRT user.info : interface deleted successfully
Jun 21 18:51:43 DD-WRT kern.warn kernel: Interface br0 doesn't exist
Jun 21 18:51:43 DD-WRT user.info : interface deleted successfully
Jun 21 18:51:43 DD-WRT user.info : bridge added successfully
Jun 21 18:51:43 DD-WRT kern.warn kernel: Interface br0 doesn't exist
Jun 21 18:51:43 DD-WRT user.info : bridge added successfully
Jun 21 18:51:43 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jun 21 18:51:43 DD-WRT user.info : interface added successfully
Jun 21 18:51:43 DD-WRT kern.info kernel: device vlan1 entered promiscuous mode
Jun 21 18:51:43 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jun 21 18:51:43 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jun 21 18:51:45 DD-WRT user.info : interface added successfully
Jun 21 18:51:45 DD-WRT kern.info kernel: device eth1 entered promiscuous mode
Jun 21 18:51:45 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jun 21 18:51:45 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jun 21 18:51:45 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jun 21 18:51:47 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jun 21 18:51:48 DD-WRT user.info : interface added successfully
Jun 21 18:51:48 DD-WRT kern.info kernel: device eth2 entered promiscuous mode
Jun 21 18:51:48 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jun 21 18:51:48 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jun 21 18:51:48 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jun 21 18:51:48 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jun 21 18:51:48 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jun 21 18:51:48 DD-WRT user.info : udhcpd : DHCP daemon successfully stopped
Jun 21 18:51:48 DD-WRT user.info : udhcpd : udhcp daemon successfully started
Jun 21 18:51:50 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jun 21 18:51:50 DD-WRT user.info : httpd : http daemon successfully stopped
Jun 21 18:51:50 DD-WRT daemon.info httpd[1382]: httpd server shutdown
Jun 21 18:51:51 DD-WRT user.info : NAS : NAS lan (wl0 interface) successfully started
Jun 21 18:51:51 DD-WRT user.info : NAS : NAS lan (wl1 interface) successfully started
Jun 21 18:51:52 DD-WRT user.info : httpd : http daemon hanging, send SIGKILL
Jun 21 18:51:52 DD-WRT daemon.info httpd[23755]: httpd server started at port 80

Code:

Jun 22 01:41:57 DD-WRT daemon.debug ntpclient[2779]: Connecting to us.pool.ntp.org [97.107.128.165] ...
Jun 22 01:41:57 DD-WRT daemon.info ntpclient[2779]: Time set from us.pool.ntp.org [97.107.128.165].
Jun 22 01:41:57 DD-WRT daemon.info process_monitor[1538]: cyclic NTP Update success (servers us.pool.ntp.org)
Jun 22 02:10:28 DD-WRT user.info : nas : NAS daemon successfully stopped
Jun 22 02:10:28 DD-WRT kern.info kernel: br0: port 3(eth2) entered disabled state
Jun 22 02:10:28 DD-WRT kern.info kernel: br0: port 2(eth1) entered disabled state
Jun 22 02:10:28 DD-WRT kern.info kernel: br0: port 1(vlan1) entered disabled state
Jun 22 02:10:28 DD-WRT user.info : bridge deleted successfully
Jun 22 02:10:28 DD-WRT kern.warn kernel: Hooks already unregistered
Jun 22 02:10:28 DD-WRT kern.warn kernel: Hooks already unregistered
Jun 22 02:10:28 DD-WRT kern.info kernel: device eth2 left promiscuous mode
Jun 22 02:10:28 DD-WRT kern.info kernel: br0: port 3(eth2) entered disabled state
Jun 22 02:10:28 DD-WRT kern.info kernel: device eth1 left promiscuous mode
Jun 22 02:10:28 DD-WRT kern.info kernel: br0: port 2(eth1) entered disabled state
Jun 22 02:10:28 DD-WRT kern.info kernel: device vlan1 left promiscuous mode
Jun 22 02:10:28 DD-WRT kern.info kernel: br0: port 1(vlan1) entered disabled state
Jun 22 02:10:28 DD-WRT user.info : interface deleted successfully
Jun 22 02:10:28 DD-WRT kern.warn kernel: Interface br0 doesn't exist
Jun 22 02:10:28 DD-WRT user.info : interface deleted successfully
Jun 22 02:10:28 DD-WRT kern.warn kernel: Interface br0 doesn't exist
Jun 22 02:10:28 DD-WRT user.info : interface deleted successfully
Jun 22 02:10:28 DD-WRT user.info : bridge added successfully
Jun 22 02:10:28 DD-WRT kern.warn kernel: Interface br0 doesn't exist
Jun 22 02:10:28 DD-WRT user.info : bridge added successfully
Jun 22 02:10:28 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jun 22 02:10:29 DD-WRT user.info : interface added successfully
Jun 22 02:10:29 DD-WRT kern.info kernel: device vlan1 entered promiscuous mode
Jun 22 02:10:29 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jun 22 02:10:29 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jun 22 02:10:29 DD-WRT user.info : interface added successfully
Jun 22 02:10:29 DD-WRT kern.info kernel: device eth1 entered promiscuous mode
Jun 22 02:10:29 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jun 22 02:10:29 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jun 22 02:10:29 DD-WRT user.info : interface added successfully
Jun 22 02:10:29 DD-WRT kern.info kernel: device eth2 entered promiscuous mode
Jun 22 02:10:29 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jun 22 02:10:29 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jun 22 02:10:29 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jun 22 02:10:29 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jun 22 02:10:29 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jun 22 02:10:30 DD-WRT user.info : udhcpd : DHCP daemon successfully stopped
Jun 22 02:10:30 DD-WRT user.info : udhcpd : udhcp daemon successfully started
Jun 22 02:10:31 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jun 22 02:10:31 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jun 22 02:10:31 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jun 22 02:10:32 DD-WRT user.info : httpd : http daemon successfully stopped
Jun 22 02:10:32 DD-WRT daemon.info httpd[23763]: httpd server shutdown
Jun 22 02:10:33 DD-WRT user.info : NAS : NAS lan (wl0 interface) successfully started
Jun 22 02:10:33 DD-WRT user.info : NAS : NAS lan (wl1 interface) successfully started
Jun 22 02:10:34 DD-WRT user.info : httpd : http daemon hanging, send SIGKILL
Jun 22 02:10:34 DD-WRT daemon.info httpd[3347]: httpd server started at port 80
Jun 22 02:41:57 DD-WRT daemon.debug ntpclient[4381]: Connecting to us.pool.ntp.org [63.211.239.58] ...
Jun 22 02:41:57 DD-WRT daemon.info ntpclient[4381]: Time set from us.pool.ntp.org [63.211.239.58].
Jun 22 02:41:57 DD-WRT daemon.info process_monitor[1538]: cyclic NTP Update success (servers us.pool.ntp.org)

Code:

Jun 23 17:42:12 DD-WRT daemon.debug ntpclient[25768]: Connecting to us.pool.ntp.org [74.117.214.3] ...
Jun 23 17:42:12 DD-WRT daemon.info ntpclient[25768]: Time set from us.pool.ntp.org [74.117.214.3].
Jun 23 17:42:12 DD-WRT daemon.info process_monitor[1538]: cyclic NTP Update success (servers us.pool.ntp.org)
Jun 23 18:12:08 DD-WRT user.info : udhcpd : DHCP daemon successfully stopped
Jun 23 18:12:08 DD-WRT user.info : udhcpd : udhcp daemon successfully started
Jun 23 18:12:08 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
Jun 23 18:12:08 DD-WRT user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jun 23 18:12:09 DD-WRT user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jun 23 18:12:09 DD-WRT user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jun 23 18:12:09 DD-WRT user.info : vpn modules : nf_nat_pptp successfully loaded
Jun 23 18:12:09 DD-WRT user.info : process_monitor : Process Monitor successfully stopped
Jun 23 18:12:09 DD-WRT user.info : process_monitor successfully started
Jun 23 18:12:09 DD-WRT user.info : wland : WLAN daemon successfully stopped
Jun 23 18:12:09 DD-WRT user.info : wland : WLAN daemon successfully started
Jun 23 18:12:09 DD-WRT user.info : WAN is up. IP: 192.168.0.4
Jun 23 18:12:09 DD-WRT daemon.debug ntpclient[26405]: Connecting to us.pool.ntp.org [199.223.248.98] ...
Jun 23 18:12:09 DD-WRT daemon.info ntpclient[26405]: Time set from us.pool.ntp.org [199.223.248.98].
Jun 23 18:12:09 DD-WRT daemon.info process_monitor[26404]: cyclic NTP Update success (servers us.pool.ntp.org)

Sponsor

mwchang
DD-WRT Guru

Joined: 26 Mar 2013
Posts: 1856
Location: Hung Hom, Hong Kong

Posted: Tue Jun 26, 2018 8:33 Post subject: Re: Linksys E4200 v1

kernel-panic69 wrote:

Uptime is around 3 days, 22:04 hours. Not entirely sure what to make of the following syslog excerpts, as I have not been doing any changes or applying settings on the fly since it's been up:
...

Unless you had something to debug, one could ignore all *.info messages in syslog, maybe by

Code:

grep -v ".info" /var/log/messages

Option "-v" for grep means "not".
_________________
Router: Asus RT-N18U (rev. A1)

Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!

Facebook: https://www.facebook.com/changmanwai
Website: https://sites.google.com/site/changmw
SETI@Home profile: http://setiathome.berkeley.edu/view_profile.php?userid=211832
GitHub: https://github.com/changmw/changmw

kernel-panic69
DD-WRT Guru

Joined: 08 May 2018
Posts: 14215
Location: Texas, USA

Posted: Tue Jun 26, 2018 14:03 Post subject: Re: Linksys E4200 v1

mwchang wrote:

kernel-panic69 wrote:

Uptime is around 3 days, 22:04 hours. Not entirely sure what to make of the following syslog excerpts, as I have not been doing any changes or applying settings on the fly since it's been up:
...

Unless you had something to debug, one could ignore all *.info messages in syslog, maybe by

Code:

grep -v ".info" /var/log/messages

Option "-v" for grep means "not".

Not entirely what I was getting at. Networking was cycling without me doing any network-related config changes and applying settings (that I recall)... I've rebooted since then, and currently at 1 Day, ~18 hours uptime with no repeat occurrences. Could've just been an anomaly, of course, I may have done some things and forgot I had.

Last edited by kernel-panic69 on Tue Jun 26, 2018 16:30; edited 1 time in total

mama_mia
DD-WRT Novice

Joined: 15 Aug 2012
Posts: 44

Posted: Tue Jun 26, 2018 15:21 Post subject: Re: Linksys E4200 v1

kernel-panic69 wrote:

Router/Version: Linksys E4200 v1
...

Do you have a stable connection with that device?
I have a E4200 v1 too but since about a year ago it began to restart wan every 5 minutes.

You can see it there:
https://pastebin.com/craviRBS

I tried everything.
- Dirty flash on top of a older build;
- 30/30/30 before, then flash, then 30/30/30 again;
- reset factory by software;

Nothing helps, it keeps doing that. I need to go back to 2016 or early 2017 builds to have a stable connection.

kernel-panic69
DD-WRT Guru

Joined: 08 May 2018
Posts: 14215
Location: Texas, USA

Posted: Tue Jun 26, 2018 15:53 Post subject: Re: Linksys E4200 v1

mama_mia wrote:

kernel-panic69 wrote:

Router/Version: Linksys E4200 v1
...

Wireless*/wland I haven't had much issue with either, except for the wireless WPA2/GTK re-key interval seeming to break Windows / wi-fi. 35531; 35927 and up have been pretty good for me otherwise. Which build are you currently using?

mama_mia
DD-WRT Novice

Joined: 15 Aug 2012
Posts: 44

Posted: Tue Jun 26, 2018 16:01 Post subject: Re: Linksys E4200 v1

kernel-panic69 wrote:

That log is from r36168.
Every time a new build comes out I try it to see if it works. But I end up going back to r30*** or so to have it working...

kernel-panic69
DD-WRT Guru

Joined: 08 May 2018
Posts: 14215
Location: Texas, USA

Posted: Tue Jun 26, 2018 16:29 Post subject: Re: Linksys E4200 v1

mama_mia wrote:

kernel-panic69 wrote:

That log is from r36168.
Every time a new build comes out I try it to see if it works. But I end up going back to r30*** or so to have it working...

Are you using a K2.6 or K3.x build? I had a weird cycling issue at first, or so my syslog seemed to indicate, but it wasn't every 5 minutes. Of course, I am not using DDNS, UPnP, or DNSMasq, among other things. I've yet to find the magic configuration to switch to DNSMasq, and honestly I have no need to use it, so I gave up. I've been using K3.x builds since 35531. K2.6 30880 was pretty good 'out of the box' for me, though. Try setting your re-key interval to 0, apply settings, reboot. I haven't tried to switch back to the default 3600 yet in this build.

mama_mia
DD-WRT Novice

Joined: 15 Aug 2012
Posts: 44

Posted: Tue Jun 26, 2018 21:07 Post subject: Re: Linksys E4200 v1

kernel-panic69 wrote:

I'm using K3.x.
DNSMasq comes enabled by default. DDNS and UPnP are on because I need them, but, even with those off the reboot happens. I already tried 30/30/30 and left it working without changing anything and it happens...every 5 minutes!

kernel-panic69
DD-WRT Guru

Joined: 08 May 2018
Posts: 14215
Location: Texas, USA

Posted: Tue Jun 26, 2018 22:59 Post subject: Re: Linksys E4200 v1

mama_mia wrote:

DNSMasq doesn't seem to want to work for me, wouldn't even lease IP addresses in this build. Wondering if maybe that is part of your problem. UDHCPD seems to work fine for me.

varunzzz
DD-WRT Novice

Joined: 29 Jun 2018
Posts: 1

Posted: Fri Jun 29, 2018 8:49 Post subject: Re: New Build 36168 (BS): 06-20-2018-r36168

Hi. I am new to flashing dd wrt. I have managed to install a DD WRT firmware but now if I want to go back to stock firmware I am unable to do that. When I flash the stock firmware it flashed without any problem but when I enter the setup page DD WRT firmware loads up. Could you kindly help me out and tell me what am I doing wrong.

My router is Netgear r6400

jwh7 wrote:

Downloads at:
https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/06-20-2018-r36168/
ftp://ftp.dd-wrt.com/betas/2018/06-20-2018-r36168/
Also: alternate DD-WRT website link.

Changelogs:
SVN Changelog: Since last build (36154)
Summary: (deprecated after 29739)

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.
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 Issue #5 below).

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. Trendnet 81*DRU models are missing factory-to-flash, and 811/812v2 are too big to flash: http://svn.dd-wrt.com/ticket/6144
3. DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:
http://svn.dd-wrt.com/ticket/6246
4. Reports of nas module crashes (used by the bcm driver):
https://svn.dd-wrt.com/ticket/6310 [BS hopes this will be fixed in this build.]
5. WDS does not work on ARM devices (only MIPS<->MIPS)

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.):

Code:

[b]Router/Version: [/b]
[b]Firmware: [/b]
[b]Kernel: [/b]
[b]Mode: [/b]
[b]Status: [/b]

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.

kernel-panic69
DD-WRT Guru

Joined: 08 May 2018
Posts: 14215
Location: Texas, USA

Posted: Fri Jun 29, 2018 14:22 Post subject: Re: New Build 36168 (BS): 06-20-2018-r36168

varunzzz wrote:

I'm not entirely familiar with your device, but I did find this thread:

https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1101336

Hope this helps.

kernel-panic69
DD-WRT Guru

Joined: 08 May 2018
Posts: 14215
Location: Texas, USA

Posted: Wed Jul 04, 2018 14:01 Post subject: Re: Linksys E4200 v1

kernel-panic69 wrote:

Router/Version: Linksys E4200 v1
Firmware: DD-WRT v3.0-r36168 mega ( 06/20/18 )
Kernel: Linux 3.10.108-d2 #19640 Wed Jun 20 18:06:53 CEST 2018 mips
Previous: Linksys1.0.06 build 3 ( 05/20/14 )
Firmware file used:dd-wrt.v24-36168_NEWD-2_K3.x_mega-e4200.bin
Reset;No
Mode: Gateway/AP
Status: OK
Issues/Errors:

De-bricked!

By way of dd-wrt.v24-21061_NEWD-2_K2.6_mini-e4200.bin, dd-wrt.v24-30880_NEWD-2_K2.6_mega-nv60k.bin, dd-wrt.v24-36168_NEWD-2_K2.6_mega-nv60k.bin, and finally dd-wrt.v24-36168_NEWD-2_K3.x_mega-e4200.bin...

i didn't have 35531 mega k2.6 to step to after 30880 or the initial 21676 mini E4200 k2.6 on my MacBook, but all went well. Not touching defaults and soft reset until the final K3.x 36168 flash seemed to work just fine. Will keep an eye on logs to see if issues arise with nas, etc.

EDIT: Only issue so far is with webGUI basic wireless settings page. Seems to want to default to auto channel and not allow channel selection after initial reboot without 'save' or 'apply settings' first. I don't think this is a 'new' issue, and probably tied to forgetting to reset after flash via GUI when I went from K2.6 to K3.x ...

EDIT#2: Which also broke DNSMasq (or Windows), apparently. "Error resolving host"...

EDIT#3: Reverted to DNSMasq being disabled and using udhcp as DHCP server, continuing to test WPA2/GTK re-key interval at 3600...

EDIT#4: WPA2/GTK re-key interval eventually causes disconnects. Set interval to 0 and rebooted at around 18 hours or so uptime, will see if the disconnects disappear. Things get a little buggy after the loopback error message and then eventually things just crap out altogether, especially if an ntp cyclic update fails.

serial_console.txt

Description:

Download

Filename:

serial_console.txt

Filesize:

12.08 KB

Downloaded:

2138 Time(s)

post-debrick-ddwrt-dmesg_r36168.txt

Description:

Download

Filename:

post-debrick-ddwrt-dmesg_r36168.txt

Filesize:

8.66 KB

Downloaded:

252 Time(s)

post-debrick-ddwrt-syslog_r36168.txt

Description:

Download

Filename:

post-debrick-ddwrt-syslog_r36168.txt

Filesize:

20.98 KB

Downloaded:

193 Time(s)

Goto page Previous 1, 2, 3

Display posts from previous:

Page 3 of 3

DD-WRT Forum Index -> Broadcom SoC based Hardware

All times are GMT

Navigation

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum

Log in

New Build 36168 (BS): 06-20-2018-r36168

Quick Links

Log in