Hi @alfaprima 

Thanks for posting in our business forum.

Refer to the troubleshooting guide first. Verify if this is a LAN or WAN issue.

Secondly, ARP issue, you should fix the ARP issue by looking it up in your settings. Is there any duplicate IP address? That would the be root cause for your ARP issue.

Lastly, might consider if the router cannot handle all those devices. 50 devices, what are they? If 50 devices are heavy bandwidth devices, this model is old and may not handle that many devices.

Hi @alfaprima 

Thanks for posting in our business forum.

alfaprima wrote

  @Clive_A 

 

Thank for the reply. 
looking into the different issues:

ARP: the full message is: Detected ARP conflict. Dropped 9 packets. (Packet=192.168.0.199:00-F6-20-7B-7F-39, Bind-Rule=192.168.0.199:00-F6-20-7B-7F-39)

 

In the LAN settings:

20

Google-Home

00-F6-20-7B-7F-39

192.168.0.199

1:59:34

---

 

Address Reservation:

39

00-F6-20-7B-7F-39

192.168.0.199

Google-Home

 

The device its an old  Google Home speaker 

I can't spot the problem from this information. 

 

50 Devices: 
we have a home office (hence the need of 2 internet providers),  we don't host anything inside, and the volumen of traffic si not high.

Many of the devices are IOT devices, and other network connected devices like printer and TV. Again the use is low.

 

C:\Users\jp>ping 192.168.0.1 -t

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=17ms TTL=64
Reply from 192.168.0.1: bytes=32 time=31ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=42ms TTL=64
Reply from 192.168.0.1: bytes=32 time=269ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=23ms TTL=64
Reply from 192.168.0.1: bytes=32 time=73ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 269ms, Average = 52ms

 

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1     3 ms     2 ms     4 ms  192.168.0.1
  2   433 ms   208 ms     5 ms  192.168.10.1
  3    27 ms    13 ms    10 ms  10.161.10.161
  4    12 ms    16 ms    11 ms  mx-str-1-ae115-300.voo.be [78.129.125.45]
  5    19 ms    27 ms   116 ms  mx-lvl3-2-ae8-0.voo.be [212.68.211.169]
  6    88 ms    28 ms   282 ms  192.168.175.13
  7     *     2838 ms   203 ms  mx-lvl3-2-ae20-0.voo.be [212.68.211.144]
  8    21 ms    18 ms    16 ms  mx-bxl2-2-ae1-0.voo.be [212.68.211.21]
  9     *        *        *     Request timed out.
 10   193 ms    19 ms    24 ms  216.239.54.185
 11    21 ms    20 ms    14 ms  209.85.254.113
 12   130 ms    18 ms    18 ms  dns.google [8.8.8.8]

Trace complete.

 

Will redo this when the issue happens again.

 

1. Fix the ARP issue. If you don't fix it, I cannot rule out this variable. So, there is no need to go further because I think it is the reason why here while nothing useful is provided as evidence to lead the troubleshooting.

2. The PC you used for the test is getting this high ping. Is it on WIFI? Use the wired and does it get this high ping?

3. This shows the issue is on your 192.168.10.1 router. Have you checked the connection between 0.1 and 10.1?