Deco M5 disconnecting when Linux PC is on?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I just installed a 3-set Deco M5 in Router mode.
Devices are connected with ethernet backhaul and everything looks good.
I got a small Gigabyte Brix that is running headless Debian with some docker containers. Every time that I power on this device the main Deco M5 goes red and internet is disconnected. This usually happens when the Brix has been connected for some minutes. A few days ago the device was connected for about 7 hours before the Deco disconnected, but usually it's just some minutes.
The Brix is getting a DHCP IP from the Deco and is just a regular client.
Why is this happening?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
To locate the issue , please help to check and provide the following info:
1. What is the firmware version on your M5? How about the hardware version?
2. Do you have any Advanced settings on the Deco M5? Such as QoS etc?
3. How can you get the internet back on the main Deco? Do you need to restart the device? Or it will work once the Brix is disconnected from the system?
4. Please tell more details about the Brix. How it works on internet connection?
- Copy Link
- Report Inappropriate Content
This is info on the Decos:
Model: Deco M5
Hardware Version: V1
Firmware Version: 1.3.0 Build 20190419 Rel. 70702
2. I have 4 port forwarding rules and QoS set to Streaming. Two devices are set to high priority (the Brix is not one of them).
3. To get the system going I need to disconnect and reconnect power on the main deco unit. If the Brix is still connected to the network the deco will turn red after a short time. If I disconnect or power off the Brix it stays green.
4. The Brix got a standard Debian 9 headless installation and is connected to a Netgear GS108 switch connected to the main Deco. It's receiving an IP from the Deco DHCP server.
Are there some way to see a log for the Deco system? To know what happens when it turns red?
- Copy Link
- Report Inappropriate Content
Please draw a network topology which shows how you connect your modem, switch and Deco devices.
Please note that, when the Deco works in the Router mode, only the main Deco can connected to the front-end modem/router by an Ethernet cable, the other slave Deco can only connected to the main Deco’s network via Ethernet cable/Wi-Fi.
- Copy Link
- Report Inappropriate Content
The topology is pretty standard with modem - Deco - Switch - Deco/Deco/Linux PC
During some more troubleshooting I first found that when I shut down Docker on the Linux machine the network stayed up. From there I started one conainer after the other and found one specific container to bring the network down. I don't know why, but I just stopped using that container and the network works.
I do however see lots of various errors in the logs from the main Deco.
Fri Jun 7 08:00:57 2019 daemon.err udhcpd[7039]: Sending OFFER of 10.0.0.158
Fri Jun 7 08:00:57 2019 daemon.err udhcpd[7039]: Sending ACK to 10.0.0.158
Fri Jun 7 08:00:57 2019 daemon.err udhcpd[7039]: clear ip 9e00000a
Fri Jun 7 08:01:02 2019 daemon.err udhcpd[7039]: clear ip a400000a
Fri Jun 7 08:01:02 2019 daemon.err udhcpd[7039]: Sending OFFER of 10.0.0.164
Fri Jun 7 08:01:02 2019 daemon.err udhcpd[7039]: Sending ACK to 10.0.0.164
Fri Jun 7 08:01:02 2019 daemon.err udhcpd[7039]: clear ip a400000a
Fri Jun 7 08:03:12 2019 daemon.err udhcpd[7039]: Sending ACK to 10.0.0.160
Fri Jun 7 08:03:12 2019 daemon.err udhcpd[7039]: clear ip a000000a
Fri Jun 7 08:06:20 2019 daemon.err udhcpd[7039]: clear ip 9e00000a
Fri Jun 7 08:06:20 2019 daemon.err udhcpd[7039]: Sending OFFER of 10.0.0.158
Fri Jun 7 08:06:20 2019 daemon.err udhcpd[7039]: Sending ACK to 10.0.0.158
Fri Jun 7 08:06:20 2019 daemon.err udhcpd[7039]: clear ip 9e00000a
Fri Jun 7 08:07:01 2019 daemon.err udhcpd[7039]: clear ip 9e00000a
Fri Jun 7 08:07:01 2019 daemon.err udhcpd[7039]: Sending OFFER of 10.0.0.158
Fri Jun 7 08:07:01 2019 daemon.err udhcpd[7039]: Sending ACK to 10.0.0.158
Fri Jun 7 08:07:01 2019 daemon.err udhcpd[7039]: clear ip 9e00000a
Fri Jun 7 08:08:11 2019 daemon.err uhttpd[3390]: ath22 no frequency information.
Fri Jun 7 08:08:11 2019 daemon.err uhttpd[3390]:
Fri Jun 7 08:08:16 2019 daemon.err uhttpd[3390]: ath22 no frequency information.
Fri Jun 7 08:08:16 2019 daemon.err uhttpd[3390]:
Fri Jun 7 08:08:48 2019 daemon.err udhcpd[7039]: Sending ACK to 10.0.0.157
Fri Jun 7 08:08:48 2019 daemon.err udhcpd[7039]: clear ip 9d00000a
Fri Jun 7 08:09:05 2019 daemon.err uhttpd[3390]: ath22 no frequency information.
Fri Jun 7 08:09:05 2019 daemon.err uhttpd[3390]:
Fri Jun 7 08:09:05 2019 daemon.err uhttpd[3390]: ath22 no frequency information.
Are these normal?
- Copy Link
- Report Inappropriate Content
@Jepsh did you ever find the culprit for this issue? I have a Deco M4 setup and just recently wired my third access point and wired my Linux server to it.
However, after some time (and mostly when it has constant traffic), that AP will switch to red and give me similar logs as you are describing (not sure if they are common or not).
But the wierd thing is that when the Deco goes red, I can still access the server from another device on the network, but the server in itself can no longer access the main router (192.168.68.1) nor anything on the internet.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2410
Replies: 5
Voters 0
No one has voted for it yet.