IPv6 forwarding doesn't work
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have three Virtual Machines: A, B, C.
Machine A and Machine C connected to each other through the B.
Their config:
A's IP: 2000::ffff:50a:b0b/120
C's IP: 2000::ffff:50a:d0d/120
Machine B has two interfaces - eth0
and eth1
IP of eth0
- 2000::ffff:50a:b0c/120
IP of eth1
- 2000::ffff:50a:d0e/120
I've set sysctl -w net.ipv6.conf.all.forwarding=1
at Machine B
Also, at machines A and C I've set default gateways:
At A
ip -6 ro add default via 2000::ffff:50a:b0c
At C
ip -6 ro add default via 2000::ffff:50a:d0e
I want to ping machine C from A and vice versa.
The strange thing, that most part of ICMP packets are lost with message
Address unreachable
routing ipv6 ping forwarding
 |Â
show 1 more comment
up vote
0
down vote
favorite
I have three Virtual Machines: A, B, C.
Machine A and Machine C connected to each other through the B.
Their config:
A's IP: 2000::ffff:50a:b0b/120
C's IP: 2000::ffff:50a:d0d/120
Machine B has two interfaces - eth0
and eth1
IP of eth0
- 2000::ffff:50a:b0c/120
IP of eth1
- 2000::ffff:50a:d0e/120
I've set sysctl -w net.ipv6.conf.all.forwarding=1
at Machine B
Also, at machines A and C I've set default gateways:
At A
ip -6 ro add default via 2000::ffff:50a:b0c
At C
ip -6 ro add default via 2000::ffff:50a:d0e
I want to ping machine C from A and vice versa.
The strange thing, that most part of ICMP packets are lost with message
Address unreachable
routing ipv6 ping forwarding
I instead use a bridge interface if the same subnet is on two different interfaces of a host
â thrig
May 9 at 14:41
Which virtualization system are you using, and what type of interface (host, NAT, bridge, etc.) do the VMs have to the host?
â ErikF
May 9 at 16:16
If the addresses in your examples are the actual addresses you are using, I would strongly suggest using Unique Local Addresses instead, and with/64
subnets instead of/120
.
â Johan Myréen
May 9 at 20:10
/120 means they are in different subnets, so it's routed. Reproducing the very same configuration with 3 network namespaces (linux) works fine here.
â A.B
May 11 at 20:29
@A.B i don't know why, but the problem was in neighbor table. I manually set mapping between ip and mac addresses and it works fine
â Evgeniy
May 16 at 10:10
 |Â
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have three Virtual Machines: A, B, C.
Machine A and Machine C connected to each other through the B.
Their config:
A's IP: 2000::ffff:50a:b0b/120
C's IP: 2000::ffff:50a:d0d/120
Machine B has two interfaces - eth0
and eth1
IP of eth0
- 2000::ffff:50a:b0c/120
IP of eth1
- 2000::ffff:50a:d0e/120
I've set sysctl -w net.ipv6.conf.all.forwarding=1
at Machine B
Also, at machines A and C I've set default gateways:
At A
ip -6 ro add default via 2000::ffff:50a:b0c
At C
ip -6 ro add default via 2000::ffff:50a:d0e
I want to ping machine C from A and vice versa.
The strange thing, that most part of ICMP packets are lost with message
Address unreachable
routing ipv6 ping forwarding
I have three Virtual Machines: A, B, C.
Machine A and Machine C connected to each other through the B.
Their config:
A's IP: 2000::ffff:50a:b0b/120
C's IP: 2000::ffff:50a:d0d/120
Machine B has two interfaces - eth0
and eth1
IP of eth0
- 2000::ffff:50a:b0c/120
IP of eth1
- 2000::ffff:50a:d0e/120
I've set sysctl -w net.ipv6.conf.all.forwarding=1
at Machine B
Also, at machines A and C I've set default gateways:
At A
ip -6 ro add default via 2000::ffff:50a:b0c
At C
ip -6 ro add default via 2000::ffff:50a:d0e
I want to ping machine C from A and vice versa.
The strange thing, that most part of ICMP packets are lost with message
Address unreachable
routing ipv6 ping forwarding
asked May 9 at 12:24
Evgeniy
61
61
I instead use a bridge interface if the same subnet is on two different interfaces of a host
â thrig
May 9 at 14:41
Which virtualization system are you using, and what type of interface (host, NAT, bridge, etc.) do the VMs have to the host?
â ErikF
May 9 at 16:16
If the addresses in your examples are the actual addresses you are using, I would strongly suggest using Unique Local Addresses instead, and with/64
subnets instead of/120
.
â Johan Myréen
May 9 at 20:10
/120 means they are in different subnets, so it's routed. Reproducing the very same configuration with 3 network namespaces (linux) works fine here.
â A.B
May 11 at 20:29
@A.B i don't know why, but the problem was in neighbor table. I manually set mapping between ip and mac addresses and it works fine
â Evgeniy
May 16 at 10:10
 |Â
