Ubuntu pinging from link-local address instead of global
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
1
I have a network like this, (client 2001:10:1:100:0/64) -> router -> (server 2001:172:16:200:0/64)
However, when I ping from client to the 172.16.200.0 network, (or anywhere) it always uses the link local address instead of the global.
ens192 Link encap:Ethernet HWaddr 00:0c:29:e8:87:5a
inet addr:10.1.100.11 Bcast:10.1.100.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fee8:875a/64 Scope:Link <------ uses this
inet6 addr: 2001:10:1:100::11/64 Scope:Global <----- want to use this
I can see this on my router debug, note the source address is the link local, not the global
FGT-B (vd1) # id=20085 trace_id=5 func=resolve_ip6_tuple_fast line=4005 msg="vd-vd1:0 received a packet(proto=58, fe80::20c:29ff:fee8:875a:1115->2001:172:16:200::44:128) from port2."
id=20085 trace_id=5 func=resolve_ip6_tuple line=4122 msg="allocate a new session-00000163"
id=20085 trace_id=5 func=vf_ip6_route_input line=1117 msg="find a route: gw-2001:172:16:200::44 via port3 err 0 flags 01000001"
id=20085 trace_id=5 func=ip6_forward line=547 msg="invalid source address, drop"
The error I get on client is this
root@user1-virtual-machine:~# ping6 2001:172:16:200::44
PING 2001:172:16:200::44(2001:172:16:200::44) 56 data bytes
From fe80::926c:acff:fefb:b53b icmp_seq=1 Destination unreachable: Beyond scope of source address
From fe80::926c:acff:fefb:b53b icmp_seq=2 Destination unreachable: Beyond scope of source address
Any ideas why this is happening?
**Routing table
2001:10:1:100::/64 dev ens192 proto kernel metric 256 pref medium
fe80::/64 dev ens160 proto kernel metric 256 pref medium
fe80::/64 dev ens192 proto kernel metric 256 pref medium
default via 2001:10:1:100::2 dev ens192 metric 1024 pref medium
linux ubuntu networking routing ipv6
asked May 18 at 2:02
Thomas
263
 |Â
show 1 more comment
up vote
2
down vote
favorite
1
I have a network like this, (client 2001:10:1:100:0/64) -> router -> (server 2001:172:16:200:0/64)
However, when I ping from client to the 172.16.200.0 network, (or anywhere) it always uses the link local address instead of the global.
ens192 Link encap:Ethernet HWaddr 00:0c:29:e8:87:5a
inet addr:10.1.100.11 Bcast:10.1.100.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fee8:875a/64 Scope:Link <------ uses this
inet6 addr: 2001:10:1:100::11/64 Scope:Global <----- want to use this
I can see this on my router debug, note the source address is the link local, not the global
FGT-B (vd1) # id=20085 trace_id=5 func=resolve_ip6_tuple_fast line=4005 msg="vd-vd1:0 received a packet(proto=58, fe80::20c:29ff:fee8:875a:1115->2001:172:16:200::44:128) from port2."
id=20085 trace_id=5 func=resolve_ip6_tuple line=4122 msg="allocate a new session-00000163"
id=20085 trace_id=5 func=vf_ip6_route_input line=1117 msg="find a route: gw-2001:172:16:200::44 via port3 err 0 flags 01000001"
id=20085 trace_id=5 func=ip6_forward line=547 msg="invalid source address, drop"
The error I get on client is this
root@user1-virtual-machine:~# ping6 2001:172:16:200::44
PING 2001:172:16:200::44(2001:172:16:200::44) 56 data bytes
From fe80::926c:acff:fefb:b53b icmp_seq=1 Destination unreachable: Beyond scope of source address
From fe80::926c:acff:fefb:b53b icmp_seq=2 Destination unreachable: Beyond scope of source address
Any ideas why this is happening?
**Routing table
2001:10:1:100::/64 dev ens192 proto kernel metric 256 pref medium
fe80::/64 dev ens160 proto kernel metric 256 pref medium
fe80::/64 dev ens192 proto kernel metric 256 pref medium
default via 2001:10:1:100::2 dev ens192 metric 1024 pref medium
linux ubuntu networking routing ipv6
asked May 18 at 2:02
Thomas
263
This looks like an issue with the router, not the endpoints.
– Michael Hampton
May 18 at 3:13
Probably because you're using teredo tunneling addresses for your IPv6? It's also not clear if you're trying to get your router to do 6to4 translation for you which is done on the 2002::/16 block and ipv4 mapped addresses on the ::ffff:0:0/96 block.
– jdwolf
May 18 at 4:30
Just a guess but try:ping6 ::ffff:0:172:16:200:0
– jdwolf
May 18 at 4:31
1
Please show us your routing table:ip -6 r.
– Johan Myréen
May 18 at 15:40
@johan, i attached my routing table
– Thomas
May 18 at 17:25
 |Â
