I’m using a Peplink Balance 20 (firmware 5.4.9 build 1732) for my home and home office network (so, 5-10 devices on the network). I’m using it to connect to MediaCom (Motorola surfboard cable modem - working fine) and ATT U-verse (2Wire 3801HGV - not working as well). I’ve done a fair amount of reading online about problems with ATT U-verse and the Peplink, but I haven’t been able to resolve my problems.
The reasons I think the ATT connection is giving me the problem are:
- It seems others have been having similar problems with ATT
- The Peplink logs (see below)
With Health Check turned on, the MediaCom connection will create “WAN failed DNS test” errors in the log file (and disconnect/reconnect) a few times per week:
Jun 22 16:26:18 WAN: MediaCom connected (173.21.xxx.xxx)
Jun 22 16:25:27 WAN: MediaCom disconnected (WAN failed DNS test)
Jun 19 19:15:58 WAN: MediaCom connected (173.21.xxx.xxx)
Jun 19 19:14:07 WAN: MediaCom disconnected (WAN failed DNS test)
Jun 16 01:16:08 WAN: MediaCom connected (173.21.xxx.xxx)
Jun 16 01:04:25 WAN: MediaCom disconnected (WAN failed DNS test)
Jun 11 10:41:21 System: Changes applied
For the log entries above, I had manually turned off the ATT connection from June 11 through June 23. A few times a week doesn’t bother me, so I’m not worried about the MediaCom connection.
However, the ATT U-verse connection will disconnect/reconnect every few minutes with the Health Check turned on:
Jun 25 13:22:19 WAN: U-verse connected (172.1.yyy.yyy)
Jun 25 13:22:13 [1223999.836000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:22:13 [1223999.756000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:22:03 [1223989.676000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:21:43 [1223969.516000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:21:22 WAN: U-verse disconnected (WAN failed DNS test)
Jun 25 13:21:22 [1223949.288000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:18:56 [1223803.308000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:18:16 [1223763.280000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:18:13 WAN: U-verse connected (172.1.yyy.yyy)
Jun 25 13:18:12 [1223758.720000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:18:02 WAN: U-verse disconnected (WAN failed DNS test)
Jun 25 13:14:55 [1223562.212000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:14:15 [1223522.176000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:14:12 WAN: U-verse connected (172.1.yyy.yyy)
Jun 25 13:14:11 [1223517.704000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:13:41 WAN: U-verse disconnected (WAN failed DNS test)
Jun 25 13:13:40 [1223487.380000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:09:45 [1223252.100000] MAC address conflict: Received an ARP packet claiming to be from our MAC address 10:56:CA:06:F1:31, but with an unknown IP (172.1.yyy.yyy)
Jun 25 13:09:09 System: Changes applied
For the u-verse WAN connection, I have filled in the DNS server 1 and DNS server 2 addresses manually under “DHCP Settings” with the DNS servers that my computer got when I connected it directly to the 2wire. The “Include Public DNS servers” option is selected under Health Check Settings. I’ve also tried filling in the Health Check DNS Servers with Google’s public DNS servers. Neither of these seemed to have much of an impact. I changed the “Timeout” setting to 10 seconds, and that seemed to reduce the frequency of the “WAN Failed DNS test” errors, but didn’t impact the “MAC address conflict” errors.
I would appreciate any help to try to resolve these errors, and any insight into what might be causing them. I’m reasonably savvy with IT issues, but I’m no network expert. I can’t seem to find anything on the “MAC address conflict” error.
Thanks in advance,
tom