Configure static ipv6 in coreos
406 views
Skip to first unread message
Imma bee
Nov 30, 2017, 12:24:57 PM11/30/17
to CoreOS User
Anyone have a single clue on how to configure ipv6 in core os? I can't find a single piece of documentation on it.
Seán C. McCord
Nov 30, 2017, 12:43:29 PM11/30/17
to Imma bee, CoreOS User
There's nothing special about it. systemd-networkd takes IPv4 addresses just the same as IPv6 addresses. Just configure them with `Address=` lines like any other.
On Thu, Nov 30, 2017 at 12:25 PM Imma bee <andyb...@gmail.com> wrote:
Anyone have a single clue on how to configure ipv6 in core os? I can't find a single piece of documentation on it.
--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Imma bee
Nov 30, 2017, 1:33:59 PM11/30/17
to CoreOS User
I did that and I can't ping any ipv6 addresses.
[Match]
Name=eth0
[Network]
Address=2607:5300:203:2116:c856:8ae0:33cb:cf63/64
Gateway=2607:5300:203:21ff:ff:ff:ff:ff
DNS=2001:4860:4860::8888
IPv6AcceptRA=yes
Address=167.114.4.96
Gateway=167.114.4.254
DNS=8.8.8.8
Seán C. McCord
Nov 30, 2017, 2:02:09 PM11/30/17
to Imma bee, CoreOS User
Would you mind pasting in your `ip -6 addr show` and `ip -6 route show`?
Seán C. McCord
Nov 30, 2017, 2:03:46 PM11/30/17
to Imma bee, CoreOS User
Actually, your network doesn't look correct, anyway. You're telling it a /64, but that gateway is not on the same /64 as your host.
Imma bee
Nov 30, 2017, 2:14:20 PM11/30/17
to CoreOS User
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 2607:5300:203:2116:c856:8ae0:33cb:cf63/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::ff:fea2:e03b/64 scope link
valid_lft forever preferred_lft forever
2607:5300:203:2116::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev docker0 proto kernel metric 256 pref medium
fe80::/64 dev vetha822604 proto kernel metric 256 pref medium
fe80::/64 dev veth10ab761 proto kernel metric 256 pref medium
fe80::/64 dev veth4d5d0bd proto kernel metric 256 pref medium
fe80::/64 dev vethr4c65cf4941 proto kernel metric 256 pref medium
fe80::/64 dev vethr97a89cdbe4 proto kernel metric 256 pref medium
fe80::/64 dev vethr9e36d318ec proto kernel metric 256 pref medium
fe80::/64 dev vethr81f4fd34f4 proto kernel metric 256 pref medium
fe80::/64 dev vethr5f7a6ebd37 proto kernel metric 256 pref medium
I can ping my windows host with the exact same nework config. 2607:5300:203:2116:c856:8ae0:33cb:cf62 /64
Seán C. McCord
Nov 30, 2017, 2:20:20 PM11/30/17
to Imma bee, CoreOS User
So that is consistent with my earlier statement. It looks like systemd-network rejected that default route. You don't see it there in the `ip -6 route show`. Make sure you didn't typo that gateway. The first four segments of the address MUST match for a /64. IPv6 addresses are 128 bits, consisting of 8 segments. Thus, a /64 says that the first half defines the network. In the configuration you showed, the gateway is outside of your local network.
--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Imma bee
Nov 30, 2017, 2:25:06 PM11/30/17
to CoreOS User
This is what OVH said to do. http://docs.ovh.ca/en/guides-network-ipv6.html
Since OVH uses a special type of routing, one might think the IPv6 gateway should be2607:5300:60:47b3:ff:ff:ff:ff. But instead, the IPv6 gateway for your IPv6 block follow this template: xxxx:xxxx:xxxx:xxff:ff:ff:ff:ff. So, our IPv6 gateway in this example will be 2607:5300:60:47ff:ff:ff:ff:ff.
Seán C. McCord
Nov 30, 2017, 3:02:35 PM11/30/17
to Imma bee, CoreOS User
Okay, they're doing something silly. As per their instructions, you will need to add a point-to-point interface route to their gateway.
Add something like the following section (removing the Gateway= statement from the main [Network] section):
[Route]
Gateway=2607:5300:60:47b3:ff:ff:ff:ff
GatewayOnLink=yes
Destination=::/0
The GatewayOnLink tells the kernel to ignore the fact that the gateway is not within the defined subnet and to just send the packets to the gateway anyway.
On Thu, Nov 30, 2017 at 2:25 PM Imma bee <andyb...@gmail.com> wrote:
This is what OVH said to do. http://docs.ovh.ca/en/guides-network-ipv6.htmlSince OVH uses a special type of routing, one might think the IPv6 gateway should be2607:5300:60:47b3:ff:ff:ff:ff. But instead, the IPv6 gateway for your IPv6 block follow this template: xxxx:xxxx:xxxx:xxff:ff:ff:ff:ff. So, our IPv6 gateway in this example will be 2607:5300:60:47ff:ff:ff:ff:ff.
--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Imma bee
Nov 30, 2017, 3:21:05 PM11/30/17
to CoreOS User
Nothing is ever standard at OVH. They gotta fuck with everything standard and make my life hell. Please tell me if the below is correct. Thank you very much for your help.
[Match]
Name=eth0
[Network]
Address=2607:5300:203:2116:c856:8ae0:33cb:cf64/64
Gateway=2607:5300:60:47b3:ff:ff:ff:ff
GatewayOnLink=yes
Destination=::/0
DNS=2001:4860:4860::8888
IPv6AcceptRA=yes
Address=167.114.4.96
Gateway=167.114.4.254
DNS=213.186.33.99
Seán C. McCord
Nov 30, 2017, 3:27:51 PM11/30/17
to Imma bee, CoreOS User
I would put the IPv6 route in a separate [Route] section, like I posted. The GatewayOnLink is ambiguous (if it is even supported in the [Network] section).
--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Imma bee
Nov 30, 2017, 3:52:49 PM11/30/17
to CoreOS User
What is strange is I can ping the other VMs from this VM and I can ping the ipv6 of the main server host which is windows. I cant ping the linux VMs from the outside but I can ping another windows VM with the same config. I did what you suggested to the config. I have complained to OVH. They say they will get back to me. Probably in two days. lul. Thanks again for your help. I'll let you know what happens.
Seán C. McCord
Nov 30, 2017, 3:58:02 PM11/30/17
to Imma bee, CoreOS User
Yes, the IP address of the Windows box you pasted is inside the /64, so it should have been pingable. Any time you add an IP address, Linux adds a route to the subnet in which that IP address resides. Thus, you can communicate with other devices inside that subnet without any explicit routes.
Imma bee
Nov 30, 2017, 5:10:08 PM11/30/17
to CoreOS User
I can ping the windows VMs from my home though but not the linux ones.
Reply all
Reply to author
Forward
0 new messages