When using Winbox (version 3.6) it shows my local router as being IPv4 only but it is IPv4 and IPv6:
This, to me, is just a curiosity as I know which of my devices are ipv4 only and which are ipv4 + ipv6.
Click the black down-arrow at the top-right corner of the display grid, choose “show columns” and add IPv6 Address.
There is no IPv6 Address option in the Neighbors tab:
This is WinBox v3.6
Interesting. I’m using Winbox 3.4 and it’s available…
I also noticed that the IPv6 neighbor address takes a moment to appear - I think it’s listening for RA messages or possibly any packet originated by the router. I didn’t feel like breaking out Wireshark and diving down into packet space…
One interesting thing I found was that if I added a routable address to the neighbor’s interface, that address is what shows up (not the link-local) but I disabled the public address. When I disabled discovery on router2, and re-enabled it (to force a “refresh”) - the public address showed up, even though it was disabled on R1. ? If I removed the address (having never enabled it) then the link-local shows up.
Methinks there be buggies lurking about.
I even found that a router (I’m using CHR v6.36 in my test) with the IPv6 package disabled will still show the IPv6 address of its v6-enabled neighbor.
Oh wait - I just noticed that you’re referring to the neighbor discovery tab in the Winbox launcher, not the IP>Neighbors list in the Mikrotik itself.
Interestingly - I don’t know if this is a Winbox thing or a GNS3 virtual switch thing or a MS-Loopback interface thing…
After I pinged ff02::1%18 (all IPv6 nodes on my GNS3 virtual interface) from my host, suddenly all of my ROS devices appeared in neighbor discovery tab - including IPv6 address.
They weren’t showing up with IPv4 either prior to this action on my part…
Here’s what it looked like afterwards. (CHR-2 has IPv6 disabled)
Does not help on windows 10. Still no ipv6 on winbox 3.40