New Build 40900: BS 09-04-2019-r40900

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
madhits45
DD-WRT User


Joined: 20 Apr 2009
Posts: 69

PostPosted: Thu Sep 05, 2019 18:48    Post subject: Reply with quote
Router/Version: Asus Ac5300
Firmware: DD-WRT v3.0-r40900 std (09/04/19)
Kernel: Linux 4.4.190 #1141 SMP Wed Sep 4 06:27:43 +04 2019 armv7l
Previous: r39960
Mode/Status: Gateway / working with issues
Reset: no
Issues/Errors: web gui keeps crashing, 5ghz cant change channels, stuck on auto. UPDATE: Also 2.4ghz channel still crashing same as other builds but does not bring down WAN with it.


Uptime: 1hr
Temperatures: CPU 54.7 °C / WL0 44.0 °C / WL1 42.5 °C with USB fan is use. Without fan temps are close to 70 °C


Last edited by madhits45 on Sat Sep 07, 2019 15:34; edited 1 time in total
Sponsor
kernel-panic69
DD-WRT Guru


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

PostPosted: Thu Sep 05, 2019 19:17    Post subject: Reply with quote
madhits45 wrote:
Router/Version: Asus Ac5300
Firmware: DD-WRT v3.0-r40900 std (09/04/19)
Kernel: Linux 4.4.190 #1141 SMP Wed Sep 4 06:27:43 +04 2019 armv7l
Previous: r39960
Mode/Status: Gateway / working with issues
Reset: no
Issues/Errors: web gui keeps crashing, 5ghz cant change channels, stuck on auto


Uptime: 1hr
Temperatures: CPU 54.7 °C / WL0 44.0 °C / WL1 42.5 °C with USB fan is use. Without fan temps are close to 70 °C


What browser are you using? Getting the channels and modes on wi-fi to change and play nice can be tricky, that's nothing new. Not sure if coming from a <Kong> build without a reset is part of the problem or not, but you can always try resetting and starting from scratch.
Veritech
DD-WRT User


Joined: 02 Jan 2007
Posts: 191

PostPosted: Thu Sep 05, 2019 23:29    Post subject: WNDR4500v2 Reply with quote
Router Model: Netgear WNDR4500v2
Firmware Version: DD-WRT v3.0-r40900 giga (09/04/19)
Kernel Version: Linux 3.10.108-d8 #26530 Wed Sep 4 10:26:06 +04 2019 mips
Uptime: 1 day, 17 min
Mode: Switch - DHCP Forwarding
Status: working
Reset: no
Issues/Errors: Stable if wireless radios are turned off. If radios are turned on it stops passing traffic with in 12-15 hours and does not respond to any network traffic. Also, will not flash successfully if radios are enabled. Was running build 39469 tried flashing all previous builds up to 40890. None would flash without halting the boot process and using tftp. Even reset to defaults failed with radios enabled. All flashing done with radios disabled successfully occured with no issue and did not require a reset to defaults. With radios off 5ghz led still lit.

Temps were around 40-44dC while transmitting, temps are not displayed when radios are off.

Hope this helps.
madhits45
DD-WRT User


Joined: 20 Apr 2009
Posts: 69

PostPosted: Thu Sep 05, 2019 23:36    Post subject: Reply with quote
kernel-panic69 wrote:
madhits45 wrote:
Router/Version: Asus Ac5300
Firmware: DD-WRT v3.0-r40900 std (09/04/19)
Kernel: Linux 4.4.190 #1141 SMP Wed Sep 4 06:27:43 +04 2019 armv7l
Previous: r39960
Mode/Status: Gateway / working with issues
Reset: no
Issues/Errors: web gui keeps crashing, 5ghz cant change channels, stuck on auto


Uptime: 1hr
Temperatures: CPU 54.7 °C / WL0 44.0 °C / WL1 42.5 °C with USB fan is use. Without fan temps are close to 70 °C


What browser are you using? Getting the channels and modes on wi-fi to change and play nice can be tricky, that's nothing new. Not sure if coming from a <Kong> build without a reset is part of the problem or not, but you can always try resetting and starting from scratch.


I'll try a reset, I'm using firefox.

Update: I did the reset and it seems ok again but my 2.4ghz wifi is very slow. 5ghz is fast.

Update 2: I reset 2 times and its better but still 2.4ghz so far is still slow and the web gui is unavailable but at least 2.4ghz is not crashing but it might with it being this slow. again 5ghz is fast.


