Bridge port received packet with own address as source, probably loop

Common sense is under-utilized these days. By many people.

Mikrotik has confirmed that this is an issue with neighbor discovery.
But since they assume that this is just a cosmetical issue, a time/date for a fix of this issue will be in the far future.

it’s mean that probleam can be resolved by disabling neighbor discovery?

Hello

I had this issue a while back but forgot how I solved it.

I have a software vlan setup with 8 VLANs, one of which is a Telco only vlan. If memory serves, I only kept the associated bridge of that vlan as a neighbour enabled interface, along with physical interfaces.

Cheers,


Sent from my cell phone. Sorry for the errors.

Hi All,

I have this problem only on my DiscLite5 (Boardname=RBDisc5nD), when a change to new Disclite5 (Boardname=RBDisc-5nD), the problem solved.
Until now, around 8 units of disclite5 was changed to new Disclite w/ new broadname.
The problem is with the hardware or firmware, I think.

I have tried to make ether 1 Mac as admin Mac on the AP and wlan1 on the station, but no luck.

It seems disabling neighbor discovery solves the false positive alerts (that were generated exactly every 1 min):


[adm@SW2-DIS-01] > ip neighbor discovery-settings print 
  discover-interface-list: none
[adm@SW2-DIS-01] >

This likely means that you cloned your first device to your second (e.g. by restoring a backup) and thus created a dup MAC address on your network.

I’ve resolve the issue.
My configuration consist of three routers, one is capsman, two of them are used for caps. On one of the caps the bridge mac was inherit from the wlan1 and the capsman uses the same mac address on his virtual cap interface.
I’ve change the bridge mac with the ether1’s mac.

I got the “…probably loop” error logs and after all I figured out a missconfigured wirless mode. In my case I had a point-to-point connection, one end with mikrotik wireless in mode=bridge and the other end was just in “mode=station”, not as expected in “mode=station bridge”. Correcting the mode to “station bridge” makes the link work perfectly and no more “… probably loop ..” error logs.

It is sign of mac address conflict. reset mac addresses of each interface and set auto-mac=yes for all bridges.

It is mostly caused by restoring backup of a router to another.

as pe1chl said, check all your interface’s mac address

specially (i guess) the bridge mac address because it can be the same of one of the ports on the same equipment and it seems it makes it to work worse regarding that.

on the other half, check if you have a slow link or a WDS one, i had the same problem while testing a WDS link with another brand’s equipment AND making mikrotik’s bandwith tests on firmware 6.43.14. i wont go on further details to not make it more confusing because i have spent a lot of time on this and finally i gave up and restored the original CPE without WDS link. But it was strange to have this loop log regarding the eth interface mac (even after changing the bridge’s one and having a bit better results)

cheers

Same problem here and posting some of my experience that may help.
I Have the same issue from time to time. Once the cause was of 2 lhg link connected as point to point with wireless “bridge” mode on ap with wds dynamic enabled and the wds default bridge is the bridge that contain the eth and wlan interfaces and “station wds” wireless mode on the station side. I solved it by removing the wlan interface from the bridge of the ap because I noticed that the wds interface is added to the bridge dynamically and the bridge will contain 3 port (eth,wlan and wds dynamic interface).
But sometimes I can’t know the reason. I use omintik with poe a lot and make them as ap bridge and connect it from the main station with a link. It helps me a lot. I usually use mikrotik and ubitquiti to connect my stations together and also for clients. Some stations will have the probably loop error on the log of the omnitik and cause pppoe sessions to disconnect a lot.
The newest problem now is that I have an omintik that was working fine with no probably loop error. A new client wants to connect to the omnitik ap bridge but there was a problem with resetting his sq lite mikrotik (the user led will blink slowly when trying to reset) so I decide to use the sq lite station of his brother who is already a client of my clients. I use vlans as different ISP so the station wds contains a vlan interface hosted on the wlan(which is the trunk in my case) and placed it in a bridge with the ether. I placed a tp-link router and used it as a switch after disabling dhcp and changing its default ip because I wasn’t having a dummy switch and connected the 2 routers to the bridge ports of the tp-link router with pppoe connection on wan interfaces of the 2 routers. Everything worked fine after few days I noticed that the omintik started to give the probably loop error and pppoe users are disconnected periodically, and I am sure that there is no duplicate mac address in this station because all my configs are from scratch.
So the cause is placing a switch after the station wds client mode.
I am going to replace this router which I used the 4 ports bridge of it with a netis 8 port 10/100 mbps switch and watch if the error occurs again.

I had the same problem recently, and I was able to resolve the issue.
If you go to IP-Neighbors, and there you should see the same interface repeating for two different MAC.
In this case the router is giving you the correct information that there is a loopback,
In my case the problem was with a switch connected to one of repeated ports that I so on IP - Neighbors on the router that was causing the problem

hope this will help

INFO:
RB951 ROS 7.1.3

I encounter that problem just now
STEPS TAKEN:
-reboot = not fixed
-unplug ethernet cable then plug back = not fixed
-move cable to different port = not fixed

SOLUTIONS:
-disable nic in /interface (in my case ether4) then enable back

[quote=rakiburrahaman post_id=1028316 time=1696330479 user_id=224156]
After applying all the possible solution form google the success was 0 for me then i just delete the bridge from my mikrotik rb4011 and configure a single port as lan which i connect to a 24 port gigabit switch everything is going smoothly & no more loop no network down :pensive_face::pensive_face:
[/quote]
Just SPAM: It doesn’t make any sense, you didn’t ask for help on the forum and the cause of everything could simply be you who weren’t able to configure the device correctly.