[Bug 260474] ping -e does not forward packets to specified next-hop

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260474

--- Comment #4 from Masse Nicolas <nicolas.masse@stormshield.eu> ---
Same thing here.
Seems it comes from commit https://reviews.freebsd.org/rS358572.
My analysis is as follow:

When calling ip6_output, rip6_send does not pass the cached route (but why?),
which makes ip6_output using the new route KPI. The thing is that new KPI does
not take the ipv6 next-hop option into account. As a result, packets are
emitted on the wrong interface.

I was able to workaround this issue by passing the cached route to ip6_output
in rip6_send. This makes the old KPI being used, making the packets emitted on
the right interface.
But the fact is that it does not solve the root cause of the issue, so I have
no idea if this is an acceptable solution.

-- 
You are receiving this mail because:
You are the assignee for the bug.