show 1 more comment
up vote
2
down vote
favorite
1
up vote
2
down vote
favorite
1
1
I have a network like this, (client 2001:10:1:100:0/64) -> router -> (server 2001:172:16:200:0/64)
However, when I ping from client to the 172.16.200.0 network, (or anywhere) it always uses the link local address instead of the global.
ens192 Link encap:Ethernet HWaddr 00:0c:29:e8:87:5a
inet addr:10.1.100.11 Bcast:10.1.100.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fee8:875a/64 Scope:Link <------ uses this
inet6 addr: 2001:10:1:100::11/64 Scope:Global <----- want to use this
I can see this on my router debug, note the source address is the link local, not the global
FGT-B (vd1) # id=20085 trace_id=5 func=resolve_ip6_tuple_fast line=4005 msg="vd-vd1:0 received a packet(proto=58, fe80::20c:29ff:fee8:875a:1115->2001:172:16:200::44:128) from port2."
id=20085 trace_id=5 func=resolve_ip6_tuple line=4122 msg="allocate a new session-00000163"
id=20085 trace_id=5 func=vf_ip6_route_input line=1117 msg="find a route: gw-2001:172:16:200::44 via port3 err 0 flags 01000001"
id=20085 trace_id=5 func=ip6_forward line=547 msg="invalid source address, drop"
The error I get on client is this
root@user1-virtual-machine:~# ping6 2001:172:16:200::44
PING 2001:172:16:200::44(2001:172:16:200::44) 56 data bytes
From fe80::926c:acff:fefb:b53b icmp_seq=1 Destination unreachable: Beyond scope of source address
From fe80::926c:acff:fefb:b53b icmp_seq=2 Destination unreachable: Beyond scope of source address
Any ideas why this is happening?
**Routing table
2001:10:1:100::/64 dev ens192 proto kernel metric 256 pref medium
fe80::/64 dev ens160 proto kernel metric 256 pref medium
fe80::/64 dev ens192 proto kernel metric 256 pref medium
default via 2001:10:1:100::2 dev ens192 metric 1024 pref medium
linux ubuntu networking routing ipv6
asked May 18 at 2:02
Thomas
263
I have a network like this, (client 2001:10:1:100:0/64) -> router -> (server 2001:172:16:200:0/64)
However, when I ping from client to the 172.16.200.0 network, (or anywhere) it always uses the link local address instead of the global.
ens192 Link encap:Ethernet HWaddr 00:0c:29:e8:87:5a
inet addr:10.1.100.11 Bcast:10.1.100.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fee8:875a/64 Scope:Link <------ uses this
inet6 addr: 2001:10:1:100::11/64 Scope:Global <----- want to use this
I can see this on my router debug, note the source address is the link local, not the global
FGT-B (vd1) # id=20085 trace_id=5 func=resolve_ip6_tuple_fast line=4005 msg="vd-vd1:0 received a packet(proto=58, fe80::20c:29ff:fee8:875a:1115->2001:172:16:200::44:128) from port2."
id=20085 trace_id=5 func=resolve_ip6_tuple line=4122 msg="allocate a new session-00000163"
id=20085 trace_id=5 func=vf_ip6_route_input line=1117 msg="find a route: gw-2001:172:16:200::44 via port3 err 0 flags 01000001"
id=20085 trace_id=5 func=ip6_forward line=547 msg="invalid source address, drop"
The error I get on client is this
root@user1-virtual-machine:~# ping6 2001:172:16:200::44
PING 2001:172:16:200::44(2001:172:16:200::44) 56 data bytes
From fe80::926c:acff:fefb:b53b icmp_seq=1 Destination unreachable: Beyond scope of source address
From fe80::926c:acff:fefb:b53b icmp_seq=2 Destination unreachable: Beyond scope of source address
Any ideas why this is happening?
**Routing table
2001:10:1:100::/64 dev ens192 proto kernel metric 256 pref medium
fe80::/64 dev ens160 proto kernel metric 256 pref medium
fe80::/64 dev ens192 proto kernel metric 256 pref medium
default via 2001:10:1:100::2 dev ens192 metric 1024 pref medium
linux ubuntu networking routing ipv6
asked May 18 at 2:02
Thomas
263
edited May 18 at 17:25
asked May 18 at 2:02
Thomas
263
asked May 18 at 2:02
Thomas
263
asked May 18 at 2:02
Thomas
263
263
This looks like an issue with the router, not the endpoints.
– Michael Hampton
May 18 at 3:13
Probably because you're using teredo tunneling addresses for your IPv6? It's also not clear if you're trying to get your router to do 6to4 translation for you which is done on the 2002::/16 block and ipv4 mapped addresses on the ::ffff:0:0/96 block.
– jdwolf
May 18 at 4:30
Just a guess but try:ping6 ::ffff:0:172:16:200:0
– jdwolf
May 18 at 4:31
1
Please show us your routing table:ip -6 r.
– Johan Myréen
May 18 at 15:40
@johan, i attached my routing table
– Thomas
May 18 at 17:25
 |Â
