Neighbor Discovery on Bridge Interfaces

I’m seeing an odd behaviour with neighbour discovery on bridge interfaces. When I open up WinBox and look at the neighbours, I see both IPv4 and IPv6 entries for interfaces that aren’t bridges, but only IPv4 entries for bridge interfaces. I can’t see any significant differences between the entries when I check from the RouterOS CLI. Any thoughts from the community before I open a ticket?

Neighbor Discovery

Do you have any other L2/L3 router/switch on your network?

Nope. This is all connected through a RouterOS bridge… and it’s only the bridge interface itself that doesn’t show its IPv6 addresses in WinBox. RouterOS devices that are connected through the bridge are fine.

Neighbor Discovery protocols allow us to find devices compatible with MNDP (MikroTik Neighbor Discovery Protocol), CDP (Cisco Discovery Protocol), or LLDP (Link Layer Discovery Protocol) in the Layer2 broadcast domain. It can be used to map out your network.

If you don’t have any other router/switch your fine.

This is what I have connect

SODOLA SL-SWTG3C12F switch

MNDP discovery runniing on ubuntu

I get how MNDP works. Everything is working except for the missing IPv6 entries. To illustrate, here's what I'm getting in my WinBox on a client connected to the spoke3 router's bridge:

I'm figuring I should be seeing IPv6 entries for the hub and for spoke3 (both of which are bridge interfaces) just like I do for spoke1 and spoke2 (which are not bridge interfaces) but this isn't the case.

I see what your saying. Click on the pancake icon (the 3 lines) column selection and check box ipv6 address

I’m not running ipv6 so there are link-local.

Also, could be a version difference since I’m on 7.22rc3

You’re looking at the router’s IP Neighbours panel after logging in. I’m looking at WinBox’s Neighbours before logging in. These have different options and entries.

Oh, sorry they look too much alike.

I don’t get any ipv6 addresses in the winbox client.

Maybe, someone can chime in and help out.

Related ? RouterOS bridge VLAN filtering breaks MNDP over IPv6 reception/response processing - #6 by BobbyMcgee

Yes, I can confirm this observation. When the PC running WinBox is connected to the router on one of its ethernet ports, or on a VLAN interface then the Neighbors tab on the start screen shows IPv6 addresses; but not when the connection is made to the bridge interface (for example the default bridge of defconf).

But in the later case the link local IPv6 address of the router on that bridge can still be used to login, it just not listed with the discovery feature.