Created attachment 768722 [details] ping link-local address Description of problem: In the ping page, it can not ping a reachable ipv6 link-local address. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20130222.0.auto1707.el6.iso ovirt-node-3.0.0-1.999.20130701111251git99aadc6.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Clean install the rhev-hypervisor6-6.5. 2. Configure the network with ipv6 auto mode. 3. Ping a reachable ipv6 link-local address. Actual results: In step3, it can input the successful ping info. But check it in the cmd like #ping6 -I em1 fe80::1a03:73ff:fe39:9a6e can success. Expected results: In step3, it can input the successful ping info. Additional info:
We can only solve this bug by exposing a list of interfaces which can be used to ping a link-local address. As link local addresses are only valid on the link, ping6 needs to know what link (device) to use for pinging. And that information is currently not provided to ping6. Mike, shall we allow to ping link-local addresses which means that we'll need to add a list of network interfaces to the ping page. Or shall this case be not supported and the user should use the console to ping a link-local address?
I think being able to ping from a specific interface makes some sense. I would lean toward making this an RFE though.
We can also add zones to the ipv6 addr validator to allow: 0::1%eth9 or similar
we're not tackling ipv6 at host level yet in rhev