Hi,
I’ve this problem since a few week, sometimes a get the message “Bridge port received packet with own address as source, probably loop” and sometimes all is fine. Now I’m search again around the internet and some forums and found many content about this, but no solution. In one thread a found a hint to search for duplicate mac adress, but I can’t imagine, that the router should be double mac addresses.
BUT… I found, that the “brigde” and the wlan interface (2G) the same mac address. When I change the mac address from the wlan interface also the mac address from the bridge also changed at the same time. HHmmm.. now, what can I do?
It’s necessary that have the bridge a mac address or can I delete this? I have not found any concrete reference so far.
Can anybody explain this behaviar why the bridge and the wlan interface has the same mac address?
So that means, this is correct? But how can I find out the trouble with the loop error (Bridge port received packet with own address as source, probably loop) or is this a regular behavior? Hhmm…
I’ve seen the same thing in a gns3 simulation. I didn’t have time for deeper investigation but I’m wondering if it’s not related to stp convergence time (although ports should be blocked at first).
I’ve had this error occur with a VLAN bridge (stp, rstp, both off) with only one port. So, both had the same MAC, naturally. Now, when another device is connected to this physical port - that is also not a Trunk port itself (thus sending non-tagged packets ) I get the same error. Because there is not a VLAN tag coming from the sender (to direct it to the virtual interface), I suspect that creates the error. Maybe a bug?
You can test making the error occur every-time when opening Winbox and selecting the Neighbors tab. So, when a broadcast is sent? As soon as you adjust the incoming packets to be tagged packets, all is well. View /ip neighbor print for a clue as to why this occurs.
Sample configuration that triggers the error (make sure sender is sending non-tagged):
# RouterOS 6.38.7
# Two bridges
/interface bridge
add name=bridge-LAN protocol-mode=none
add name=bridge-VLAN protocol-mode=none
# Trunk port
/interface ethernet
set [ find default-name=ether1 ] master-port="none"
set [ find default-name=ether3 ] master-port=ether2
set [ find default-name=ether4 ] master-port=ether2
set [ find default-name=ether5 ] master-port=ether2
# Create the VLAN on ether1
/interface vlan
add interface=ether1 name=vLAN10 vlan-id=10
# bridge ports
/interface bridge port
add bridge=bridge-LAN interface=ether2
add bridge=bridge-LAN interface=vLAN10
add bridge=bridge-VLAN interface=ether1
# bridge ip addresses
/ip address
add interface=bridge-LAN address=192.168.0.2/24
add interface=bridge-VLAN address=192.168.10.2/24
# set default route, etc.
Sorry for my late reply. I get this info from the mikrotik support, but it doesn’t realy helps me.
This message states that the device received a packet on the interface which has the exact same MAC address as the interface has.
In case of a Layer2 traffic loop, your device will send a packet with a MAC address 64:D1:54:35:98:84, it will bounce around your faulty network and receive the same packet back. This should not happen and can cause problems. If your network uses “dumb” switches, then eventually you might hog up your Layer2 connection with 1 packet multiplied many times.
@Alain
No, i didn’t change the default stp parameters.
Today I got a new answer from mikrotik. They suggested, to find out this cause, to monitor the traffic with the packet sniffer. I’ll do this next week because I’m tomorrow on a longer trip. Should I find any solution or new things, I’m post it here again.