show 1 more comment
I instead use a bridge interface if the same subnet is on two different interfaces of a host
â thrig
May 9 at 14:41
Which virtualization system are you using, and what type of interface (host, NAT, bridge, etc.) do the VMs have to the host?
â ErikF
May 9 at 16:16
If the addresses in your examples are the actual addresses you are using, I would strongly suggest using Unique Local Addresses instead, and with/64
subnets instead of/120
.
â Johan Myréen
May 9 at 20:10
/120 means they are in different subnets, so it's routed. Reproducing the very same configuration with 3 network namespaces (linux) works fine here.
â A.B
May 11 at 20:29
@A.B i don't know why, but the problem was in neighbor table. I manually set mapping between ip and mac addresses and it works fine
â Evgeniy
May 16 at 10:10
I instead use a bridge interface if the same subnet is on two different interfaces of a host
â thrig
May 9 at 14:41
I instead use a bridge interface if the same subnet is on two different interfaces of a host
â thrig
May 9 at 14:41
Which virtualization system are you using, and what type of interface (host, NAT, bridge, etc.) do the VMs have to the host?
â ErikF
May 9 at 16:16
Which virtualization system are you using, and what type of interface (host, NAT, bridge, etc.) do the VMs have to the host?
â ErikF
May 9 at 16:16
If the addresses in your examples are the actual addresses you are using, I would strongly suggest using Unique Local Addresses instead, and with
/64
subnets instead of /120
.â Johan Myréen
May 9 at 20:10
If the addresses in your examples are the actual addresses you are using, I would strongly suggest using Unique Local Addresses instead, and with
/64
subnets instead of /120
.â Johan Myréen
May 9 at 20:10
/120 means they are in different subnets, so it's routed. Reproducing the very same configuration with 3 network namespaces (linux) works fine here.
â A.B
May 11 at 20:29
/120 means they are in different subnets, so it's routed. Reproducing the very same configuration with 3 network namespaces (linux) works fine here.
â A.B
May 11 at 20:29
@A.B i don't know why, but the problem was in neighbor table. I manually set mapping between ip and mac addresses and it works fine
â Evgeniy
May 16 at 10:10
@A.B i don't know why, but the problem was in neighbor table. I manually set mapping between ip and mac addresses and it works fine
â Evgeniy
May 16 at 10:10
 |Â
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f442750%2fipv6-forwarding-doesnt-work%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
I instead use a bridge interface if the same subnet is on two different interfaces of a host
â thrig
May 9 at 14:41
Which virtualization system are you using, and what type of interface (host, NAT, bridge, etc.) do the VMs have to the host?
â ErikF
May 9 at 16:16
If the addresses in your examples are the actual addresses you are using, I would strongly suggest using Unique Local Addresses instead, and with
/64
subnets instead of/120
.â Johan Myréen
May 9 at 20:10
/120 means they are in different subnets, so it's routed. Reproducing the very same configuration with 3 network namespaces (linux) works fine here.
â A.B
May 11 at 20:29
@A.B i don't know why, but the problem was in neighbor table. I manually set mapping between ip and mac addresses and it works fine
â Evgeniy
May 16 at 10:10