show 1 more comment
This looks like an issue with the router, not the endpoints.
– Michael Hampton
May 18 at 3:13
Probably because you're using teredo tunneling addresses for your IPv6? It's also not clear if you're trying to get your router to do 6to4 translation for you which is done on the 2002::/16 block and ipv4 mapped addresses on the ::ffff:0:0/96 block.
– jdwolf
May 18 at 4:30
Just a guess but try:ping6 ::ffff:0:172:16:200:0
– jdwolf
May 18 at 4:31
1
Please show us your routing table:ip -6 r.
– Johan Myréen
May 18 at 15:40
@johan, i attached my routing table
– Thomas
May 18 at 17:25
This looks like an issue with the router, not the endpoints.
– Michael Hampton
May 18 at 3:13
This looks like an issue with the router, not the endpoints.
– Michael Hampton
May 18 at 3:13
Probably because you're using teredo tunneling addresses for your IPv6? It's also not clear if you're trying to get your router to do 6to4 translation for you which is done on the 2002::/16 block and ipv4 mapped addresses on the ::ffff:0:0/96 block.
– jdwolf
May 18 at 4:30
Probably because you're using teredo tunneling addresses for your IPv6? It's also not clear if you're trying to get your router to do 6to4 translation for you which is done on the 2002::/16 block and ipv4 mapped addresses on the ::ffff:0:0/96 block.
– jdwolf
May 18 at 4:30
Just a guess but try:
ping6 ::ffff:0:172:16:200:0– jdwolf
May 18 at 4:31
Just a guess but try:
ping6 ::ffff:0:172:16:200:0– jdwolf
May 18 at 4:31
1
1
Please show us your routing table:
ip -6 r.– Johan Myréen
May 18 at 15:40
Please show us your routing table:
ip -6 r.– Johan Myréen
May 18 at 15:40
@johan, i attached my routing table
– Thomas
May 18 at 17:25
@johan, i attached my routing table
– Thomas
May 18 at 17:25
 |Â
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444507%2fubuntu-pinging-from-link-local-address-instead-of-global%23new-answer', 'question_page');
);
Post as a guest
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
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
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
This looks like an issue with the router, not the endpoints.
– Michael Hampton
May 18 at 3:13
Probably because you're using teredo tunneling addresses for your IPv6? It's also not clear if you're trying to get your router to do 6to4 translation for you which is done on the 2002::/16 block and ipv4 mapped addresses on the ::ffff:0:0/96 block.
– jdwolf
May 18 at 4:30
Just a guess but try:
ping6 ::ffff:0:172:16:200:0– jdwolf
May 18 at 4:31
1
Please show us your routing table:
ip -6 r.– Johan Myréen
May 18 at 15:40
@johan, i attached my routing table
– Thomas
May 18 at 17:25