[opensuse] How do I interpret this router advert?
Hi,
I see entries like this in "iptraf":
│ ICMPv6 router adv (72 bytes) from fe80::fa8e:85ff:fe64:78f2 to ff02::1
on eth0 │
Who is "ff02::1"? This machine or the router?
linux-0o2k:~ # ping6 ff02::1
connect: Invalid argument
linux-0o2k:~ # ping6 "ff02::1"
connect: Invalid argument
linux-0o2k:~ #
linux-0o2k:~ # ifconfig
eth0: flags=4163
Carlos E. R. wrote:
Hi,
I see entries like this in "iptraf":
│ ICMPv6 router adv (72 bytes) from fe80::fa8e:85ff:fe64:78f2 to ff02::1 on eth0 │
Who is "ff02::1"? This machine or the router?
It's a multicast address. https://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-add... https://en.wikipedia.org/wiki/Multicast_address -- Per Jessen, Zürich (7.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/15/19 10:23 PM, Per Jessen wrote:
Carlos E. R. wrote:
Hi,
I see entries like this in "iptraf":
│ ICMPv6 router adv (72 bytes) from fe80::fa8e:85ff:fe64:78f2 to ff02::1 on eth0 │
Who is "ff02::1"? This machine or the router?
It's a multicast address.
https://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-add... https://en.wikipedia.org/wiki/Multicast_address
Ah, ok. I'm curious because my router doesn't hand out IPv6 addresses, yet that is coming from the router. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/15/2019 05:36 PM, Carlos E. R. wrote:
I'm curious because my router doesn't hand out IPv6 addresses, yet that is coming from the router.
Fire up Wireshark and see what it says. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/15/2019 07:39 PM, James Knott wrote:
On 04/15/2019 05:36 PM, Carlos E. R. wrote:
I'm curious because my router doesn't hand out IPv6 addresses, yet that is coming from the router. Fire up Wireshark and see what it says.
Just don't try and middle-mouse select anything -- you can't anymore with the new Gtk3 interface. You can't even select a Src: or Dst: IP to run whois on it. (or at least I can't find a way to do it...) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
Who is "ff02::1"? This machine or the router?
It's a multicast address.
https://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-add... https://en.wikipedia.org/wiki/Multicast_address
Ah, ok.
I'm curious because my router doesn't hand out IPv6 addresses, yet that is coming from the router.
The router obviously understands IPv6, but maybe it doesn't have any prefix. As James already suggested, run wireshark or tcpdump to see what else it's up to. tcpdump -n -i dev ip6 I would expect to see neighbour solicitations/advertisements, maybe mDNS broadcasts. -- Per Jessen, Zürich (4.3°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/16/19 7:29 AM, Per Jessen wrote:
Carlos E. R. wrote:
Who is "ff02::1"? This machine or the router?
It's a multicast address.
https://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-add... https://en.wikipedia.org/wiki/Multicast_address
Ah, ok.
I'm curious because my router doesn't hand out IPv6 addresses, yet that is coming from the router.
The router obviously understands IPv6, but maybe it doesn't have any prefix. As James already suggested, run wireshark or tcpdump to see what else it's up to.
tcpdump -n -i dev ip6
linux-0o2k:~ # tcpdump -n -i dev ip6 tcpdump: dev: No such device exists (SIOCGIFHWADDR: No such device) linux-0o2k:~ # I suppose it is -i eth0 but then I get everything. Ah! "tcpdump -n -i eth0 ip6" Nothing much: linux-0o2k:~ # tcpdump -n -i eth0 ip6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 12:46:05.141051 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:09.157109 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:17.180165 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:23.945444 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:31.368144 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:34.804115 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:43.232276 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:48.711316 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 ... 12:48:45.654171 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 ^C 27 packets captured 27 packets received by filter 0 packets dropped by kernel linux-0o2k:~ #
I would expect to see neighbour solicitations/advertisements, maybe mDNS broadcasts.
No, just those broadcasts. There doesn't seem to be replies :-? Wireshark is not installed, and the whole system is 15 GB. I'm testing Leap 15.1 on a 15GB partition that includes home. tcpdump is better in this case, although I'm not familiar with it. The router is IPv6 capable, but the ISP is apparently not providing IPv6 addresses or connectivity. Thus seeing those v6 broadcasts aroused my curiosity. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/16/2019 06:53 AM, Carlos E. R. wrote:
linux-0o2k:~ # tcpdump -n -i dev ip6 tcpdump: dev: No such device exists (SIOCGIFHWADDR: No such device)
I think you're supposed to replace "dev" with whatever interface is used. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 4/16/19 7:29 AM, Per Jessen wrote:
Carlos E. R. wrote:
I would expect to see neighbour solicitations/advertisements, maybe mDNS broadcasts.
No, just those broadcasts. There doesn't seem to be replies :-?
That's fine - the advertisement is really the "reply". (to a solicitation).
Wireshark is not installed, and the whole system is 15 GB. I'm testing Leap 15.1 on a 15GB partition that includes home. tcpdump is better in this case, although I'm not familiar with it.
I only use wireshark when I can't decipher the packets directly. Most systems I work on don't have GUIs nor monitors. tcpdump is my friend. -- Per Jessen, Zürich (14.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/16/2019 06:53 AM, Carlos E. R. wrote:
I would expect to see neighbour solicitations/advertisements, maybe mDNS broadcasts. No, just those broadcasts. There doesn't seem to be replies :-?
There's no such thing as broadcasts with IPv6. The closest to it is all hosts multicast. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Dienstag, 16. April 2019, 12:53:12 CEST schrieb Carlos E. R.:
On 4/16/19 7:29 AM, Per Jessen wrote:
Carlos E. R. wrote:
Who is "ff02::1"? This machine or the router?
It's a multicast address.
https://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast -addresses.xhtml https://en.wikipedia.org/wiki/Multicast_address
Ah, ok.
I'm curious because my router doesn't hand out IPv6 addresses, yet that is coming from the router.
The router obviously understands IPv6, but maybe it doesn't have any prefix. As James already suggested, run wireshark or tcpdump to see what else it's up to.
tcpdump -n -i dev ip6
linux-0o2k:~ # tcpdump -n -i dev ip6 tcpdump: dev: No such device exists (SIOCGIFHWADDR: No such device) linux-0o2k:~ #
I suppose it is -i eth0 but then I get everything.
Ah! "tcpdump -n -i eth0 ip6"
Nothing much: linux-0o2k:~ # tcpdump -n -i eth0 ip6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 12:46:05.141051 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:09.157109 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:17.180165 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:23.945444 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:31.368144 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:34.804115 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:43.232276 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 12:46:48.711316 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 ... 12:48:45.654171 IP6 fe80::fa8e:85ff:fe64:78f2 > ff02::1: ICMP6, router advertisement, length 32 ^C 27 packets captured 27 packets received by filter 0 packets dropped by kernel linux-0o2k:~ #
I would expect to see neighbour solicitations/advertisements, maybe mDNS broadcasts.
No, just those broadcasts. There doesn't seem to be replies :-?
Wireshark is not installed, and the whole system is 15 GB. I'm testing Leap 15.1 on a 15GB partition that includes home. tcpdump is better in this case, although I'm not familiar with it.
The router is IPv6 capable, but the ISP is apparently not providing IPv6 addresses or connectivity. Thus seeing those v6 broadcasts aroused my curiosity.
just run radvdump and you'll see that (most likely) your router +is+ in fact handing out IPv6 adresses. Cheers MH -- Mathias Homann Senior Systems Engineer, IT Consultant. IT Trainer Mathias.Homann@openSUSE.org http://www.tuxonline.tech gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
Mathias Homann wrote:
just run radvdump and you'll see that (most likely) your router +is+ in fact handing out IPv6 adresses.
surely 'ip addr' would show that too ? -- Per Jessen, Zürich (11.3°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/17/19 10:26 AM, Per Jessen wrote:
Mathias Homann wrote:
just run radvdump and you'll see that (most likely) your router +is+ in fact handing out IPv6 adresses.
surely 'ip addr' would show that too ?
Leap 15.1 on automatics:
linux-0o2k:~ # ip addr
1: lo:
Am Mittwoch, 17. April 2019, 10:26:53 CEST schrieb Per Jessen:
Mathias Homann wrote:
just run radvdump and you'll see that (most likely) your router +is+ in fact handing out IPv6 adresses.
surely 'ip addr' would show that too ?
only if your local machine actually *accepts* them and configures the interface accordingly, which, in case of IPv6 forwarding being enabled (docker / libvirt), it doesn't. Cheers MH -- gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
Mathias Homann wrote:
Am Mittwoch, 17. April 2019, 10:26:53 CEST schrieb Per Jessen:
Mathias Homann wrote:
just run radvdump and you'll see that (most likely) your router +is+ in fact handing out IPv6 adresses.
surely 'ip addr' would show that too ?
only if your local machine actually *accepts* them and configures the interface accordingly, which, in case of IPv6 forwarding being enabled (docker / libvirt), it doesn't.
Okay - bit of a corner case I would say. Installing radvd to run radvdump is probably also a bit much. -- Per Jessen, Zürich (15.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Mittwoch, 17. April 2019, 13:40:52 CEST schrieb Per Jessen:
Mathias Homann wrote:
Am Mittwoch, 17. April 2019, 10:26:53 CEST schrieb Per Jessen:
Mathias Homann wrote:
just run radvdump and you'll see that (most likely) your router +is+ in fact handing out IPv6 adresses.
surely 'ip addr' would show that too ?
only if your local machine actually *accepts* them and configures the interface accordingly, which, in case of IPv6 forwarding being enabled (docker / libvirt), it doesn't.
Okay - bit of a corner case I would say. Installing radvd to run radvdump is probably also a bit much.
depends. as long as you don't enable radvd without knowing what it does, radvdump is quite useful to decode RA packets. Cheers MH -- gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On 4/17/19 7:49 AM, Mathias Homann wrote:
Am Dienstag, 16. April 2019, 12:53:12 CEST schrieb Carlos E. R.:
On 4/16/19 7:29 AM, Per Jessen wrote:
Carlos E. R. wrote:
...
The router is IPv6 capable, but the ISP is apparently not providing IPv6 addresses or connectivity. Thus seeing those v6 broadcasts aroused my curiosity.
just run radvdump and you'll see that (most likely) your router +is+ in fact handing out IPv6 adresses.
After installing it: linux-0o2k:~ # radvdump # # radvd configuration generated by radvdump 2.17 # based on Router Advertisement from fe80::fa8e:85ff:fe64:78f2 # received by interface eth0 # interface eth0 { AdvSendAdvert on; # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvManagedFlag off; AdvOtherConfigFlag off; AdvReachableTime 0; AdvRetransTimer 0; AdvCurHopLimit 64; AdvDefaultLifetime 0; AdvHomeAgentFlag off; AdvDefaultPreference low; AdvLinkMTU 1492; AdvSourceLLAddress on; }; # End of interface definition # # radvd configuration generated by radvdump 2.17 # based on Router Advertisement from fe80::fa8e:85ff:fe64:78f2 # received by interface eth0 # interface eth0 { AdvSendAdvert on; # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvManagedFlag off; AdvOtherConfigFlag off; AdvReachableTime 0; AdvRetransTimer 0; AdvCurHopLimit 64; AdvDefaultLifetime 0; AdvHomeAgentFlag off; AdvDefaultPreference low; AdvLinkMTU 1492; AdvSourceLLAddress on; }; # End of interface definition ... # # radvd configuration generated by radvdump 2.17 # based on Router Advertisement from fe80::fa8e:85ff:fe64:78f2 # received by interface eth0 # interface eth0 { AdvSendAdvert on; # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvManagedFlag off; AdvOtherConfigFlag off; AdvReachableTime 0; AdvRetransTimer 0; AdvCurHopLimit 64; AdvDefaultLifetime 0; AdvHomeAgentFlag off; AdvDefaultPreference low; AdvLinkMTU 1492; AdvSourceLLAddress on; }; # End of interface definition ^C linux-0o2k:~ # What does it mean? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
After installing it:
linux-0o2k:~ # radvdump # # radvd configuration generated by radvdump 2.17 # based on Router Advertisement from fe80::fa8e:85ff:fe64:78f2 # received by interface eth0 #
interface eth0 { AdvSendAdvert on; # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvManagedFlag off; AdvOtherConfigFlag off; AdvReachableTime 0; AdvRetransTimer 0; AdvCurHopLimit 64; AdvDefaultLifetime 0; AdvHomeAgentFlag off; AdvDefaultPreference low; AdvLinkMTU 1492; AdvSourceLLAddress on; }; # End of interface definition [snip]
What does it mean?
I think they are proposed configurations for radvd. Unless you have radvd installed and running, maybe radvdump is not of much use. -- Per Jessen, Zürich (15.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 17/04/2019 13.45, Per Jessen wrote:
Carlos E. R. wrote:
After installing it:
linux-0o2k:~ # radvdump # # radvd configuration generated by radvdump 2.17 # based on Router Advertisement from fe80::fa8e:85ff:fe64:78f2 # received by interface eth0 #
interface eth0 { AdvSendAdvert on; # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvManagedFlag off; AdvOtherConfigFlag off; AdvReachableTime 0; AdvRetransTimer 0; AdvCurHopLimit 64; AdvDefaultLifetime 0; AdvHomeAgentFlag off; AdvDefaultPreference low; AdvLinkMTU 1492; AdvSourceLLAddress on; }; # End of interface definition [snip]
What does it mean?
I think they are proposed configurations for radvd. Unless you have radvd installed and running, maybe radvdump is not of much use.
The package I installed this morning, because radvdump is there. But I have not configured it, of course, no idea how to. And now I have uninstalled it. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 17/04/2019 13.45, Per Jessen wrote:
Carlos E. R. wrote:
After installing it:
linux-0o2k:~ # radvdump # # radvd configuration generated by radvdump 2.17 # based on Router Advertisement from fe80::fa8e:85ff:fe64:78f2 # received by interface eth0 #
interface eth0 { AdvSendAdvert on; # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvManagedFlag off; AdvOtherConfigFlag off; AdvReachableTime 0; AdvRetransTimer 0; AdvCurHopLimit 64; AdvDefaultLifetime 0; AdvHomeAgentFlag off; AdvDefaultPreference low; AdvLinkMTU 1492; AdvSourceLLAddress on; }; # End of interface definition [snip]
What does it mean?
I think they are proposed configurations for radvd. Unless you have radvd installed and running, maybe radvdump is not of much use.
The package I installed this morning, because radvdump is there. But I have not configured it, of course, no idea how to. And now I have uninstalled it.
I have radvd on our router, for years, but I think the idea is to run radvdump on the client. I would just run tcpdump. -- Per Jessen, Zürich (16.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Mittwoch, 17. April 2019, 11:24:30 CEST schrieb Carlos E. R.:
What does it mean?
it means that your router does send out RA packets but there's no network configuration included. It's up to you to decide if that is correct or not. This is what that looks like when your router actually hands out addresses: # # radvd configuration generated by radvdump 2.17 # based on Router Advertisement from fe80::2a92:4aff:fe34:530f # received by interface wlan0 # interface wlan0 { AdvSendAdvert on; # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvManagedFlag on; AdvOtherConfigFlag on; AdvReachableTime 0; AdvRetransTimer 0; AdvCurHopLimit 64; AdvDefaultLifetime 180; AdvHomeAgentFlag off; AdvDefaultPreference medium; AdvLinkMTU 1480; AdvSourceLLAddress on; prefix fdff:ffc0:8aee:a415::/64 { AdvValidLifetime 86400; AdvPreferredLifetime 14400; AdvOnLink on; AdvAutonomous on; AdvRouterAddr on; }; # End of prefix definition }; # End of interface definition -- gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On 17/04/2019 15.28, Mathias Homann wrote:
Am Mittwoch, 17. April 2019, 11:24:30 CEST schrieb Carlos E. R.:
What does it mean?
it means that your router does send out RA packets but there's no network configuration included.
It's up to you to decide if that is correct or not.
This is what that looks like when your router actually hands out addresses:
# # radvd configuration generated by radvdump 2.17 # based on Router Advertisement from fe80::2a92:4aff:fe34:530f # received by interface wlan0 #
interface wlan0 { AdvSendAdvert on; # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump AdvManagedFlag on; AdvOtherConfigFlag on; AdvReachableTime 0; AdvRetransTimer 0; AdvCurHopLimit 64; AdvDefaultLifetime 180; AdvHomeAgentFlag off; AdvDefaultPreference medium; AdvLinkMTU 1480; AdvSourceLLAddress on;
prefix fdff:ffc0:8aee:a415::/64 { AdvValidLifetime 86400; AdvPreferredLifetime 14400; AdvOnLink on; AdvAutonomous on; AdvRouterAddr on; }; # End of prefix definition
}; # End of interface definition
Then my router is not handling out addresses. Confirmed. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/15/2019 03:12 PM, Carlos E. R. wrote:
Hi,
I see entries like this in "iptraf":
│ ICMPv6 router adv (72 bytes) from fe80::fa8e:85ff:fe64:78f2 to ff02::1 on eth0 │
Who is "ff02::1"? This machine or the router?
That's a multicast to all IPv6 capable devices. The "ff02:" indicates it has a link local scope, that it it will not be passed by routers. The ":1" indicates all hosts. Here's some info: http://www.ciscopress.com/articles/article.asp?p=2803866&seqNum=5 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-04-15 21:12, Carlos E. R. wrote:
linux-0o2k:~ # ping6 ff02::1 connect: Invalid argument
Just a small comment. You seem too have an old iputils installed. It was a bug in 2017. A workaround is to specify the interface in the command when trying to ping. Most tools recognize <ipv6>%<dev> or you could also use -i in this case. Like so: ping6 ff02::1%eth0 And for what it's worth. Now days ping6 and ping are the same. $ ls -l `which ping6` lrwxrwxrwx 1 root root 4 2 aug 2018 /usr/bin/ping6 -> ping Cheers, -- /bengan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Bengt Gördén wrote:
On 2019-04-15 21:12, Carlos E. R. wrote:
linux-0o2k:~ # ping6 ff02::1 connect: Invalid argument
Just a small comment. You seem too have an old iputils installed. It was a bug in 2017.
I also see the above, on Leap15. iputils does seem to be a bit old. -- Per Jessen, Zürich (11.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/16/19 11:06 AM, Bengt Gördén wrote:
On 2019-04-15 21:12, Carlos E. R. wrote:
linux-0o2k:~ # ping6 ff02::1 connect: Invalid argument
Just a small comment. You seem too have an old iputils installed.
It is Leap 15.1 Beta... the most recent possible.
It was a bug in 2017. A workaround is to specify the interface in the command when trying to ping. Most tools recognize <ipv6>%<dev> or you could also use -i in this case.
Like so: ping6 ff02::1%eth0
Ah! I always forget that syntax, and the man page has no examples, I was at a loss to find out the correct combination. Thanks. The result is curious: linux-0o2k:~ # ping6 -c 1 ff02::1%eth0 PING ff02::1%eth0(ff02::1%eth0) 56 data bytes 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=1 ttl=64 time=0.067 ms --- ff02::1%eth0 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.067/0.067/0.067/0.000 ms linux-0o2k:~ # but: linux-0o2k:~ # ping6 -c 4 ff02::1%eth0 PING ff02::1%eth0(ff02::1%eth0) 56 data bytes 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=1 ttl=64 time=0.062 ms 64 bytes from fe80::21e:bff:fe08:4ccb%eth0: icmp_seq=1 ttl=1 time=0.375 ms (DUP!) 64 bytes from fe80::4ecc:6aff:fe61:50a1%eth0: icmp_seq=1 ttl=64 time=0.417 ms (DUP!) 64 bytes from fe80::4609:b8ff:fe42:c944%eth0: icmp_seq=1 ttl=64 time=0.425 ms (DUP!) 64 bytes from fe80::fa8e:85ff:fe64:78f2%eth0: icmp_seq=1 ttl=64 time=1.68 ms (DUP!) 64 bytes from fe80::3a80:dfff:fe5c:75b5%eth0: icmp_seq=1 ttl=64 time=77.7 ms (DUP!) 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=2 ttl=64 time=0.066 ms 64 bytes from fe80::21e:bff:fe08:4ccb%eth0: icmp_seq=2 ttl=1 time=0.363 ms (DUP!) 64 bytes from fe80::4ecc:6aff:fe61:50a1%eth0: icmp_seq=2 ttl=64 time=0.395 ms (DUP!) 64 bytes from fe80::4609:b8ff:fe42:c944%eth0: icmp_seq=2 ttl=64 time=0.404 ms (DUP!) 64 bytes from fe80::fa8e:85ff:fe64:78f2%eth0: icmp_seq=2 ttl=64 time=0.649 ms (DUP!) 64 bytes from fe80::3a80:dfff:fe5c:75b5%eth0: icmp_seq=2 ttl=64 time=304 ms (DUP!) 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=3 ttl=64 time=0.059 ms 64 bytes from fe80::21e:bff:fe08:4ccb%eth0: icmp_seq=3 ttl=1 time=0.373 ms (DUP!) 64 bytes from fe80::4ecc:6aff:fe61:50a1%eth0: icmp_seq=3 ttl=64 time=0.392 ms (DUP!) 64 bytes from fe80::4609:b8ff:fe42:c944%eth0: icmp_seq=3 ttl=64 time=0.400 ms (DUP!) 64 bytes from fe80::fa8e:85ff:fe64:78f2%eth0: icmp_seq=3 ttl=64 time=0.660 ms (DUP!) 64 bytes from fe80::3a80:dfff:fe5c:75b5%eth0: icmp_seq=3 ttl=64 time=187 ms (DUP!) 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=4 ttl=64 time=0.052 ms --- ff02::1%eth0 ping statistics --- 4 packets transmitted, 4 received, +15 duplicates, 0% packet loss, time 3002ms rtt min/avg/max/mdev = 0.052/30.355/304.330/78.294 ms linux-0o2k:~ # With 1 ping, there is no time for the reply from the rest of the network, it exits at the first reply. The command doesn't know that it is a multicast.qq
And for what it's worth. Now days ping6 and ping are the same. $ ls -l `which ping6` lrwxrwxrwx 1 root root 4 2 aug 2018 /usr/bin/ping6 -> ping
That I noticed yesterday. Good thing, having two versions was absurd. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/16/2019 05:06 AM, Bengt Gördén wrote:
And for what it's worth. Now days ping6 and ping are the same.
Not quite. Ping6 forces IPv6, whereas ping will use IPv4 if an IPv6 address is not available. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/16/19 12:59 PM, James Knott wrote:
On 04/16/2019 05:06 AM, Bengt Gördén wrote:
And for what it's worth. Now days ping6 and ping are the same.
Not quite. Ping6 forces IPv6, whereas ping will use IPv4 if an IPv6 address is not available.
-6 Use IPv6 only. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/16/2019 07:34 AM, Carlos E. R. wrote:
Not quite. Ping6 forces IPv6, whereas ping will use IPv4 if an IPv6 address is not available.
-6 Use IPv6 only.
As with ping6. Here's an example of the difference. $ ping6 172.16.0.1 ping: 172.16.0.1: Address family for hostname not supported ping -6 172.16.0.1 ping: 172.16.0.1: Address family for hostname not supported $ ping 172.16.0.1 PING 172.16.0.1 (172.16.0.1) 56(84) bytes of data. 64 bytes from 172.16.0.1: icmp_seq=1 ttl=64 time=0.272 ms 64 bytes from 172.16.0.1: icmp_seq=2 ttl=64 time=0.330 ms -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/17/19 2:39 AM, James Knott wrote:
On 04/16/2019 07:34 AM, Carlos E. R. wrote:
Not quite. Ping6 forces IPv6, whereas ping will use IPv4 if an IPv6 address is not available.
-6 Use IPv6 only.
As with ping6. Here's an example of the difference.
$ ping6 172.16.0.1 ping: 172.16.0.1: Address family for hostname not supported
ping -6 172.16.0.1 ping: 172.16.0.1: Address family for hostname not supported
$ ping 172.16.0.1 PING 172.16.0.1 (172.16.0.1) 56(84) bytes of data. 64 bytes from 172.16.0.1: icmp_seq=1 ttl=64 time=0.272 ms 64 bytes from 172.16.0.1: icmp_seq=2 ttl=64 time=0.330 ms
All is good then, no? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/17/19 4:43 AM, James Knott wrote:
On 04/16/2019 09:31 PM, Carlos E. R. wrote:
All is good then, no?
Funny thing, there is no ping4. You have to use ping -4.
I don't see ping4 in Leap 15.0, either. Now that I look, ping6 is also a symlink there. I prefer this way, more consistent. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Bengt Gördén -
Carlos E. R. -
David C. Rankin -
James Knott -
Mathias Homann -
Per Jessen