I have a problem with IPv6 ND (neighbour discovery) and interface configured in ARP mode reply-only.
Scenario:
RB433AH [ether2] ----- [eth] Windows client
RB433AH
tested ROS 5.7, 5.8
Windows client
tested Windows XP SP3, Windows 7
configuration on Windows XP is stateless IPv6 (only one supported mode for IPv6)
Problem description:
When I configure:
/interface ether2 set arp=reply-only
the ROS ND is not working - in the Windows XP I can see IPv6 IP address from range that is advertised from ROS, but I’m not able to ping ether2’s IPv6 IP address from the Windows XP client. I can’t see the Windows XP client in ROS IPv6/ND list. When I configure:
/interface ether2 set arp=enabled
everything is working correctly - the client is able to ping ether2’s IPv6 address, I’m able to see the Windows XP client in ROS IPv6/ND list.
Do you see any misconfiguration in my screnario, please? On the same interface I’m running also IPv4, the ARP mode reply-only is working correctly. If you need more information or I should open ticket for this issue, please let me know.
edit: it works as you expect, there is problem with addresses when ARP is not working for IPv6. It is known problem and we are working on it. It is not an easy fix unfortunately.
The first tests shows that the issue with interface ARP mode reply-only and IPv6 stateless autoconfiguration is solved in ROS 5.12, let’s wait for a final release