Router: Netgear R7000
Firmware: DD-WRT v3.0-r36104 std (06/10/2018)
Kernel: Linux 4.4.136 #3233 SMP Sun Jun 10 08:02:47 CEST 2018 armv7l
Status: Working
Reset: No
Previous: 36070M
Errors: No
CPU Temperature : 54.1 °C / WL0 45.0 °C / WL1 47.0 °C
Working very well :
Router mode : DHCP
SFE Enable STP Enable
DNSMasq
Encrypt DNS
Cache DNSSEC data
Validate DNS Replies (DNSSEC)
Local DNS
No DNS Rebind
Query DNS in Strict Order
SPI Firewall
Usb
Nas, MiniDLNA, Samba, JFFS2,
MAC Filter
wl0, wl1
Vpn (OpenVPN Client)
Kong and BS: Thanks for all your good work!
without VPN
with VPN
Could you tell me what is your EncrytDNS settings because EncryptDNS dows not aloow me to get internet access unless i select an !PV6 resolver and i am still on IPV4 only.
Router Model: Linksys EA6400
Firmware: DD-WRT v3.0-r36104 std (06/10/18)
Kernel: Linux 4.4.136 #3233 SMP Sun Jun 10 08:02:47 CEST 2018 armv7l
Status: VPN AP / Switch
Previous: DD-WRT v3.0-r35927 std (05/13/18)
Reset: No: Save/Restore nvram after upgrade.
Errors: Took a few SAVE/APPly sequences to get VPN to stick. Seems to have stabled out.
Linksys WAP54G v3
DD-WRT v3.0-r36104 micro [06/10/18]
Linux 2.4.37 #49726 Sun Jun 10 06:49:19 CEST 2018 mips
[dd-wrt.v24_micro_generic.bin]
GUI install over r33986, NO Reset.
WAP + guest on br1
all working ok... but it required a power cycle after install.
Could not reach wired or wireless. Wifi broadcast and connected but would not pass traffic.
After power cycle all is good!!!
Reset
setup 'Repeater Bridge'. All good but VAP WPA2 Personal AES security must be same as Physical Interface.
Connected to EA8500 [Kong r36100M 06/11/18] works fine.
WAP54G can have different VAP SSID for repeater bridge but WPA2 security must be same on VAP for wireless to connect.
Router: Buffalo WZR-1750DHP
Firmware: buffalo-wzr-1750dhp-webflash.bin (v3.0-r36104 std)
Kernel: Linux 4.4.136 #3233 SMP Sun Jun 10 08:02:47 CEST 2018 armv7l
Status: Working
Reset: No
Notes on configuration:
FTP server
DNSMasq
USB v3.0
DHCP reservation
Errors:
1. No overclocking
2. user.info : Authentication fail after each http login
daemon.err httpd[1396]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Thu Jun 14, 2018 8:42 Post subject: Re: Linksys E4200v1
kernel-panic69 wrote:
kernel-panic69 wrote:
Router/Version: Linksys E4200 v1
Firmware: DD-WRT v3.0-r36104 mega ( 06/10/18 )
Kernel: Linux 3.10.108-d2 #19520 Sun Jun 10 15:40:36 CEST 2018 mips
Previous:DD-WRT v3.0-r36079 mega ( 06/01/18 )
Firmware file used:dd-wrt.v24-36104_NEWD-2_K3.x_mega-e4200.bin
Reset;No
Mode: Gateway/AP
Status: OK
Issues/Errors:
Aaaaaaand, we have the first nas crash.
I think I have discovered a possible workaround until this is fixed permanently. Set WPA re-key interval to 99999 and reboot router daily. I am at around 20 hours of uptime with no nas crash and no wi-fi client issues.
EDIT: Currently at 1 day, 4:11 hours of uptime with no reboot. No nas crash and no wi-fi client issues. Going to ride it out and see if this stabilizes the issue, may re-test with the default WPA re-key interval and a reboot to see if it was just a no-reset flash glitch, but seems to have settled things out. I can only think that it is coincidental with WPA re-key interval, and probably client connected time. That is probably the last thing to check besides wireless media streaming.
Last edited by kernel-panic69 on Thu Jun 14, 2018 16:46; edited 1 time in total
Posted: Thu Jun 14, 2018 10:03 Post subject: Re: Linksys E4200v1
kernel-panic69 wrote:
kernel-panic69 wrote:
kernel-panic69 wrote:
Router/Version: Linksys E4200 v1
Firmware: DD-WRT v3.0-r36104 mega ( 06/10/18 )
Kernel: Linux 3.10.108-d2 #19520 Sun Jun 10 15:40:36 CEST 2018 mips
Previous:DD-WRT v3.0-r36079 mega ( 06/01/18 )
Firmware file used:dd-wrt.v24-36104_NEWD-2_K3.x_mega-e4200.bin
Reset;No
Mode: Gateway/AP
Status: OK
Issues/Errors:
Aaaaaaand, we have the first nas crash.
I think I have discovered a possible workaround until this is fixed permanently. Set WPA re-key interval to 99999 and reboot router daily. I am at around 20 hours of uptime with no nas crash and no wi-fi client issues.
How can identify this crash you speak of? I have a bunch of this in my syslog:
#1064 (0x42a780)->0x42a080: 0 sec 0 usec 0x403499
But nothing before or after to identify the crashed module
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Thu Jun 14, 2018 11:16 Post subject: Re: Linksys E4200v1
Pdobrien3 wrote:
How can identify this crash you speak of? I have a bunch of this in my syslog:
#1064 (0x42a780)->0x42a080: 0 sec 0 usec 0x403499
But nothing before or after to identify the crashed module
My crash usually occurs after #1086 as shown in syslog excerpt below. Note the bold red lines that indicate the process thread that crashes and eventually restarts.
Jun 12 22:13:48 DD-WRT user.info : #1086 (0x4327e0)->0x0: 0 sec 989602 usec 0x403461
Jun 12 17:13:48 DD-WRT user.err : Caught SIGSEGV (11) in dd_timer_create
Jun 12 17:13:48 DD-WRT user.err : Fault at memory location 0x0000001c due to address not mapped to object (1).
Jun 12 17:13:48 DD-WRT user.err : Thread 1460: nas
Jun 12 17:13:48 DD-WRT user.err : === Context:
Jun 12 17:13:48 DD-WRT user.err : ZERO:00000000 AT:00000000 V0:00000000 V1:0000043f A0:00000000 A1:00000000
Jun 12 17:13:48 DD-WRT user.err : A2:0000043f A3:00000000 T0:00000000 T1:00000000 T2:7f8b5208 T3:7f8b4ffa
Jun 12 17:13:48 DD-WRT user.err : T4:00000001 T5:00000000 T6:00000000 T7:20636573 S0:778705e0 S1:00000000
Jun 12 17:13:48 DD-WRT user.err : S2:00000014 S3:00401301 S4:77920000 S5:77920000 S6:77920000 S7:00000000
Jun 12 17:13:48 DD-WRT user.err : T8:00000000 T9:778f7a60 K0:00000000 K1:00000000 GP:778705e0 SP:7f8b56f8
Jun 12 17:13:48 DD-WRT user.err : FP:00000000 RA:77842d0b
Jun 12 17:13:48 DD-WRT user.err : === Backtrace:
Jun 12 17:13:48 DD-WRT user.err : # Text at 0x77833ffd is not mapped; trying prior frame pointer.
Jun 12 17:13:49 DD-WRT user.err : # Text at 0x77833fff is not mapped; terminating backtrace.
Jun 12 17:13:49 DD-WRT user.err : /usr/lib/libutils.so[0x77834000](dd_timer_create+0x00000064)[0x77842d0d]
Jun 12 17:13:49 DD-WRT user.err : /usr/lib/libutils.so[0x77834000](dd_timer_create+0x00000062)[0x77842d0b]
Jun 12 17:13:49 DD-WRT user.err : === Code:
Jun 12 17:13:49 DD-WRT user.err : 77842cc8: f1304d18 6c069814 6538e840 ea4b6a01 e8a06476 9d42250a 9d412a03 6005720e
Jun 12 17:13:49 DD-WRT user.err : 77842ce8: 98a4f030 4d10f212 f01017ec d2069858 9a3cf389 f0302906 f21d988c ec404c11
Jun 12 17:13:49 DD-WRT user.err : 77842d08: >6a00653c f0309967 c94c980c f29d9206 65384809 da7cf389 e8406a00 920ed947
Jun 12 17:13:49 DD-WRT user.err : 77842d28: 6a00da20 650017d5 6a00dca4 dcc5e820 6a03f000 0b04f0bb 3240f400 659ae269
Jun 12 22:14:00 DD-WRT user.info : nas : NAS daemon successfully stopped
Jun 12 22:14:02 DD-WRT user.info : nas : NAS daemon hanging, send SIGKILL
Jun 12 22:14:02 DD-WRT user.info : NAS : NAS lan (wl0 interface) successfully started
Jun 12 22:14:02 DD-WRT user.info : NAS : NAS lan (wl1 interface) successfully started
Jun 12 22:14:12 DD-WRT kern.warn kernel: br0: received packet on eth2 with own address as source address
Not sure if you have to have syslogd and klogd both enabled to see it, but that is what is enabled on mine.
E2500
DD-WRT v3.0-r36104 mega [06/10/18]
Linux 3.10.108-d2 #19520 Sun Jun 10 15:40:36 CEST 2018 mips
[dd-wrt.v24-36104_NEWD-2_K3.x_mega.bin]
GUI update over r33986 Repeater Bridge.
No reset.
Tis working ok.
----
EDIT:
Repeater Bridge notes ---> https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1132041#1132041
Last edited by mrjcd on Sun Jun 17, 2018 12:36; edited 1 time in total
Status: Working
Reset: No
Errors: When I try to connect via FileZilla on port 22 I see this error:
Error: Received unexpected end-of-file from SFTP server
Error: Could not connect to server _________________ Kaan's World | @mkaand | PLEX Archive | Trakt.tv
I think I have discovered a possible workaround until this is fixed permanently. Set WPA re-key interval to 99999 and reboot router daily. I am at around 20 hours of uptime with no nas crash and no wi-fi client issues.
EDIT: Currently at 1 day, 4:11 hours of uptime with no reboot. No nas crash and no wi-fi client issues. Going to ride it out and see if this stabilizes the issue, may re-test with the default WPA re-key interval and a reboot to see if it was just a no-reset flash glitch, but seems to have settled things out. I can only think that it is coincidental with WPA re-key interval, and probably client connected time. That is probably the last thing to check besides wireless media streaming.
Its too early for me to tell since I've only had 10 hours uptime but I think you may be on to something. I tried your workaround this morning and wifi has been behaving so far.
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Thu Jun 14, 2018 19:11 Post subject:
rumbleroast wrote:
kernel-panic69 wrote:
I think I have discovered a possible workaround until this is fixed permanently. Set WPA re-key interval to 99999 and reboot router daily. I am at around 20 hours of uptime with no nas crash and no wi-fi client issues.
EDIT: Currently at 1 day, 4:11 hours of uptime with no reboot. No nas crash and no wi-fi client issues. Going to ride it out and see if this stabilizes the issue, may re-test with the default WPA re-key interval and a reboot to see if it was just a no-reset flash glitch, but seems to have settled things out. I can only think that it is coincidental with WPA re-key interval, and probably client connected time. That is probably the last thing to check besides wireless media streaming.
Its too early for me to tell since I've only had 10 hours uptime but I think you may be on to something. I tried your workaround this morning and wifi has been behaving so far.
I was literally having to disconnect and reconnect wi-fi every 1-2 hours (sometimes LESS!) until I changed that particular setting. At 1 day, 6:40 and still no crash and everything is behaving.
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Fri Jun 15, 2018 9:54 Post subject: Re: Linksys E4200v1
kernel-panic69 wrote:
I think I have discovered a possible workaround until this is fixed permanently. Set WPA re-key interval to 99999 and reboot router daily. I am at around 20 hours of uptime with no nas crash and no wi-fi client issues.
Interesting observation if not discovery here... Thank you, Your Curiosity!
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Jun 15, 2018 11:31 Post subject: Re: Linksys E4200v1
kernel-panic69 wrote:
Pdobrien3 wrote:
How can identify this crash you speak of? I have a bunch of this in my syslog:
#1064 (0x42a780)->0x42a080: 0 sec 0 usec 0x403499
But nothing before or after to identify the crashed module
My crash usually occurs after #1086 as shown in syslog excerpt below. Note the bold red lines that indicate the process thread that crashes and eventually restarts.
Jun 12 22:13:48 DD-WRT user.info : #1086 (0x4327e0)->0x0: 0 sec 989602 usec 0x403461
Jun 12 17:13:48 DD-WRT user.err : Caught SIGSEGV (11) in dd_timer_create
Jun 12 17:13:48 DD-WRT user.err : Fault at memory location 0x0000001c due to address not mapped to object (1).
Jun 12 17:13:48 DD-WRT user.err : Thread 1460: nas
Jun 12 17:13:48 DD-WRT user.err : === Context:
Jun 12 17:13:48 DD-WRT user.err : ZERO:00000000 AT:00000000 V0:00000000 V1:0000043f A0:00000000 A1:00000000
Jun 12 17:13:48 DD-WRT user.err : A2:0000043f A3:00000000 T0:00000000 T1:00000000 T2:7f8b5208 T3:7f8b4ffa
Jun 12 17:13:48 DD-WRT user.err : T4:00000001 T5:00000000 T6:00000000 T7:20636573 S0:778705e0 S1:00000000
Jun 12 17:13:48 DD-WRT user.err : S2:00000014 S3:00401301 S4:77920000 S5:77920000 S6:77920000 S7:00000000
Jun 12 17:13:48 DD-WRT user.err : T8:00000000 T9:778f7a60 K0:00000000 K1:00000000 GP:778705e0 SP:7f8b56f8
Jun 12 17:13:48 DD-WRT user.err : FP:00000000 RA:77842d0b
Jun 12 17:13:48 DD-WRT user.err : === Backtrace:
Jun 12 17:13:48 DD-WRT user.err : # Text at 0x77833ffd is not mapped; trying prior frame pointer.
Jun 12 17:13:49 DD-WRT user.err : # Text at 0x77833fff is not mapped; terminating backtrace.
Jun 12 17:13:49 DD-WRT user.err : /usr/lib/libutils.so[0x77834000](dd_timer_create+0x00000064)[0x77842d0d]
Jun 12 17:13:49 DD-WRT user.err : /usr/lib/libutils.so[0x77834000](dd_timer_create+0x00000062)[0x77842d0b]
Jun 12 17:13:49 DD-WRT user.err : === Code:
Jun 12 17:13:49 DD-WRT user.err : 77842cc8: f1304d18 6c069814 6538e840 ea4b6a01 e8a06476 9d42250a 9d412a03 6005720e
Jun 12 17:13:49 DD-WRT user.err : 77842ce8: 98a4f030 4d10f212 f01017ec d2069858 9a3cf389 f0302906 f21d988c ec404c11
Jun 12 17:13:49 DD-WRT user.err : 77842d08: >6a00653c f0309967 c94c980c f29d9206 65384809 da7cf389 e8406a00 920ed947
Jun 12 17:13:49 DD-WRT user.err : 77842d28: 6a00da20 650017d5 6a00dca4 dcc5e820 6a03f000 0b04f0bb 3240f400 659ae269
Jun 12 22:14:00 DD-WRT user.info : nas : NAS daemon successfully stopped
Jun 12 22:14:02 DD-WRT user.info : nas : NAS daemon hanging, send SIGKILL
Jun 12 22:14:02 DD-WRT user.info : NAS : NAS lan (wl0 interface) successfully started
Jun 12 22:14:02 DD-WRT user.info : NAS : NAS lan (wl1 interface) successfully started
Jun 12 22:14:12 DD-WRT kern.warn kernel: br0: received packet on eth2 with own address as source address
Not sure if you have to have syslogd and klogd both enabled to see it, but that is what is enabled on mine.
in the middle of your log your time changes 5 hours from 17 to 22
can you explain this? _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
