We’re having a problem on the LAN at one of our sites in which we’re getting an error that says “WLAN1: bridge port received packet with own address as source address . . . probably loop.” The router that is logging the error is the first wireless client in the chain of hops, so it’s the closest one to our gateway router. WLAN1 is configured as a station bridge, and it connects to a tower that is an AP bridge. A total of four station bridges connect to the tower.
We physically inspected throughout the site for cabling problems that could cause a spanning tree loop, and checked for loops in our wireless connections and found none. We tried blocking all the remote stations with an access list and brought them back up one by one to see if we could determine where the problem was occurring. I brought up one station with no problem. I was able to recreate the problem by then letting two different stations connect to the tower access point individually. We replaced the access point on the tower, and the problem persists. We have over 90 sites with MikroTik wireless backhauls, and we’re only having this problem at one site. Any ideas as to what might cause this problem?
All MikroTik devices at this site are running RouterOS 6.38.1. We have one switch running SwitchOS 1.17.
Are you sure that you did not copy the MAC address from one place to another?
This can happen when you restore a backup of one device on another, or import an export which has MAC addresses in it.
E.g. when you “convenient rollout plan” has been to restore a backup of a single configured client onto every client’s AP,
you will have surprises like this.
No, both configurations are done from scratch with default settings first after the problems are coming with the news ROS.
Editing of the Neighbor Discovery setting have not solve the problem.
But setting on both units (AP and CPE) the MAC address of the unit’s wireless interface as Admin MAC address of the bridge, this brings a stable connection (current link uptime > 1 hour and a very low PING time)
The bridge error message for having a loop is also gone away. At the moment, everything is working fine.
This points in the direction I mentioned. Check all MAC addresses in the system to see if they are unique.
(wlan1, ether1, bridge on all connected devices)
I’ve also started having this issue over the weekend.
I’ve checked and rechecked MAC addresses but there don’t seem to be any duplicates and I’ve disabled anything not used.
If I shut off the router (and switch it’s plugged into) for a minute or two the issue clears, but then comes back after X amount of time (sometimes it’s an hour, sometimes it’s six).
Mostly just throwing in my 2 cents as this seems to be a new issue that a few people are experiencing around the same time.
Hi
I’m having the same problem and it occurs at random times only once or twice and then nothing for hours. I downgraded to ros5.25 and it stopped. I would suspect a clash between the way ubiquity handles bridged connections and Mikrotik’s way
I had the same problem at a device with capsman. I solved it by removing bridge from all cap devices. Now discovery interface is ether1 and not bridge1.
I have this problem since before I bought mikrotik.
There’s a chance that this error is trigger whenever I open a specific computer. Sometimes it works Fine and sometimes Give me this error.
I have many computers connected in hub which conneted to router(mikrotik) and then to modem. I have motherboard of gigabite Jetway and Asrock.
Only This Asrock Give me error. As I checked its lanport Only Thing Than get my attention is the light that it immit. As I believe normal color should be lightgreen and orange blinking but, this one immit orrange and red. I checked other pc And I found out theres 2 of my computer that immit such different light. after That nothing in the internet could explain me better. All I got is that Other light than lightgreen and orange has low transfer rate of data bites. though Internet speed is normally working fine as It should be.
Can someone gues whats might occuring this instances?
12:31:43 interface,warning WRN: vlan102: bridge port received packet with own address as source address (e4:8d:8c:d5:4e:1d), probably loop
12:32:16 interface,warning WRN: vlan102: bridge port received packet with own address as source address (e4:8d:8c:44:2d:43), probably loop
12:32:25 interface,warning WRN: vlan102: bridge port received packet with own address as source address (6c:3b:6b:52:67:c2), probably loop
Here’s a quick overview of my setup.
I have vlan interfaces, using a bridge called BR-TRUNK for the “interface” field.
My RB1200 is my CapsMAN with VLANs being sent through a trunk port (ether08) to my hAP ac. I use wlan2 (5GHz) of the hAP ac as the trunk port to 3 other hAP ac lites. This is when I started getting those pesky messages. Having read a reply from becs (+1), I disabled MNDP from all VLAN bridges (except BR-TRUNK) and VLAN interfaces.
Hello. I just solved this problem by removing the bridge (of course I lost the connection with the router). Then I created a new bridge. And after that, it was still necessary to Disable and Enable the problem port, which one I saw in the error messages. For 30 minutes there is no error. Prior to this, there were errors in the log every 7-10 seconds.
I have a CCR in a datacenter where the internet connection is provided by a pair of (juniper) routers in VRRP configuration and I very seldomly see the message on that port, but I think it happens when the active router changes.
It is only one such message and then it may not be seen for a month.
I just disregard those.
Of course when it happened every minute, I would research the matter more deeply…