Open ericwong3 opened 3 years ago
Yea, manual setting of --router-mac
is the way to go for the moment. I'm going to have to do a better job of either asking the operating system for it's desired router, or parsing Neighbor Notification packets to get the right router. I'm going to have to setup my lab to reproduce this, so it'll take a while.
Thank you for the great work for IPv6 @robertdavidgraham ! However, I am experiencing a similar issue that an incorrect router-mac is used and thus nothing returns from the scan.
In relation to #541, this time it indeed used some IPv6 neighbor as the router MAC. However, it did not pick the real router's MAC, but apparently it picked a "router" on the link-local network of the default interface.
There are multiple interfaces on this host and we are primarily using ens3. It is the default gateway's interface, and the scan should also be ran via that interface.
Here is the scan command output:
The
router-mac-ipv6
will cycle between scans and output fa-01-0d-e8-80-29 / fa-01-0b-d1-c5-82 / fa-01-03-99-f4-66, and the corresponding entries inip neigh
output is as follow:===
The real gateway and it's MAC should be as follow:
The real router MAC should therefore be 00:22:bd:f8:19:ff
===
Scanning will indeed work if I specify the router-mac: