Joined: 08 May 2018 Posts: 6961 Location: Texas, USA
Posted: Fri May 18, 2018 15:12 Post subject:
Digging through the source code would require a computer running Linux or OSX, equipped with all the appropriate tools, and I'm not as much of a guru on that part yet
Router Model: Linksys EA6400
Firmware: DD-WRT v3.0-r35927 std (05/13/18)
Kernel: Linux 4.4.131 #3081 SMP Sun May 13 07:27:31 CEST 2018 armv7l
Uptime: 4 days, 11:09
CPU Model: Broadcom BCM4708
CPU Clock: 800 MHz
Load Average: 100% 4.01, 4.02, 3.97
Status: VPN AP
Errors: Load average keeps steadily climbing. No apparent impact to performance so more of a curiosity. Maybe just not averaging correctly.
Router/Version: Asus AC5300 Firmware: 35927 Kernel: ? Mode: ? Issues: Updating from 35831 to 35927 has left me unable to access the administrator gui through ssh, telnet, or browser. I believe the update went through, and I can still access the internet. What options do I have?
Edit: After powering the router on and back off I noticed the update had not taken.
Joined: 08 May 2018 Posts: 6961 Location: Texas, USA
Posted: Sat May 19, 2018 1:23 Post subject:
Router/Version: Linksys E4200 v1
Firmware: DD-WRT v3.0-r35927 mega ( 05/13/18 )
Kernel: Linux 3.10.108-dd #19152 Sun May 13 12:33:42 CEST 2018 mips
Reset : No
Mode: AP/Gateway
Status: OK, except random wireless connectivity drop-outs
Issues:
One persistent thing I have noticed is that the Wireless -> Basic Settings tab, channel select seems to lock to 'Auto' and not show any options for channel until you click 'Save'. Not sure if that has anything to do with the wireless issues or not.
To further test, I have set 2.4G to channel 6 and 5G to 136, with lower extension channel selected.
EDIT: After some reading, I realized why Auto vs. PSK broke things. Still having wi-fi issues, but nothing in the logs is pointing me in any direction. Disconnect/reconnect on client seems to fix the problem until the next hang-up. Even enabling KeepAlive on Windows doesn't help.
Last edited by kernel-panic69 on Sat May 19, 2018 17:08; edited 1 time in total
Joined: 08 May 2018 Posts: 6961 Location: Texas, USA
Posted: Sat May 19, 2018 1:47 Post subject:
zerophase wrote:
Router/Version: Asus AC5300 Firmware: 35927 Kernel: ? Mode: ? Issues: Updating from 35831 to 35927 has left me unable to access the administrator gui through ssh, telnet, or browser. I believe the update went through, and I can still access the internet. What options do I have?
Edit: After powering the router on and back off I noticed the update had not taken.
You may want to try a soft reset through the webGUI before and after flash and then re-set all of your settings by hand and see if that does the trick. There isn't a wiki page for that router that I could find, but that's the only thing I can suggest.
You may want to try a soft reset through the webGUI before and after flash and then re-set all of your settings by hand and see if that does the trick. There isn't a wiki page for that router that I could find, but that's the only thing I can suggest.
Joined: 26 Mar 2013 Posts: 678 Location: Hung Hom, Hong Kong
Posted: Sat May 19, 2018 16:24 Post subject: Programming DD-WRT?
kernel-panic69 wrote:
Digging through the source code would require a computer running Linux or OSX, equipped with all the appropriate tools, and I'm not as much of a guru on that part yet
I am also interested in some C programming, fixing simple problems.
But like you, I need to know how to read those source codes first. It's way too hard to guess the objective of a page of C source codes from the bottom. _________________ Router: Asus RT-N18U (rev. A1)
May the Force and farces be with you! Live long and proper!
Joined: 08 May 2018 Posts: 6961 Location: Texas, USA
Posted: Sat May 19, 2018 16:46 Post subject:
zerophase wrote:
kernel-panic69 wrote:
You may want to try a soft reset through the webGUI before and after flash and then re-set all of your settings by hand and see if that does the trick. There isn't a wiki page for that router that I could find, but that's the only thing I can suggest.
May 19 17:04:06 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:07 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
_________________ ASUS RT-AC3200 - Deployed Client's site
ASUS RT-AC5200 - Merlin
ASUS RT-AX88U - Merlin
Joined: 08 May 2018 Posts: 6961 Location: Texas, USA
Posted: Sat May 19, 2018 17:31 Post subject:
mbze430 wrote:
Anyone know why this is happening?
I am using my ASUS AC3200 as an Access Point
Code:
May 19 17:04:06 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:07 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
May 19 17:04:08 AC3200 kern.warn kernel: br0: received packet on eth2 with own address as source address
I'm getting the same thing every so often in the syslog. If I'm not mistaken, that is the 5GHz interface on mine (actually, I think it's dual-band on the E4200 Linksys?). That could be part of the problem with NAS/wland, perhaps?
Status: VPN AP
Errors: Load average keeps steadily climbing. No apparent impact to performance so more of a curiosity. Maybe just not averaging correctly.
Noticed same on my AP/gateway. top revealed it was ebtables, with 2 tasks driving all 2 cores to the max.
Applied settings of various pages without changing anything (me thinks), rebooted and it is gone since.
Before, I was playing around with OpenVPN, same build. _________________ 3xBuffalo WLI-H4-D1300
1xBuffalo WZR-D1800H
1xBuffalo WHR-HP-G300N
1xBuffalo WHR-1166D (stock f/w)
1xASUS RT-AC87U
1xTP710
Joined: 08 May 2018 Posts: 6961 Location: Texas, USA
Posted: Mon May 21, 2018 2:21 Post subject: NAS crash
I was streaming internet radio with VLC. Stream never stopped, but when I woke up and tried to reload pages in my browser, nothing. Disconnect and reconnect to wi-fi and shut down VLC, back in business. Streaming media over wi-fi seems to break things for me, I'm guessing. Didn't have this issue during the same time period with streaming from a wired client, only wi-fi. Guess I got lucky enough to catch the entire trace (over 1000 entries prior to crash). Syslog from last boot-up until now attached, haven't tried to register on SVN again yet.
Does anyone else have the webUI crash when you click status>active connections? I've noticed it in previous versions as well, but never got around to asking if anyone else is seeing it before i log it as an issue.
RT-AC66U
Code:
May 21 12:43:11 router user.err : Caught SIGSEGV (11) sent by kernel in ej_ip_conntrack_table
May 21 12:43:11 router user.err : Thread 22555: httpd
May 21 12:43:11 router user.err : === Context:
May 21 12:43:11 router user.err : ZERO:00000000 AT:775234d8 V0:6b6e752e V1:77868108 A0:775239b0 A1:774f0000
May 21 12:43:11 router user.err : A2:775238a8 A3:fefefeff T0:9bffc18b T1:775233ce T2:0000000a T3:09097063
May 21 12:43:11 router user.err : T4:69660a09 T5:8624be78 T6:00000000 T7:09096f64 S0:77514880 S1:774ef804
May 21 12:43:11 router user.err : S2:77523d40 S3:005d0f00 S4:00000000 S5:7783ba90 S6:7750e000 S7:7f92ede8
May 21 12:43:11 router user.err : T8:00000000 T9:777d5140 K0:00000000 K1:00000000 GP:7786f3c0 SP:77523590
May 21 12:43:11 router user.err : FP:77870ea0 RA:774cea8b
May 21 12:43:11 router user.err : === Backtrace:
May 21 12:43:12 router user.err : # Text at 0x774beffd is not mapped; trying prior frame pointer.
May 21 12:43:14 router user.err : # Text at 0x774befff is not mapped; terminating backtrace.
May 21 12:43:14 router user.err : /usr/lib/visuals.so[0x774c0000](ej_ip_conntrack_table+0x00000134)[0x774cea95]
May 21 12:43:14 router user.err : /usr/lib/visuals.so[0x774c0000](ej_ip_conntrack_table+0x0000012a)[0x774cea8b]
May 21 12:43:14 router user.err : === Code:
May 21 12:43:14 router user.err : 774cea48: 92d14904 67b196d4 9a4094dc 653aea40 9848f030 98b0f030 f1cb94d2 f6084a0d
May 21 12:43:14 router user.err : 774cea68: d2d04d18 653aea40 659e9604 2205f0a0 98b0f030 4d00f03f 9840f270 ea4004c6
May 21 12:43:14 router user.err : 774cea88: >06c6653a f03092d1 94dc98b0 f05f9a40 ea404d08 9604653a f3d093d7 659e9854
May 21 12:43:14 router user.err : 774ceaa8: f0a006ce f0302b17 f05f98b0 04064d1c 653aea40 92d167b1 94dc96ce 9828f030
