Why does this keep happening?

[MvW]

Yes I can still connect to all the nodes / the main router through SSH & sometimes the 192.168.1.1 login page loads but then after I click login it just stalls.

You can try restarting httpd on the main router to see if that solves the issue of being locked out of the WebUI, by issuing:

service restart_httpd

If the nodes and main router stay accessible through ssh I would start digging through their logfiles to seek for any clues as to what is really happening.

 

[bbunge]

Is only the WebUI inaccessible after making changes or can you still connect through ssh to 192.168.1.1?

You may have something here...

Log in via ssh and run command: service restart_httpd
See if that gets the GUI going.

 

[ComputerSteve]

You may have something here...

Log in via ssh and run command: service restart_httpd
See if that gets the GUI going

So I installed SCmerlin which has that option. It didn't work. I also tried this command. So now the things I have tried for troubleshooting.. Setup Everything to defaults, Assign manual IP's to the Nodes, Reconfigure the nodes once the problem started happening again, & I have now also removed all but 1 wireless node. I thought maybe the ethernet backhaul was causing the problem. So now I only have 1 RT-AC3100 node, & still this problem happens. If I do anything that changes the config such as add something to the roaming blocklist, change the wifi channel, change anything in the professional settings. The web interface dies and the AiMesh nodes switch to unable to find parent AP, & don't recover from that state until I reboot the RT-AC5300.

 

[MvW]

If restarting httpd doesn't restore access through the WebUI, I would use ssh and seriously start digging through the logfiles of your main router as well as your nodes, looking for clues to see why this is happening every time you make a change to your config.

 

[ComputerSteve]

If restarting httpd doesn't restore access through the WebUI, I would use ssh and seriously start digging through the logfiles of your main router as well as your nodes, looking for clues to see why this is happening every time you make a change to your config.

yeah i'm too much of a novice to do that lol I might just be upgrading everything to AX wifi soon so i'll see if that still happens. Thanks though for the input. I'm wondering does anyone else have a similar setup. I'm also wondering if its Pixelserv cause I do use it for diversion.

 

[ComputerSteve]

https://www.snbforums.com/threads/b...rlin-384-4-beta-is-now-available.44941/page-8 so right at the top of this thread is something that sounds just like my situation. "My RT-AC3200 has an issue where every time I change a wifi related setting, the wifi never turns back on until I remove & reapply power. I did accomplish a factory reset on it." this is just like the situation with AiMesh "Apr 6 18:54:21 RT-AC5300-DEN kernel: br0: port 2(wds0.18) entering forwarding state" --- Looks like this is something with the NAT loopback issue. https://community.spiceworks.com/topic/839187-asus-rt-ac87u-causing-loop-in-network

 

[ComputerSteve]

I was able to pull the log file when this happened and it says -

Apr 6 19:05:51 RT-AC5300-DEN kernel: br0: received packet on vlan1 with own address as source address

 

[ComputerSteve]

This is also in the log that happens right before this issue
Apr 6 18:54:09 RT-AC5300-DEN kernel: br0: port 3(wds0.6) entering forwarding state


Apr 6 18:54:10 RT-AC5300-DEN kernel: device wds0.6 left promiscuous mode


Apr 6 18:54:10 RT-AC5300-DEN kernel: br0: port 3(wds0.6) entering disabled state


Apr 6 18:54:10 RT-AC5300-DEN kernel: EMF_ERROR: Interface wds0.6 doesn't exist


Apr 6 18:54:10 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:10 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:10 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:10 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:10 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:10 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:10 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:10 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:14 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:14 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:14 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:14 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:14 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:14 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:14 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:14 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:15 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:15 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:15 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:15 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:15 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:15 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:15 RT-AC5300-DEN kernel: udb_ioctl_copy_out: no handler for ioctl 0xd:0x4


Apr 6 18:54:15 RT-AC5300-DEN kernel: udb_ioctl_copy_in: no handler for ioctl 0xd:0x3