Last edited by madhits45 on Sun Sep 08, 2019 3:42; edited 2 times in total
technoside2
DD-WRT User


Joined: 25 Oct 2018
Posts: 64

PostPosted: Fri Sep 06, 2019 2:47    Post subject: Reply with quote
Quote:

nicely written.

i have the means to de-brick but i do not have the time mostly as most of the devices i upgrade are operational and not for testing. so what i usually do is to wait until someone reports a successful flash for the same device.

if i am the first to flash, then i get my self ready to de-brick, no surprises.


The user base of EA6350 V2 is pretty small. Sad

_________________
WRT54GL v1.1 - Flashed
Linksys WRT54G2 v1 - Flashed
EA6350 v2 - Flashed
Roger W
DD-WRT Novice


Joined: 23 Apr 2014
Posts: 18

PostPosted: Fri Sep 06, 2019 3:37    Post subject: Reply with quote
Router/Version: Asus RT-AC68U
File: asus_rt-ac68u-firmware.trx
Kernel: Linux 4.4.190 #1136 SMP Wed Sep 4 06:03:54 +04 2019 armv7l
Mode: Gateway / AP/ Bridged VAP
Status: ok (5 minutes)

EDIT: I previously said that OP's comment about the startup script wasn't correct for me. I thought I was unbridged but I am bridged after all, so I can't speak to not needing the startup script.


Last edited by Roger W on Fri Sep 06, 2019 18:16; edited 1 time in total
Valeriy_tc
DD-WRT User


Joined: 03 Sep 2016
Posts: 66
Location: Ukraine

PostPosted: Fri Sep 06, 2019 10:45    Post subject: Re: Linksys EA6400 Reply with quote
watchsat wrote:
Valeriy_tc wrote:
Router/Version: Linksys EA6400
Firmware: DD-WRT v3.0-r40900 std (09/04/19)
Kernel: Linux 4.4.190 #1136 SMP Wed Sep 4 06:03:54 +04 2019 armv7l
Previous: DD-WRT v3.0-r40501 std (08/02/19)
Mode/Status: Gateway/Port Forwarding
Reset: No
Issues/Errors: None so far.

Uptime: 57 min
Temperatures: CPU 67.5 °C / WL0 51.8 °C / WL1 55.3 °C


Wonder did you flash your EA6400 from CLI mode? I also tested my EA6400, failed upgrade from WebGUI...


I used WebGUI. I requested from the second attempt.
tli
DD-WRT Novice


Joined: 06 Mar 2019
Posts: 32

PostPosted: Fri Sep 06, 2019 13:26    Post subject: Reply with quote
Router/Version: ASUS RT-N66R
File: dd-wrt.v24-40900_NEWD-2_K3.x-big-RT-N66U.trx
Kernel: Linux 3.10.108-d8 #26542 Wed Sep 4 10:34:42 +04 2019 mips
Mode: Auto-DHCP IPv4 Gateway (disabled/unused: WiFi, VLAN, USB, UPnP & QoS)
Status: Uptime ~45 hrs; working with no apparent issue
Reset: nvram-erased & rebooted before & after update, then power-cycled before manually configured custom settings
Previous: dd-wrt.v24-40352_NEWD-2_K3.x_mega_RT-N66U.trx

Notes:
1) Switched from MEGA-build to the BIG-build for secured operations with using the additional SSH and HTTPS functional capabilities.

2) SFE was enabled by default, as were with previous builds that have been flashed for this router. Left SFE enabled, since it didn't seem to affect/impact the router's performance.
adasch
DD-WRT User


Joined: 02 Jan 2015
Posts: 69
Location: Gdansk, Poland

PostPosted: Fri Sep 06, 2019 17:10    Post subject: Reply with quote
Router/Version: Linksys EA6900
File:
Kernel: Linux 4.4.190 #1136 SMP Wed Sep 4 06:03:54 +04 2019 armv7l
Mode: AP
Status: Working with bugs

Weak build

Web GUI crash some time - replug AC helps
Not working from few YEARS !!!!
Virtual Interfaces wl0.1
in Unbridged and as new bug Bridged mode
DRAMATIC!!!

VPN - working 2,4 and 5G working, speed looks ok

Or maybe my Virtual Interfaces have error in config?
in build r35531 it's works in "Bridged" mode but and don't work in Unbridged mode
In build r40900 this feature don't work - other wifi units can't connect.

it strange for me: it's very important feature. Many persons ask me for acces to my wifi.

