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
/interface vlan add comment=telecomm interface=BR-TRUNK name=vlan100 vlan-id=100 add comment="servers and voip" interface=BR-TRUNK name=vlan101 vlan-id=101 add comment=pc interface=BR-TRUNK name=vlan102 vlan-id=102
/interface bridge port add bridge=BR-TRUNK interface=ether08 add bridge=BR-VLAN100 interface=vlan100 add bridge=BR-VLAN101 interface=vlan101 add bridge=BR-VLAN102 interface=vlan102
could you please explain this in detail...I had the same problem on CAPsMAN... Left in bridge only ether1 (I had wlan1 in bridge, too) and it solved it. Maybe this could help someone.
My setup: Capsman running on an rb2011 connected to a cAP ACI had the same problem on CAPsMAN... Left in bridge only ether1 (I had wlan1 in bridge, too) and it solved it. Maybe this could help someone.
You can change MAC addresses where ever you want. Just keep them distinct. The important thing is to have different MAC addresses for VAPs ... if VAP has same MAC address as AP, it just won't work (although it might seem to be fine from configuration point of view).If have an AP with two WLANS is it okay to change them too, so they are clearly distinct from each other ????
VLANs share MAC address of a physical port. In a switch/bridge configuration, switched ports don't need MAC address at all, because MAC address is only needed as base of L3 operation. Hence when multiple ether ports are bridge in RB, all ports will seem to be using bridge's MAC address (whichever that might be). Combined with first sentence in this paragraph ... you have all LAN VLANs using MAC of the bridge. I assume WNA port is not member of the bridge, hence it uses its own MAC address.I noticed that my vlans all have the same mac address, but the vlan attached for the ISP does not. Assuming all vlans on a bridge get assigned same mac address?
ether10: bridge port received packet with own address as source address (4c:5e:0c:00:00:00), probably loop
All MACs are unique
Excuse me but WHAT?? Someone with issue suspect? tap the network, sniff the data, confirm/reject suspicion. You don't need MTCNA to come up with this. Its common sense.I suspect that...
Its common sense.
it's mean that probleam can be resolved by disabling neighbor discovery?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.
[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.It seems disabling neighbor discovery solves the false positive alerts (that were generated exactly every 1 min):