2 VMs, communicating with static ipv6
up vote
0
down vote
favorite
In an attempt to better understand IPv6 routing, I've set up 2 Linux virtual machines on the same computer, that are bridged to 2 different NICs. The NICs are connected via physical cable.
However, when I assign an IPv6 address (if I understand correctly, I'm supposed to use ULAs here) to each virtual machine, and attempt to ping one machine from the other, I get this error:
sudo ip address add fde5:fc44:e261:d3d4::2 dev enp0s9
sudo ip link set up enp0s9
# ...
# first 2 lines repeated in other vm,
# except address ends in ::3 instead of ::2
# ...
vm@vm1 ~> ping -6 fde5:fc44:e261:d3d4::3
connect: Network is unreachable
I then attempt to add a route on the first vm:
sudo ip -6 route add default dev enp0s9
After this, the ping goes from saying the network is unreachable, to saying there is 100% packet loss.
No firewall is running on either virtual machine when this is happening.
What changes need to be made to my setup, to get the two virtual machines to communicate with each other after I manually assign each IPv6 addresses?
linux ip iproute
asked Nov 27 at 3:52
Aaron Thomas
1244
add a comment |
up vote
0
down vote
favorite
In an attempt to better understand IPv6 routing, I've set up 2 Linux virtual machines on the same computer, that are bridged to 2 different NICs. The NICs are connected via physical cable.
However, when I assign an IPv6 address (if I understand correctly, I'm supposed to use ULAs here) to each virtual machine, and attempt to ping one machine from the other, I get this error:
sudo ip address add fde5:fc44:e261:d3d4::2 dev enp0s9
sudo ip link set up enp0s9
# ...
# first 2 lines repeated in other vm,
# except address ends in ::3 instead of ::2
# ...
vm@vm1 ~> ping -6 fde5:fc44:e261:d3d4::3
connect: Network is unreachable
I then attempt to add a route on the first vm:
sudo ip -6 route add default dev enp0s9
After this, the ping goes from saying the network is unreachable, to saying there is 100% packet loss.
No firewall is running on either virtual machine when this is happening.
What changes need to be made to my setup, to get the two virtual machines to communicate with each other after I manually assign each IPv6 addresses?
linux ip iproute
asked Nov 27 at 3:52
Aaron Thomas
1244
Yes, ULAs are correct. However, as they are bridged, they still should be on the same subnet; so use/32etc. Test routing withip get ....
– dirkt
Nov 27 at 7:42
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In an attempt to better understand IPv6 routing, I've set up 2 Linux virtual machines on the same computer, that are bridged to 2 different NICs. The NICs are connected via physical cable.
However, when I assign an IPv6 address (if I understand correctly, I'm supposed to use ULAs here) to each virtual machine, and attempt to ping one machine from the other, I get this error:
sudo ip address add fde5:fc44:e261:d3d4::2 dev enp0s9
sudo ip link set up enp0s9
# ...
# first 2 lines repeated in other vm,
# except address ends in ::3 instead of ::2
# ...
vm@vm1 ~> ping -6 fde5:fc44:e261:d3d4::3
connect: Network is unreachable
I then attempt to add a route on the first vm:
sudo ip -6 route add default dev enp0s9
After this, the ping goes from saying the network is unreachable, to saying there is 100% packet loss.
No firewall is running on either virtual machine when this is happening.
What changes need to be made to my setup, to get the two virtual machines to communicate with each other after I manually assign each IPv6 addresses?
linux ip iproute
asked Nov 27 at 3:52
Aaron Thomas
1244
In an attempt to better understand IPv6 routing, I've set up 2 Linux virtual machines on the same computer, that are bridged to 2 different NICs. The NICs are connected via physical cable.
However, when I assign an IPv6 address (if I understand correctly, I'm supposed to use ULAs here) to each virtual machine, and attempt to ping one machine from the other, I get this error:
sudo ip address add fde5:fc44:e261:d3d4::2 dev enp0s9
sudo ip link set up enp0s9
# ...
# first 2 lines repeated in other vm,
# except address ends in ::3 instead of ::2
# ...
vm@vm1 ~> ping -6 fde5:fc44:e261:d3d4::3
connect: Network is unreachable
I then attempt to add a route on the first vm:
sudo ip -6 route add default dev enp0s9
After this, the ping goes from saying the network is unreachable, to saying there is 100% packet loss.
No firewall is running on either virtual machine when this is happening.
What changes need to be made to my setup, to get the two virtual machines to communicate with each other after I manually assign each IPv6 addresses?
linux ip iproute
linux ip iproute
asked Nov 27 at 3:52
Aaron Thomas
1244
asked Nov 27 at 3:52
Aaron Thomas
1244
asked Nov 27 at 3:52
Aaron Thomas
1244
asked Nov 27 at 3:52
Aaron Thomas
1244
asked Nov 27 at 3:52
Aaron Thomas
1244
1244
Yes, ULAs are correct. However, as they are bridged, they still should be on the same subnet; so use/32etc. Test routing withip get ....
– dirkt
Nov 27 at 7:42
add a comment |
Yes, ULAs are correct. However, as they are bridged, they still should be on the same subnet; so use/32etc. Test routing withip get ....
– dirkt
Nov 27 at 7:42
Yes, ULAs are correct. However, as they are bridged, they still should be on the same subnet; so use
/32 etc. Test routing with ip get ....– dirkt
Nov 27 at 7:42
Yes, ULAs are correct. However, as they are bridged, they still should be on the same subnet; so use
/32 etc. Test routing with ip get ....– dirkt
Nov 27 at 7:42
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2funix.stackexchange.com%2fquestions%2f484352%2f2-vms-communicating-with-static-ipv6%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
Yes, ULAs are correct. However, as they are bridged, they still should be on the same subnet; so use
/32etc. Test routing withip get ....– dirkt
Nov 27 at 7:42