One machine on the network (manjaro linux workstation) is being treated unfairly

One machine on the network (manjaro linux workstation) is being treated unfairly

One machine on the network (manjaro linux workstation) is being treated unfairly
One machine on the network (manjaro linux workstation) is being treated unfairly
Thursday - last edited Friday
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.3.0 Build 20250428 Rel.18967

Hi All,

I've recently acquired this router for its dual WAN capabilities. I managed to get Omada controller v5.15.24.19 setup locally without issues.


After turning the router on, before adopting it into the Omada controller,  with the default settings, all devices on my network are connected to the internet without issues. However, one (Manjaro Linux) machine has issues

Issue 1: Connection drops after a few seconds and intermittently comes back after 30s or so to stay up for a few seconds and then drops again
For a few seconds I can connect to the internet and resolve DNS and such. It receives a DHCP lease fine which is maintained when "disconnected". When the internet connection drops; I can still ping all devices on the network but anything like DNS lookup fails. Any ping outside the network fails.

As soon as I make a DHCP address reservation for this machine and add a matching MAC address reservation the connection becomes stable. This leaves me to believe it is not an OS/configuration issue on the client side (I've tried everything). 
These symptoms are consistent between WIFI and ethernet. I think that this rules out driver/chip issues as well. I also have a laptop running Manjaro Linux. None of these issues occur for that client.


I then adopted the router into the Omada controller and configured the DHCP address reservation as well as the MAC address reservation again, but no dice. The connectoin comes up but quickly fails to not provide an internet connection again (exactly the same symptoms). I've tried about every other option to see if that would unlock the use of the Omada controller for me over the router its web UI but nothing does.
 

Issue 2: Cannot access the default gateway ip (192.168.0.1) on port 88 or 443.

I've ruled out that there are any firewall rules or iptables entries that could interfere. The router logs show no mention of any connection attempt. Commandline utilities confirm the connection is being rejected. This occurs both when managed using the router web UI and Omada controller. Other devices on the network can access it without issues.

 

Both issues also occur when running an older firmware version. I've tried disabling IPv6 in each case to no avail.

Any help is appreciated.

  0      
  0      
#1
Options
1 Accepted Solution
Re:One machine on the network (manjaro linux workstation) is being treated unfairly -Solution
Friday - last edited Friday

  @MMGray 

Thank you for your post. When the connection drops, can you still ping 8.8.8.8? Alternatively, could you run a tracert to see where the packets are being lost? We also recommend capturing a mirrored packet trace while the issue is occurring to better analyze the root cause. While capturing, be sure to trigger the problem—for example, by attempting Internet access or trying to reach the device’s Web GUI.You mentioned that manually reserving an IP address on this device resolves the issue. At that point, is the device still connected behind the same gateway? Additionally, have you tried connecting to a different network to see if the problem persists? For instance, you could connect the machine to your phone’s hotspot and check whether the connection remains stable.

How to configure Port Mirror on TP-Link routers

Recommended Solution
  0  
  0  
#2
Options
2 Reply
Re:One machine on the network (manjaro linux workstation) is being treated unfairly -Solution
Friday - last edited Friday

  @MMGray 

Thank you for your post. When the connection drops, can you still ping 8.8.8.8? Alternatively, could you run a tracert to see where the packets are being lost? We also recommend capturing a mirrored packet trace while the issue is occurring to better analyze the root cause. While capturing, be sure to trigger the problem—for example, by attempting Internet access or trying to reach the device’s Web GUI.You mentioned that manually reserving an IP address on this device resolves the issue. At that point, is the device still connected behind the same gateway? Additionally, have you tried connecting to a different network to see if the problem persists? For instance, you could connect the machine to your phone’s hotspot and check whether the connection remains stable.

How to configure Port Mirror on TP-Link routers

Recommended Solution
  0  
  0  
#2
Options
Re:One machine on the network (manjaro linux workstation) is being treated unfairly
Saturday - last edited Saturday

When the connection drops, can you still ping 8.8.8.8? 
No

 

Alternatively, could you run a tracert to see where the packets are being lost?
While connection is up:

```
traceroute -n 8.8.8.8                                                                                                               
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  100.*.*.*  539.978 ms  540.260 ms  540.122 ms
 3  172.*.*.*  540.176 ms  540.133 ms  540.291 ms
 4  206.*.*.*  540.214 ms 206.224.70.4  540.404 ms 206.224.70.8  540.527 ms
 5  206.*.*.*  540.943 ms 206.224.69.254  540.214 ms 206.224.69.244  540.102 ms
 6  206.*.*.*  540.227 ms 206.224.64.137  20.793 ms  20.511 ms
 7  142.*.*.*  20.546 ms  32.486 ms 192.178.110.155  24.288 ms
 8  74.*.*.*  24.325 ms 142.250.46.167  32.630 ms 142.250.213.127  32.518 ms
 9  8.8.8.8  24.261 ms  24.505 ms  32.566 ms
```


While connection is down:
```
traceroute -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
```

 

We also recommend capturing a mirrored packet trace while the issue is occurring to better analyze the root cause

I tested with this setup:
port 1: WAN
port 3: laptop
port 5: problematic PC
Then I mirrored port 1 and 5 to port 3.
On the laptop I used tcpdump to inspect packets. I verified the mirror was working. I am capturing a ping from the PC to the laptop. As soon as it is back up, the mirror shows packets related to ping outside the network (i.e. ping 8.8.8.8). As soon as the connection drops, the packets disappear from the mirror.

 

You mentioned that manually reserving an IP address on this device resolves the issue.
Yes, but only Issue 1. And not al all when configured through the Omada controller.
I do also have to configure DNS servers to avoid using the router ip for DNS to resolve (on other devices this isn't necessary). Either on the client or via the web GUI (ping to 8.8.8.8 then works without the additional step of configuring DNS servers). 

 

At that point, is the device still connected behind the same gateway?
Yes

 

Additionally, have you tried connecting to a different network to see if the problem persists?
Yes, hotspot as well as various routers. It doesn't persist there and appears specific to the ER605.

 

  0  
  0  
#3
Options