I have RB 450G with both IPv4 and IPv6 setup, ROS version 3.30. Two interfaces are directly connected to computers, which are most of the time off, thus interface is inactive. After starting such computer interface becomes running, IPv4 works great, but computer does not get IPv6 Router Advertisement and therefore does not setup its IPv6 connectivity. Every interface has its own subnet.
When I reboot RB 450G, everything starts to work as expected (IPv6 works), until switching the computer off - then IPv6 breaks again. Tried with Windows XP and Ubuntu 9.10, didn’t try to listen to interface using Wireshark.
Partial solution:
Problem has been partially circumvented by setting up bridge, configuring IPv6 and IPv4 on bridge and attaching those interfaces to bridge - this works.
I have a same problem at RB433AH running RouterOS 4.5 . Simply router doesn’t send Router Advertisment ICMPv6 message. I have a 6to4 tunnel to HurricaneElectric Broker. When I reboot the router while PCs are running, everthing is ok. After the routers boot PCs get Advertisment message and set IPv6 address correctly. But when I reboot PCs, they never get Advertisment from router again.
I have spent lot of hours running Wireshark and logging IPv6 trafic. The Advertisment message from Mikrotik never arrived again, only after the routers reboot.
So, I did some experiments with EUI64 enabled and disabled, but without any success. Still no sign of the Router advertisement packet. More ideas? Thanks.
Try doing it through the physical interface. In other words, take that interface out of the bridge and attach the address to that interface.
It’s a shot in the dark.
So I have torn out eth1 from the bridge and disabled br0. Now it looks like Router Advertisement is being sent approx. every 250s. Now, it works. But I need eth1, eth2 and ath0 bridged.
UPDATE: I get it back to the previous state and now no more advertisement. Is this bug or a feature?
When you create the bridge, does it get an fe80:: type address automatically?
Additionally, have you looked into the various neighbor discovery options? You may find your answer there.
Yes. The br0 device get local link address automatically. It’s same as eth2 IPv6 address. I played with ND setting but without any effect. I created new specific rule for br0 and set shorter time for Advertisement, but no effect. In case when “bridge was out” shorter time caused shorter period of Advertisement packet as expected. With bridge enabled… simply nothing.