Wired computer to slave AP gives red light
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have setup my third AP and wired a computer to one of the ethernet jacks on it. Everything works initially, I can access it, speed is decent (maxing out my 250 Mbit internet connection), however if use it moderately (streaming 15Mbit of data from it), latency increases significantly (800-1200ms) and eventually it switches to red light and the computer looses connectivity with the router.
Now, even weirder, I can still access the computer via another device on Wifi, meaning I can ping it, ssh into it, but from the computer, it can't reach the router (main AP), nor anything from the internet. I can, however, ping the other AP (which is connected to the main router),
Not sure if this is a hardware fault or if it just isn't capable of running such a setup... the fact that the whole network grinds to a halt just because one of the wired ports are using bandwidth seems like a software problem, also the fact that some traffic gets blocked, but not all.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello, we would like to do further troubleshooting to locate this issue and try to figure it out.
1. What is the current network diagram?
2. With this computer connected to the slave Deco by wirelessly, does it have the same issue?
3. Try to connect the main Deco to the modem only, with other slave Decos off, and then you can wired this computer to the main Deco and verify whether it works well with streaming service.
4. Please click here to get the IP address and gateway of the computer when the Deco changes to red; and you can get the IP address of the red led Deco on the Deco app. Note: please show us the results.
5. Have you ever tried to swap the locations of the Deco units or switch the slave Deco to the main Deco to give it a shot?
Thanks a lot. Good day.
- Copy Link
- Report Inappropriate Content
@Kevin_Z Hi, I did a test and swapped my two slaves (of which one never experienced this problem), and ran for a day and now the other one shows the same symptom. Hence, it is not a hardware problem, it is the wired devices to it. I also have a printer connected, which might also be the culprit, I'll try and disconnect it next.
The PC was previously wired to the main router, without any problems, hence that test would be redundant. When it disconnects, this shows up in the main deco logs (192.168.68.106 is the slave AP that gets flagged as disconnected):
Fri Mar 20 22:05:19 2020 daemon.err udhcpd[5346]: Found static lease: c0a8446a
Fri Mar 20 22:05:19 2020 daemon.err udhcpd[5346]: Sending OFFER of 192.168.68.106
Fri Mar 20 22:05:19 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.106
Fri Mar 20 22:05:19 2020 user.err syslog: Error: connect
Fri Mar 20 22:05:19 2020 daemon.err udhcpd[5346]: Found static lease: c0a8446a
Fri Mar 20 22:05:19 2020 daemon.err udhcpd[5346]: Sending OFFER of 192.168.68.106
Fri Mar 20 22:05:20 2020 daemon.err udhcpd[5346]: Found static lease: c0a8446a
Fri Mar 20 22:05:20 2020 daemon.err udhcpd[5346]: Sending ACK to 192.168.68.106
Fri Mar 20 22:05:20 2020 daemon.err udhcpd[5346]: clear ip c0a8446a
Fri Mar 20 22:05:20 2020 daemon.err udhcpd[5346]: Found static lease: c0a8446a
Fri Mar 20 22:05:20 2020 daemon.err udhcpd[5346]: Sending ACK to 192.168.68.106
Fri Mar 20 22:05:20 2020 daemon.err udhcpd[5346]: clear ip c0a8446a
Fri Mar 20 22:05:30 2020 user.err syslog: Error: ssh_connect: No route to host
Fri Mar 20 22:05:30 2020 user.err syslog: Error: connect
Fri Mar 20 22:05:48 2020 user.err syslog: Error: ssh_connect: No route to host
Fri Mar 20 22:05:48 2020 user.err syslog: Error: connect
Fri Mar 20 22:06:07 2020 user.err syslog: Error: ssh_connect: No route to host
Fri Mar 20 22:06:07 2020 user.err syslog: Error: connect
Fri Mar 20 22:06:08 2020 daemon.err client_mgmt: wireless client associate or disassociate.
Fri Mar 20 22:19:53 2020 daemon.err uhttpd[7035]: ath22 no frequency information.
Fri Mar 20 22:19:53 2020 daemon.err uhttpd[7035]:
Fri Mar 20 22:20:08 2020 daemon.err uhttpd[7035]: ath22 no frequency information.
These in the end about ath22 started att 22:19 and didn't occur earlier (although I only have about 2h worth of logs.
On the slave Deco, at the same time, this shows up:
Fri Mar 20 22:05:17 2020 daemon.err udhcpc[8261]: Received SIGTERM
Fri Mar 20 22:05:18 2020 daemon.err udhcpc[8209]: udhcpc (v1.22.1) started
Fri Mar 20 22:05:18 2020 daemon.err udhcpc[8209]: Sending discover...
Fri Mar 20 22:05:19 2020 daemon.err udhcpc[8209]: Sending select for 192.168.68.106...
Fri Mar 20 22:05:20 2020 user.emerg syslog: tp217,505[8255]:
Fri Mar 20 22:05:20 2020 user.emerg syslog: tp217,504[8255]:
Fri Mar 20 22:09:21 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Fri Mar 20 22:09:21 2020 user.err syslog: Error: connect
Fri Mar 20 22:11:31 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Fri Mar 20 22:11:31 2020 user.err syslog: Error: connect
Fri Mar 20 22:11:39 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Fri Mar 20 22:11:39 2020 user.err syslog: Error: connect
Fri Mar 20 22:17:11 2020 daemon.err nrd[4702]: send ioctl failed
Fri Mar 20 22:17:24 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Fri Mar 20 22:17:24 2020 user.err syslog: Error: connect
Fri Mar 20 22:17:30 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Fri Mar 20 22:17:30 2020 user.err syslog: Error: connect
Fri Mar 20 22:17:34 2020 daemon.err conn-indicator: 1th attr(data) not found
Fri Mar 20 22:17:34 2020 daemon.err conn-indicator: Invalid response
Fri Mar 20 22:17:53 2020 daemon.err nrd[4702]: send ioctl failed
Fri Mar 20 22:17:54 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Fri Mar 20 22:17:54 2020 user.err syslog: Error: connect
Fri Mar 20 22:18:04 2020 daemon.err conn-indicator: 1th attr(data) not found
Fri Mar 20 22:18:04 2020 daemon.err conn-indicator: Invalid response
Fri Mar 20 22:18:20 2020 daemon.err nrd[4702]: send ioctl failed
Fri Mar 20 22:18:25 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Fri Mar 20 22:18:25 2020 user.err syslog: Error: connect
Fri Mar 20 22:18:35 2020 daemon.err conn-indicator: 1th attr(data) not found
Fri Mar 20 22:18:35 2020 daemon.err conn-indicator: Invalid response
Fri Mar 20 22:18:44 2020 daemon.err nrd[4702]: send ioctl failed
Fri Mar 20 22:18:55 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Fri Mar 20 22:18:55 2020 user.err syslog: Error: connect
This keeps repeating, and then this starts here as well:
Fri Mar 20 22:21:57 2020 user.emerg syslog: tp215,22[24365]:
Fri Mar 20 22:21:58 2020 daemon.err uhttpd[6390]: ath22 no frequency information.
Fri Mar 20 22:21:58 2020 daemon.err uhttpd[6390]:
Fri Mar 20 22:22:05 2020 daemon.err nrd[4702]: send ioctl failed
Fri Mar 20 22:22:06 2020 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Fri Mar 20 22:22:06 2020 user.err syslog: Error: connect
Fri Mar 20 22:22:19 2020 daemon.err conn-indicator: 1th attr(data) not found
Fri Mar 20 22:22:19 2020 daemon.err conn-indicator: Invalid response
Fri Mar 20 22:22:30 2020 daemon.err nrd[4702]: send ioctl failed
If I reboot either this slave (192.168.68.106) or the main deco, it all works fine again. As I said, some link connectivity still works, I can connect the the slave deco, the wired computer into the slave deco, but the wired computer can not reach the main deco for some reason, nor internet. Also, no wireless client that associate with this slave deco, will reach internet.
- Copy Link
- Report Inappropriate Content
Actually, scrap that last part. Rebooting the slave doesn't work, it it still stuck in that loop
Tue Sep 17 15:22:46 2019 user.err syslog: Error: ssh_connect: Timeout connecting to 192.168.68.1
Tue Sep 17 15:22:46 2019 user.err syslog: Error: connect
Tue Sep 17 15:22:58 2019 user.emerg syslog: tp215,22[25743]:
Tue Sep 17 15:22:59 2019 daemon.err uhttpd[6321]: ath22 no frequency information.
Tue Sep 17 15:22:59 2019 daemon.err uhttpd[6321]:
Tue Sep 17 15:23:07 2019 daemon.err conn-indicator: 1th attr(data) not found
Tue Sep 17 15:23:07 2019 daemon.err conn-indicator: Invalid response
Only rebooting the main deco seems to fix it.
- Copy Link
- Report Inappropriate Content
Actually, I think it might not be related to the computer at all, but my printer that I also connected at the same time, a Lexmark c417n. I disconnected it to rule out and now it has been fine for two days.
Not sure though why that would cause the AP to be blocked for certain traffic. Have any suggestion on what to troubleshoot? Have you heard of similar behavior with other devices?
- Copy Link
- Report Inappropriate Content
I already answered some of those questions.
Main deco
- No wired units
Slave 1
- Phillips Hue bridge
- Sonos Boost
Slave 2 (the one getting disconnected)
- Computer running Linux Debian
- Printer Lexmark CS417dn
Slave 2 unit wasn't previously used, and computer was wired directly to Main deco without any issues.
I swapped Slave 1 and Slave 2, to see if it was a problem with the hardware. Then the other slave (Slave 1) suffered from the same issue (when the same devices was wired to it). This should rule out a hardware fault.
When the issues occur, all devices have the same IP-addresses as it had before. I can even connect to the wired devices on Slave 2 from another wireless device. I can also access the web interface of both the main deco, and the slave decos, but Slave 2 is listed as disconnected in the Deco app. I can not test the computer nor the printer wirelessly since they don't have a wireless card. Everything points to the main deco blocking some traffic from the Slave 2 deco, but since I can access the wired devices from a wireless device that is associated with the main deco, it seems to only affect traffic that is targeted to the main deco (AP control traffic, or being used as an internet gateway). Pinging the Main deco from any device that is connected to the Slave 2 is timing out.
All things point to the printer being the culprit, because I've had it disconnected for two days and this problem has not happened since. Not sure what kind of traffic the printer can send to cause this issue though.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1360
Replies: 5
Voters 0
No one has voted for it yet.