Ubuntu IPv6 ping self gives unknown host
up vote
3
down vote
favorite
I'm stuck trying to get IPv6 working on a new Ubuntu 16.04 (Xenial Xerus) install. My scenario is very basic - trying to ping the local IPv6 address.
$ ifconfig
enp0s25 Link encap:Ethernet HWaddr b8:ae:ed:77:91:fa
inet6 addr: fe80::ba94:3d5e:9929:4c6e/64 Scope:Link
and
$ ping6 -c 5 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
results in
unknown host
How do I troubleshoot?
ubuntu ipv6 localhost
New contributor
add a comment |
up vote
3
down vote
favorite
I'm stuck trying to get IPv6 working on a new Ubuntu 16.04 (Xenial Xerus) install. My scenario is very basic - trying to ping the local IPv6 address.
$ ifconfig
enp0s25 Link encap:Ethernet HWaddr b8:ae:ed:77:91:fa
inet6 addr: fe80::ba94:3d5e:9929:4c6e/64 Scope:Link
and
$ ping6 -c 5 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
results in
unknown host
How do I troubleshoot?
ubuntu ipv6 localhost
New contributor
Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
Nov 17 at 18:55
superuser.com/questions/1005335/…
– harrymc
Nov 17 at 19:26
FYI:ifconfig
is deprecated. You want to useip address
orip a
instead.
– Bakuriu
Nov 17 at 23:08
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm stuck trying to get IPv6 working on a new Ubuntu 16.04 (Xenial Xerus) install. My scenario is very basic - trying to ping the local IPv6 address.
$ ifconfig
enp0s25 Link encap:Ethernet HWaddr b8:ae:ed:77:91:fa
inet6 addr: fe80::ba94:3d5e:9929:4c6e/64 Scope:Link
and
$ ping6 -c 5 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
results in
unknown host
How do I troubleshoot?
ubuntu ipv6 localhost
New contributor
I'm stuck trying to get IPv6 working on a new Ubuntu 16.04 (Xenial Xerus) install. My scenario is very basic - trying to ping the local IPv6 address.
$ ifconfig
enp0s25 Link encap:Ethernet HWaddr b8:ae:ed:77:91:fa
inet6 addr: fe80::ba94:3d5e:9929:4c6e/64 Scope:Link
and
$ ping6 -c 5 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
results in
unknown host
How do I troubleshoot?
ubuntu ipv6 localhost
ubuntu ipv6 localhost
New contributor
New contributor
edited Nov 18 at 0:32
Peter Mortensen
8,301166184
8,301166184
New contributor
asked Nov 17 at 18:50
jws
1956
1956
New contributor
New contributor
Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
Nov 17 at 18:55
superuser.com/questions/1005335/…
– harrymc
Nov 17 at 19:26
FYI:ifconfig
is deprecated. You want to useip address
orip a
instead.
– Bakuriu
Nov 17 at 23:08
add a comment |
Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
Nov 17 at 18:55
superuser.com/questions/1005335/…
– harrymc
Nov 17 at 19:26
FYI:ifconfig
is deprecated. You want to useip address
orip a
instead.
– Bakuriu
Nov 17 at 23:08
Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
Nov 17 at 18:55
Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
Nov 17 at 18:55
superuser.com/questions/1005335/…
– harrymc
Nov 17 at 19:26
superuser.com/questions/1005335/…
– harrymc
Nov 17 at 19:26
FYI:
ifconfig
is deprecated. You want to use ip address
or ip a
instead.– Bakuriu
Nov 17 at 23:08
FYI:
ifconfig
is deprecated. You want to use ip address
or ip a
instead.– Bakuriu
Nov 17 at 23:08
add a comment |
2 Answers
2
active
oldest
votes
up vote
8
down vote
Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms
The local interface argument -I can be specified in the address instead by appending %
and the interface name:
$ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
...
These combinations don't work:
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
unknown host
or
$ ping6 fe80::ba94:3d5e:9929:4c6e
connect: Invalid argument
New contributor
1
Is that an answer or a follow-up? This site is not a forum. It is a think tank.
– Peter Mortensen
Nov 18 at 0:33
1
@PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
– eckes
Nov 18 at 0:42
@PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
– kasperd
Nov 18 at 9:31
add a comment |
up vote
8
down vote
You should not use the /64
on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms
The local interface argument -I can be specified in the address instead by appending %
and the interface name:
$ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
...
These combinations don't work:
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
unknown host
or
$ ping6 fe80::ba94:3d5e:9929:4c6e
connect: Invalid argument
New contributor
1
Is that an answer or a follow-up? This site is not a forum. It is a think tank.
– Peter Mortensen
Nov 18 at 0:33
1
@PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
– eckes
Nov 18 at 0:42
@PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
– kasperd
Nov 18 at 9:31
add a comment |
up vote
8
down vote
Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms
The local interface argument -I can be specified in the address instead by appending %
and the interface name:
$ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
...
These combinations don't work:
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
unknown host
or
$ ping6 fe80::ba94:3d5e:9929:4c6e
connect: Invalid argument
New contributor
1
Is that an answer or a follow-up? This site is not a forum. It is a think tank.
– Peter Mortensen
Nov 18 at 0:33
1
@PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
– eckes
Nov 18 at 0:42
@PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
– kasperd
Nov 18 at 9:31
add a comment |
up vote
8
down vote
up vote
8
down vote
Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms
The local interface argument -I can be specified in the address instead by appending %
and the interface name:
$ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
...
These combinations don't work:
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
unknown host
or
$ ping6 fe80::ba94:3d5e:9929:4c6e
connect: Invalid argument
New contributor
Works with /64 removed and -I specified. The /64 refers to the number of bits in the mask and shouldn't be used in ping.
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e
PING fe80::ba94:3d5e:9929:4c6e(fe80::ba94:3d5e:9929:4c6e) from fe80::ba94:3d5e:9929:4c6e enp0s25: 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.043 ms
The local interface argument -I can be specified in the address instead by appending %
and the interface name:
$ ping6 fe80::ba94:3d5e:9929:4c6e%enp0s25
PING fe80::ba94:3d5e:9929:4c6e%enp0s25(fe80::ba94:3d5e:9929:4c6e) 56 data bytes
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from fe80::ba94:3d5e:9929:4c6e: icmp_seq=2 ttl=64 time=0.059 ms
...
These combinations don't work:
$ ping6 -c 1 -I enp0s25 fe80::ba94:3d5e:9929:4c6e/64
unknown host
or
$ ping6 fe80::ba94:3d5e:9929:4c6e
connect: Invalid argument
New contributor
edited Nov 17 at 21:31
New contributor
answered Nov 17 at 19:24
jws
1956
1956
New contributor
New contributor
1
Is that an answer or a follow-up? This site is not a forum. It is a think tank.
– Peter Mortensen
Nov 18 at 0:33
1
@PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
– eckes
Nov 18 at 0:42
@PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
– kasperd
Nov 18 at 9:31
add a comment |
1
Is that an answer or a follow-up? This site is not a forum. It is a think tank.
– Peter Mortensen
Nov 18 at 0:33
1
@PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
– eckes
Nov 18 at 0:42
@PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
– kasperd
Nov 18 at 9:31
1
1
Is that an answer or a follow-up? This site is not a forum. It is a think tank.
– Peter Mortensen
Nov 18 at 0:33
Is that an answer or a follow-up? This site is not a forum. It is a think tank.
– Peter Mortensen
Nov 18 at 0:33
1
1
@PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
– eckes
Nov 18 at 0:42
@PeterMortensen it’s a valid answer, to Ping a link local network address you must specify the interface and to use a ip6 address with pink you must not specify a / suffix.
– eckes
Nov 18 at 0:42
@PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
– kasperd
Nov 18 at 9:31
@PeterMortensen This is a perfectly valid answer to the question. In fact it is even a better answer than the one posted later. This answer gives examples of valid syntax and points out that there are two different ways to specify the interface.
– kasperd
Nov 18 at 9:31
add a comment |
up vote
8
down vote
You should not use the /64
on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.
add a comment |
up vote
8
down vote
You should not use the /64
on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.
add a comment |
up vote
8
down vote
up vote
8
down vote
You should not use the /64
on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.
You should not use the /64
on the address in the ping. That would be the equivalent of using a mask length or mask on the ping command for IPv4. I suppose the ping command was trying to interpret that as a host name.
edited Nov 18 at 1:43
Twisty Impersonator
16.6k126090
16.6k126090
answered Nov 17 at 19:33
Ron Maupin
3,04011020
3,04011020
add a comment |
add a comment |
jws is a new contributor. Be nice, and check out our Code of Conduct.
jws is a new contributor. Be nice, and check out our Code of Conduct.
jws is a new contributor. Be nice, and check out our Code of Conduct.
jws is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1376287%2fubuntu-ipv6-ping-self-gives-unknown-host%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Bonk... I had tried that and got invalid argument, but, at that time I didn't specify -I also. Thanks!
– jws
Nov 17 at 18:55
superuser.com/questions/1005335/…
– harrymc
Nov 17 at 19:26
FYI:
ifconfig
is deprecated. You want to useip address
orip a
instead.– Bakuriu
Nov 17 at 23:08