Apr 6 18:54:17 RT-AC5300-DEN kernel: Register interface [wds0.18] MAC:


Apr 6 18:54:17 RT-AC5300-DEN kernel: device wds0.18 entered promiscuous mode


Apr 6 18:54:17 RT-AC5300-DEN kernel: br0: port 2(wds0.18) entering listening state


Apr 6 18:54:17 RT-AC5300-DEN kernel: br0: port 2(wds0.18) entering listening state


Apr 6 18:54:19 RT-AC5300-DEN kernel: br0: port 2(wds0.18) entering learning state

 

[ComputerSteve]

So Im still having this problem while viewing the logs I see this happening: Then all my nodes change to Unable to Connect To Parent AP
Apr 8 15:15:33 RT-AC5300-DEN kernel: EMF_ERROR: Interface wds2.2 doesn't exist

Apr 8 15:15:38 RT-AC5300-DEN kernel: Register interface [wds2.1]


Apr 8 15:15:38 RT-AC5300-DEN kernel: br0: topology change detected, propagating


Apr 8 15:15:38 RT-AC5300-DEN kernel: br0: port 3(wds2.1) entering forwarding state


Apr 8 15:15:38 RT-AC5300-DEN kernel: br0: port 3(wds2.1) entering forwarding state

Apr 8 15:25:33 RT-AC5300-DEN kernel: br0: port 3(wds0.8) entering forwarding state


Apr 8 15:25:33 RT-AC5300-DEN kernel: device wds0.8 left promiscuous mode


Apr 8 15:25:33 RT-AC5300-DEN kernel: br0: port 3(wds0.8) entering disabled state


Apr 8 15:25:34 RT-AC5300-DEN kernel: br0: port 2(wds2.4) entering forwarding state


Apr 8 15:25:34 RT-AC5300-DEN kernel: device wds2.4 left promiscuous mode


Apr 8 15:25:34 RT-AC5300-DEN kernel: br0: port 2(wds2.4) entering disabled state


Apr 8 15:25:34 RT-AC5300-DEN kernel: EMF_ERROR: Interface wds2.4 doesn't exist


Apr 8 15:25:34 RT-AC5300-DEN kernel: EMF_ERROR: Interface wds0.8 doesn't exist

 

[ComputerSteve]

This is the log right as the problem happens...
Apr 8 15:28:00 RT-AC5300-DEN custom_script: Running /jffs/scripts/service-event (args: restart wireless)


Apr 8 15:28:00 RT-AC5300-DEN syslog: Error unlocking 5: 9 Bad file descriptor


Apr 8 15:28:00 RT-AC5300-DEN syslog: Error unlocking 0: 9 Bad file descriptor


Apr 8 15:28:03 RT-AC5300-DEN kernel: br0: port 3(wds0.9) entering forwarding state


Apr 8 15:28:03 RT-AC5300-DEN kernel: device wds0.9 left promiscuous mode


Apr 8 15:28:03 RT-AC5300-DEN kernel: br0: port 3(wds0.9) entering disabled state


Apr 8 15:28:04 RT-AC5300-DEN kernel: br0: port 2(wds2.2) entering forwarding state


Apr 8 15:28:04 RT-AC5300-DEN kernel: device wds2.2 left promiscuous mode


Apr 8 15:28:04 RT-AC5300-DEN kernel: br0: port 2(wds2.2) entering disabled state


Apr 8 15:28:04 RT-AC5300-DEN kernel: EMF_ERROR: Interface wds2.2 doesn't exist


Apr 8 15:28:04 RT-AC5300-DEN kernel: EMF_ERROR: Interface wds0.9 doesn't exist

 

[ComputerSteve]

Any idea what this stuff means?

 

[ComputerSteve]

So It seems to be that after I change any wifi setting / it makes the wifi service reset & since i'm on wired backhaul not wifi the AP mesh nodes die after the reset & never recover.