For me, it's unthinkable is showing the wifi private password to strangers. Virtual ports helps but other people still see my network devices like TV's, media servers, cameras etc. For repair this situation I need turn unbridged mode but this don't workig. Router don't give IP address connected clients.



EA6900 VP.png
 Description:
 Filesize:  17.01 KB
 Viewed:  1804 Time(s)

EA6900 VP.png



_________________
Linksys EA6900
Firmware: DD-WRT v3.0-r35531 std (03/26/1Cool
mwchang
DD-WRT Guru


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

PostPosted: Sat Sep 07, 2019 10:09    Post subject: DD-WRT BS build 40900 and Asus RT-N18U Reply with quote
Router/Version: Asus RT-N18U(rev. A1)
Firmware: DD-WRT v3.0-r40900 std (09/04/19)
Kernel: Linux 4.4.190 #1140 Wed Sep 4 06:22:19 +04 2019 armv7l
Previous: DD-WRT v3.0-r40459 std (07/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. Error(s) logged:
Code:
grep -i err /var/log/messages

Jan  1 08:00:14 RT-N18U kern.err kernel: bcmsflash: found no supported devices
Jan  1 08:00:14 RT-N18U kern.err kernel: hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
Jan  1 08:00:14 RT-N18U daemon.info mstpd[608]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 7
Jan  1 08:00:14 RT-N18U daemon.info mstpd[608]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 7
Sep  7 17:56:24 RT-N18U daemon.err httpd[1341]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Sep  7 17:56:28 RT-N18U daemon.err httpd[1341]: httpd : Request Error Code 404: File style/elegant/logo.png not found.
Sep  7 17:56:54 RT-N18U daemon.err httpd[1341]: httpd : Request Error Code 404: File style/elegant/logo.png not found.


2. Warning(s) logged:
Code:
grep -i warn /var/log/messages | grep -v DROP

Jan  1 08:00:14 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 0
Jan  1 08:00:14 RT-N18U kern.warn kernel: PCI: Fixing up bus 0 domain 1
Jan  1 08:00:14 RT-N18U kern.warn kernel: PCI: Fixing up bus 1 domain 1
Jan  1 08:00:14 RT-N18U kern.warn kernel: Boot partition size = 524288(0x80000)
Jan  1 08:00:14 RT-N18U kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x200000 size = 0x1e00000, 0x20000
Jan  1 08:00:14 RT-N18U kern.warn kernel: nf_conntrack_rtsp v0.7 loading
Jan  1 08:00:14 RT-N18U kern.warn kernel: nf_nat_rtsp v0.7 loading
Jan  1 08:00:14 RT-N18U kern.warn kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan  1 08:00:14 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:14 RT-N18U kern.warn kernel: Available 7 bytes at (off,len):
Jan  1 08:00:14 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:14 RT-N18U kern.warn kernel: Bad eraseblock 356 at 0x000002c80000
Jan  1 08:00:14 RT-N18U kern.warn kernel: Options: NO_SUBPAGE_WRITE,
Jan  1 08:00:14 RT-N18U kern.warn kernel: et: module license 'Proprietary' taints kernel.
Jan  1 08:00:14 RT-N18U kern.warn kernel: Disabling lock debugging due to kernel taint
Jan  1 08:00:14 RT-N18U kern.warn kernel: et_module_init: passivemode set to 0x0
Jan  1 08:00:14 RT-N18U kern.warn kernel: et_module_init: txworkq set to 0x0
Jan  1 08:00:14 RT-N18U kern.warn kernel: et_module_init: et_txq_thresh set to 0x400
Jan  1 08:00:14 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan  1 08:00:14 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan  1 08:00:14 RT-N18U kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan  1 08:00:14 RT-N18U kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
Jan  1 08:00:14 RT-N18U kern.warn kernel: wl_module_init: passivemode set to 0x0
Jan  1 08:00:14 RT-N18U kern.warn kernel: wl_module_init: txworkq set to 0x0
Jan  1 08:00:14 RT-N18U kern.warn kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
Jan  1 08:00:14 RT-N18U kern.warn kernel: eth0: mixed HW and IP checksum settings.


3. Kernel debugging messages:
Code:
grep -i debug /var/log/messages

Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:01.0: reg 0x14: [mem 0x18002000-0x18002fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:01.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:02.0: [14e4:0502] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:02.0: reg 0x10: [mem 0x1802c000-0x1802cfff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:02.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:03.0: [14e4:4715] type 00 class 0x020000
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:03.0: reg 0x10: [mem 0x18024000-0x18024fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:03.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:04.0: [14e4:4715] type 00 class 0x020000
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:04.0: reg 0x10: [mem 0x18025000-0x18025fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:04.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:05.0: [14e4:4715] type 00 class 0x020000
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:05.0: reg 0x10: [mem 0x18026000-0x18026fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:05.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:06.0: [14e4:4715] type 00 class 0x020000
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:06.0: reg 0x10: [mem 0x18027000-0x18027fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:06.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:07.0: [14e4:0501] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:07.0: reg 0x10: [mem 0x18012000-0x18012fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:07.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:08.0: [14e4:0501] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:08.0: reg 0x10: [mem 0x18013000-0x18013fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:08.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:09.0: [14e4:0501] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:09.0: reg 0x10: [mem 0x18014000-0x18014fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:09.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0a.0: [14e4:0510] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x10: [mem 0x1800b000-0x1800bfff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x14: [mem 0x1800c000-0x1800cfff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0a.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0b.0: [14e4:471a] type 00 class 0x0c0310
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0b.0: reg 0x10: [mem 0x18022000-0x18022fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0b.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0b.1: [14e4:471a] type 00 class 0x0c0320
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0b.1: reg 0x10: [mem 0x18021000-0x18021fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0b.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0c.0: [14e4:472a] type 00 class 0x0c0330
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0c.0: reg 0x10: [mem 0x18023000-0x18023fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0c.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0d.0: [14e4:0503] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0d.0: reg 0x10: [mem 0x18020000-0x18020fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0d.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0e.0: [14e4:0506] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0e.0: reg 0x10: [mem 0x18210000-0x1821ffff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0e.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0f.0: [14e4:0507] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0f.0: reg 0x10: [mem 0x18010000-0x18010fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:10.0: [14e4:0508] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:11.0: [14e4:0509] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:11.0: reg 0x10: [mem 0x18028000-0x18028fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:11.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:12.0: [14e4:050a] type 00 class 0xffffff
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:12.0: reg 0x10: [mem 0x18029000-0x18029fff]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0000:00:12.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0001:00:00.0: [14e4:8011] type 01 class 0x060400
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0001:01:00.0: [14e4:4360] type 00 class 0x028000
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0001:01:00.0: reg 0x10: [mem 0x08000000-0x08007fff 64bit]
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci 0001:01:00.0: supports D1 D2
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
Jan  1 08:00:14 RT-N18U kern.debug kernel: pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 01
Jan  1 08:00:14 RT-N18U kern.warn kernel: Disabling lock debugging due to kernel taint
Jan  1 08:00:24 RT-N18U daemon.debug ntpclient[1007]: Connecting to time.hko.hk [118.143.17.83] ...
Sep  7 17:55:47 RT-N18U daemon.debug process_monitor[1005]: Restarting cron (time sync change)
Sep  7 17:55:47 RT-N18U daemon.debug process_monitor[1202]: We need to re-update after 3600 seconds
Sep  7 17:55:48 RT-N18U daemon.debug ntpclient[1233]: Connecting to time.hko.hk [118.143.17.83] ...
Sep  7 17:55:48 RT-N18U daemon.debug process_monitor[1228]: We need to re-update after 3600 seconds


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
From 27942912 (b.39944) to 28024832 (b.40065) = 81920 bytes
From 28024832 (b.40065) to 28479488 (b.40459) = 454656 bytes
From 28479488 (b.40459) to 28749824 (b.40900) = 270336 bytes





speedtest.net result for DD-WRT BS build 40900 and Asus RT-N18U.png
 Description:
speedtest.net result for DD-WRT BS build 40900 and Asus RT-N18U
 Filesize:  13.01 KB
 Viewed:  1696 Time(s)

speedtest.net result for DD-WRT BS build 40900 and Asus RT-N18U.png



_________________
Router: Asus RT-N18U (rev. A1)

May the Force and farces be with you! Live long and proper!

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
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 7252
Location: Netherlands

PostPosted: Sat Sep 07, 2019 10:57    Post subject: Reply with quote
adasch wrote:
Router/Version: Linksys EA6900
File:
Kernel: Linux 4.4.190 #1136 SMP Wed Sep 4 06:03:54 +04 2019 armv7l
Mode: AP
Status: Working with bugs

Weak build

Web GUI crash some time - replug AC helps
Not working from few YEARS !!!!
Virtual Interfaces wl0.1
in Unbridged and as new bug Bridged mode
DRAMATIC!!!

VPN - working 2,4 and 5G working, speed looks ok

Or maybe my Virtual Interfaces have error in config?
in build r35531 it's works in "Bridged" mode but and don't work in Unbridged mode
In build r40900 this feature don't work - other wifi units can't connect.

it strange for me: it's very important feature. Many persons ask me for acces to my wifi.

For me, it's unthinkable is showing the wifi private password to strangers. Virtual ports helps but other people still see my network devices like TV's, media servers, cameras etc. For repair this situation I need turn unbridged mode but this don't workig. Router don't give IP address connected clients.


From approximately mid 2018 VAP's on Broadcom units are problematic, you cannot connect or do not get an IP address. There are workarounds :
1) When VAP is not working at boot; workaround startup command Administration/Commands, Save as Startup:
sleep 10; stopservice nas; stopservice wlconf; startservice wlconf; startservice nas;
2) Alternative way to get VAP working: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=317181
3) An other user reports the following workaround (save as startup):
sleep 4; stopservice cron; stopservice wlconf; wlconf eth1 up; wlconf eth2 up; startservice cron;
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=319412
4)This one is from @Redhawk (guaranteed to work ):
sleep 20; stopservice nas; wlconf eth1 down; wlconf eth2 down; wlconf eth1 up; wlconf eth2 up; startservice nas; logger "VAP workaround executed";

_________________
Routers:Netgear R7800, R6400v1, R6400v2, Linksys EA8500, EA6900 (XvortexCFE), E2000 (converted WRT320N), WRT54GS v1.
WireGuard Documents & Guides:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=327397
OpenVPN Documents & Guides: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=327398
IPSET: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=327261
Install guide R6400v2:http://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
adasch
DD-WRT User


Joined: 02 Jan 2015
Posts: 69
Location: Gdansk, Poland

PostPosted: Sun Sep 08, 2019 19:04    Post subject: Reply with quote
adasch wrote:

Or maybe my Virtual Interfaces have error in config?
in build r35531 it's works in "Bridged" mode but and don't work in Unbridged mode
In build r40900 this feature don't work - other wifi units can't connect.

problem solved in r35531 (very stable for me)

default config put wrong data in one cell.
in tab Setup/Networking sector Bridging window MTU default setup puts data 1500>22 but should be only 1500

next step is turn on DHCP on wl0.1

now visitors receive 172.16.1.xxx ip's and safety DNS
no one see my servers tv's etc



Networking.png
 Description:
 Filesize:  18.12 KB
 Viewed:  1581 Time(s)

Networking.png



_________________
Linksys EA6900
Firmware: DD-WRT v3.0-r35531 std (03/26/1Cool
kernel-panic69
DD-WRT Guru


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

PostPosted: Mon Sep 09, 2019 0:32    Post subject: Reply with quote
adasch wrote:
adasch wrote:

Or maybe my Virtual Interfaces have error in config?
in build r35531 it's works in "Bridged" mode but and don't work in Unbridged mode
In build r40900 this feature don't work - other wifi units can't connect.

problem solved in r35531 (very stable for me)

default config put wrong data in one cell.
in tab Setup/Networking sector Bridging window MTU default setup puts data 1500>22 but should be only 1500

next step is turn on DHCP on wl0.1

now visitors receive 172.16.1.xxx ip's and safety DNS
no one see my servers tv's etc


Were the default config errors in 40900? You should be able to change that value and save it, which will commit it to nvram, then you can apply or reboot and should be ok.
adasch
DD-WRT User


Joined: 02 Jan 2015
Posts: 69
Location: Gdansk, Poland

PostPosted: Mon Sep 09, 2019 8:57    Post subject: Reply with quote
Hello,

in release r40900 and r40932 virtual AP's don't work. Devices see SSID but connection is impossible in bridged and unbridged mode.

when I put command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
EA6900 hangs until replug AC.

I tray make some additional tests with 40932 but for me running commends is uncomfortable. I can wait for better build because r35531 is very quick stable for me.

Virtual AP's can protect children's with "OpenDNS Family Shield" I think is very useful feature.

_________________
Linksys EA6900
Firmware: DD-WRT v3.0-r35531 std (03/26/1Cool
kernel-panic69
DD-WRT Guru


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

PostPosted: Mon Sep 09, 2019 9:14    Post subject: Reply with quote
Ok, none of that helps to figure out if there is an issue that needs to be resolved with default nvram variables. Thanks anyway.
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum 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