Hi Alain,
On Thu, Oct 31, 2024 at 03:27:42PM +0000, Alain D D Williams via BitFolk Users wrote:
Why when I ping fe80::1 do I get 'enX0' in:
64 bytes from fe80::1%enX0: icmp_seq=1 ttl=64 time=0.114 ms
fe80::/10 is the link-local address space. Every network interface that
you have on your system that has IPv6 enabled should have at least one
address on it that's inside fe80::/10.
This leads to the issue that addresses in the fe80::/10 space are not
unique since most hosts have at least one network interface and a
loopback interface, each of which could have the exact same fe80::/10
address configured on it or reachable through it.
The %foo syntax is how one specifies which interface to use. In the
olden days one HAD TO specify the interface with %foo; the command would
fail if you didn't. These days Linux lets you omit the %foo part. I
think it might just try your first non-loopback network interface if
you don't specify it.
The response in the ping output does let you know which interface the
response came from.
Why when I ping fe80:: do I get 'enX0' in:
64 bytes from fe80::fcff:ffff:feff:ffff%enX0: icmp_seq=2 ttl=64 time=0.407 ms
I am not sure of the exact answer for this since I don't think we have
the address fe80:: configured anywhere. You are getting a response
from fe80::fcff:ffff:feff:ffff which is the automatic link-local address
on BitFolk's side of your virtual Ethernet. I don't know why it responds
to you asking fro fe80::. It does that for me too on newer versions of
Debian in a VM but not on older versions. All I know is that fe80:: is
some sort of multicast address.
But the answer will be basically the same with some other minor wrinkle
as to why that is happening.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
"It is I, Simon Quinlank. The chief conductor on the bus that is called
hobby." — Simon Quinlank