I keep getting these conflicts every morning at virtually the same time.
Tried to figure out where its coming from but totally stumped. Found 2 other threads on similar error messages. In one it said (obviously) 2 devices have been manually set to the same IP.
Nothing is set manually on the network. Its all DHCP Reserved. And Peplink still cannot set IPV6 addresses afaik.
I do not even use IPv6 on the network.
Who exactly is “our MAC address”?
And how can I track this down and correct?
Jun 14 05:22:43
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 14 05:22:43
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 14 05:22:41
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 14 05:22:41
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 14 05:22:22
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 14 05:22:22
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 13 05:22:37
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 13 05:22:29
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 12 05:22:36
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 12 05:22:36
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:44
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:44
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:33
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:33
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:32
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:32
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:32
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:32
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:29
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:29
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:28
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:28
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:28
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:28
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:27
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:27
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:26
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 11 05:22:26
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 10 18:59:17
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 10 18:59:17
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 10 18:55:30
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 10 18:55:30
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 10 08:01:56
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 10 08:01:56
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 10 05:22:48
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 10 05:22:48
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 10 00:07:56
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 09 05:22:42
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 09 05:22:38
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 08 05:28:07
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 08 05:28:07
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 08 05:22:51
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 07 05:22:53
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 07 05:22:53
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 07 05:22:47
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Jun 07 05:22:47
MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78
Hi, this is a MAC address conflict from a wired device within your local network.
This error always appears like this for some odd reason from time to time.
The way I have been able to fix and pinpoint problem is to start unplugging/disabling ports until the error stops and then work down equipment from that port To switches and AP. Once you see the error stop showing up, it’s on that connection.
Best I can do to help you track down the phantom device.
What is the full IPv6 IP you are getting the error about?
It appears it might be the same exact IP I am seeing in the error from.
If so, THIS CANNOT BE A RANDOM COINCIDENCE
And the most ridiculous part of this is that Peplink doesn’t even support IPv6 so it cannot possibly be from “our” MAC address 10:56:ca:14:65:78 (nor am I using any IPv6 addresses on my network because of the Peplink limitation).
I have spent the last 48 hours doing the steps you listed.
One by one, I have unplugged every wired connection, only reinserting after the error Is logged.
The only device left was a Dell X1052p Switch which was used out of the Peplink unit.
After observing the error after a one by one unplug, I pulled out the X1052p and inserted an older switch temporarily.
I am still seeing the error.
So there is no device on my LAN that I can see is causing it.
Again, as the IP is IPv6 and I am not using IPv6 on my network, nor is Peplink IPv6 compatible but the IP appears to be the same for multiple user, this has to be a Peplink Firmware issue.
@BeachComber1, I would advise opening a ticket then on the device then if you are questioning the firmware.
When I opened a ticket within the last 2 years for the same issue they pointed out it’s a LAN device issue. Never stated wired/wireless or how to find it. I just started pulling cables and waiting. I also rebooted literally 90+ devices manually to track it down and it was an old wired camera.
@BeachComber1, not ignoring your questions, the forum is not iPhone/multi tab friendly. i missed the one question. I do understand your frustration with seeing an error for no reason.
As for your initial issue, a normal IPv4 address is similar to what you posted. If you look up an IPv6 address, on Google, you will see it’s significantly longer.
To answer your question about the same MAC ID on the LAN is that similar models might be programmed that way by Peplink’s firmware. I will confirm many of my devices LAN IPv4 addresses follow the exact same format as yours, but will differ slightly.
A year later, hours upon hours (actually days) spent attempting to identify the cause and this issue continues to take down my WiFi daily for a minute, usually at 05:21 or 5:22 AM, but times sometime vary for unknown reasons.
I am confused how Peplink Balance is reporting “MAC address conflict: Received packet claiming to be from our MAC address 10:56:ca:14:65:78” (Bold mine to emphasis) as Peplink does not use IPv6 so how can it be “our” (Peplink Balance).
Wow, so much misinformation and misunderstanding of what a MAC address is in the posts above…
MAC addresses are layer 2 addresses that are supposed to be unique to any device in a given segment of a network.
IPv4 and IPv6 addresses are layer 3 in the OSI model and do not have any relevance here, just because IPv6 also uses a hex format rather than decimal does not mean any of the log entries posted above related in any way to whatsoever to IPv6.
The MAC address in the original post “10:56:ca:14:65:78” is indeed a Peplink MAC, the clipped screenshot just happens to show a similar starting MAC address also a Peplink one, that is just because the first 3 bits of the MAC are the Vendor OUI and 10:56:CA is assigned to Peplink.
If you log into your Peplink and go to Status > Device does that MAC Address match any of the listed ones for the interfaces listed there? That could help you start working out where to look, but as suggested already you quite likely have a device on your LAN that is doing something to trigger this.
Most common cause of these kinds of errors are the result of a loop in the network somewhere, or you have a device behaving in a very bad way that for whatever reason is using the MAC address of your Peplink as its own interface to source packets from.
Do you have any kind of wireless meshing system in use, where the mesh paths may change which could relate in a temporary situation where a loop may occur over the wireless side of that network?
If you disconnect everything LAN side from the Peplink and access the logs via Ic2 and the error is still there then potentially this is some very funky hardware or software issue, you could also try bumping your firmware to 8.2 or downgrading if you believe it was a firmware upgrade that triggered this - there were some bugs where certain broadcast packets were being passed from LAN to WAN but that was resolved some time ago.
I agree with @WillJones , the 10:56:ca:14:65:78 is a layer 2 MAC (Media Access Control) address and not an IPV6 address. They look similar, but IPv6 addresses will have 3 or more characters between the semicolons.
Is this error message showing up on your router? Or is it showing up on your access point?
Tell us a bit about your network setup… What Peplink device are you using for your router? Is there any kind of HA running on it>? What wireless access points are you using? Are all APs connected via a wire? Are any APs connected via mesh? Do you have any switches in the network? Are they “smart” switches?
Peplink routers have multiple MAC addresses, one for LAN and one for each WAN/USB interface. If you go to the Status->Device page, they will be listed at the bottom of the page. Which interface is the MAC address from the error message? If it is one of the WAN interfaces – what kind of modem is connected to that WAN port? I would be surprised if one of the WAN interfaces is the culprit - it is more likely that it is a LAN device causing it…
The fact that it happens around the same time every day might be helpful in sorting this out… If this error message is showing up on your router, then the next step would be to find out which physical interface the packet is coming in on. You can do that by unplugging one LAN port every day at 5:20 until the issue ceases. Once you know which port the traffic is coming from - you can start going down that link until you find the culprit. What time does you daily channel scan occur on your APs?
Good Morning BeachComber - I have been reading this string and wonder if you ever resolved this?
I have had this happen, and I have tried all of the suggestions, and it comes back. I have less than 15 devices on this network so unplugging them is not an issue - the issue is trying to recreate the issue while onsite (not going to happen),
Is the problem still happening?
Actually it resolved itself when firmware v8.3 was released
Wasnt an issue from an errant device on my network at most responses concluded, unless you count the Peplink Balance as an errant device on my network.
Was a Peplink unit error from the old firmware. The Peplink LAN 1 port was pinging itself apparently every morning about 05:20AM local everyday for over 2 years for some reasons no one has explained to me.
