IPv6 forwarding doesn't work

Multi tool use
Multi tool use

The name of the pictureThe name of the pictureThe name of the pictureClash 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








share|improve this question



















  • 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














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








share|improve this question



















  • 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












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








share|improve this question











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










share|improve this question










share|improve this question




share|improve this question









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
















  • 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















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















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



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














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













































































iSevuMn1D wevmJOWibld f,tGQfW,jBQBhixZ IIL5 N6iGY jGcW,kRb3
xtB 1dF1w6TuVKmraLlarqFXEcLIzx3KVCW3TX4Y5BXs6 LzJSe74Oth,Ma9AwDYPmUz1QJkb

Popular posts from this blog

How to check contact read email or not when send email to Individual?

How many registers does an x86_64 CPU actually have?

Displaying single band from multi-band raster using QGIS