Otdfbt

Is it advisable to add a location heads-up when a scene changes in a novel?

What is the logic behind charging tax _in the form of money_ for owning property when the property does not produce money?

How to represent jealousy in a cute way?

How do I type a hyphen in iOS 12?

What do you call the action of "describing events as they happen" like sports anchors do?

How to generate list of *all* available commands and functions?

If the pressure inside and outside a balloon balance, then why does air leave when it pops?

Realistic, logical way for men with medieval-era weaponry to compete with much larger and physically stronger foes

Parsing text written the millitext font

Why is it bad to use your whole foot in rock climbing

What is Gilligan's full Name?

Open Drain pin not going to GND

Course development: can I pay someone to make slides for the course?

Oil draining out shortly after turbo hose detached/broke

How to handle when PCs taste a potion that is actually poison?

Why did the World Bank set the global poverty line at $1.90?

In American Politics, why is the Justice Department under the President?

Do Veracrypt encrypted volumes have any kind of brute force protection?

What does this line mean in Zelazny's "The Courts of Chaos"?

What do I need to do, tax-wise, for a sudden windfall?

Why can't we do three-way comparison in C++?

Why is long-term living in Almost-Earth causing severe health problems?

How to Handle Many Times Series Simultaneously?

Forgot passport for Alaska cruise (Anchorage to Vancouver)

Systemd's Networkd: Unable to add ipv6 default route

Unable to set up a static host route - “SIOCADDRT: No such process”Linux does not get IPv6 default gateway from Cisco ASA5510 on autoconfIPv6 default gateway route disappear after rebootNative IPv6: routing between eth0 and eth1Linux server not receiving default IPv6 route over PPP linkConfigure IPv6 - CentOS OVH - Can't pingIPv6 on Amazon VPC: missing default route in UbuntuHow to route ipv6 to an openvz container?IPv6 - How does my ISP know how to route traffic to my delegated subnet?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

1

I am having a hell of a time getting IPv6 address connectivity set up on my new VPS. I thought I knew what I was doing but apparently networkd disagrees, I keep getting issues when trying to add a default route.

Here is the networking information provided to me by my ISP:

Subnet 2001:19f0:6:2::/64
Gateway 2001:19f0:6::1
Nameserver 2001:4860:4860::8888
Nameserver 2001:4860:4860::8844

Interface: ens3
OS: Ubuntu 18.04.02
Systemd version: 237

Current Setup

I can easily set up my IP address and add a route to the gateway with the following systemd file:

[Match]
Name=ens3

[Network]
Address=209.222.17.197/26
Gateway=209.222.17.193
DNS=8.8.8.8

[Network]
Address=2001:19f0:6:2::1337/64

[Route]
Destination=2001:19f0:6::1

I get no errors in journalctl, I can successfully ping 2001:19f0:6::1, but of course I don't have a default gateway or internet access. I can easily use 2001:19f0:6::1 as my default gateway with the following command:
sudo ip -6 route add default via 2001:19f0:6::1

This gives me full ipv6 routing, I can ping ipv6.google.com.

The Problem

I can't seem to get the default gateway set up in networkd, I've spent so many hours trying different combinations of options I think this might be a bug. For example, if I amend my configuration to look like this:

[Match]
Name=ens3

[Network]
Address=209.222.17.197/26
Gateway=209.222.17.193
DNS=8.8.8.8

[Network]
Address=2001:19f0:6:2::1337/64

[Route]
Destination=2001:19f0:6::1

[Route]
Gateway=2001:19f0:6::1
GatewayOnlink=true

I get the following error in the journalctl log:

May 27 19:31:46 public-NY systemd-networkd[2452]: ens3: Could not set route: No route to host

I always see that damn error "no route to host", if there's no route to 2001:19f0:6::1 then why the hell can I ping it?!

I'm fed up with this issue, but I'd like to use netplan and therefore systemd-networkd for my networking. Am I just doing something stupid or is something as critical as networkd really this broken?

routing ipv6 subnet netplan systemd-networkd

share|improve this question

asked May 27 at 23:34

Foxie The YifferFoxie The Yiffer

61

add a comment | 

1

I am having a hell of a time getting IPv6 address connectivity set up on my new VPS. I thought I knew what I was doing but apparently networkd disagrees, I keep getting issues when trying to add a default route.

Here is the networking information provided to me by my ISP:

Subnet 2001:19f0:6:2::/64
Gateway 2001:19f0:6::1
Nameserver 2001:4860:4860::8888
Nameserver 2001:4860:4860::8844

Interface: ens3
OS: Ubuntu 18.04.02
Systemd version: 237

Current Setup

I can easily set up my IP address and add a route to the gateway with the following systemd file:

[Match]
Name=ens3

[Network]
Address=209.222.17.197/26
Gateway=209.222.17.193
DNS=8.8.8.8

[Network]
Address=2001:19f0:6:2::1337/64

[Route]
Destination=2001:19f0:6::1

I get no errors in journalctl, I can successfully ping 2001:19f0:6::1, but of course I don't have a default gateway or internet access. I can easily use 2001:19f0:6::1 as my default gateway with the following command:
sudo ip -6 route add default via 2001:19f0:6::1

This gives me full ipv6 routing, I can ping ipv6.google.com.

The Problem

I can't seem to get the default gateway set up in networkd, I've spent so many hours trying different combinations of options I think this might be a bug. For example, if I amend my configuration to look like this:

[Match]
Name=ens3

[Network]
Address=209.222.17.197/26
Gateway=209.222.17.193
DNS=8.8.8.8

[Network]
Address=2001:19f0:6:2::1337/64

[Route]
Destination=2001:19f0:6::1

[Route]
Gateway=2001:19f0:6::1
GatewayOnlink=true

I get the following error in the journalctl log:

May 27 19:31:46 public-NY systemd-networkd[2452]: ens3: Could not set route: No route to host

I always see that damn error "no route to host", if there's no route to 2001:19f0:6::1 then why the hell can I ping it?!

I'm fed up with this issue, but I'd like to use netplan and therefore systemd-networkd for my networking. Am I just doing something stupid or is something as critical as networkd really this broken?

routing ipv6 subnet netplan systemd-networkd

share|improve this question

asked May 27 at 23:34

Foxie The YifferFoxie The Yiffer

61

add a comment | 

I am having a hell of a time getting IPv6 address connectivity set up on my new VPS. I thought I knew what I was doing but apparently networkd disagrees, I keep getting issues when trying to add a default route.

Here is the networking information provided to me by my ISP:

Subnet 2001:19f0:6:2::/64
Gateway 2001:19f0:6::1
Nameserver 2001:4860:4860::8888
Nameserver 2001:4860:4860::8844

Interface: ens3
OS: Ubuntu 18.04.02
Systemd version: 237

Current Setup

I can easily set up my IP address and add a route to the gateway with the following systemd file:

[Match]
Name=ens3

[Network]
Address=209.222.17.197/26
Gateway=209.222.17.193
DNS=8.8.8.8

[Network]
Address=2001:19f0:6:2::1337/64

[Route]
Destination=2001:19f0:6::1

I get no errors in journalctl, I can successfully ping 2001:19f0:6::1, but of course I don't have a default gateway or internet access. I can easily use 2001:19f0:6::1 as my default gateway with the following command:
sudo ip -6 route add default via 2001:19f0:6::1

This gives me full ipv6 routing, I can ping ipv6.google.com.

The Problem

I can't seem to get the default gateway set up in networkd, I've spent so many hours trying different combinations of options I think this might be a bug. For example, if I amend my configuration to look like this:

[Match]
Name=ens3

[Network]
Address=209.222.17.197/26
Gateway=209.222.17.193
DNS=8.8.8.8

[Network]
Address=2001:19f0:6:2::1337/64

[Route]
Destination=2001:19f0:6::1

[Route]
Gateway=2001:19f0:6::1
GatewayOnlink=true

I get the following error in the journalctl log:

May 27 19:31:46 public-NY systemd-networkd[2452]: ens3: Could not set route: No route to host

I always see that damn error "no route to host", if there's no route to 2001:19f0:6::1 then why the hell can I ping it?!

I'm fed up with this issue, but I'd like to use netplan and therefore systemd-networkd for my networking. Am I just doing something stupid or is something as critical as networkd really this broken?

routing ipv6 subnet netplan systemd-networkd

share|improve this question

asked May 27 at 23:34

Foxie The YifferFoxie The Yiffer

61

Subnet 2001:19f0:6:2::/64
Gateway 2001:19f0:6::1
Nameserver 2001:4860:4860::8888
Nameserver 2001:4860:4860::8844

Interface: ens3
OS: Ubuntu 18.04.02
Systemd version: 237

[Match]
Name=ens3

[Network]
Address=209.222.17.197/26
Gateway=209.222.17.193
DNS=8.8.8.8

[Network]
Address=2001:19f0:6:2::1337/64

[Route]
Destination=2001:19f0:6::1

[Match]
Name=ens3

[Network]
Address=209.222.17.197/26
Gateway=209.222.17.193
DNS=8.8.8.8

[Network]
Address=2001:19f0:6:2::1337/64

[Route]
Destination=2001:19f0:6::1

[Route]
Gateway=2001:19f0:6::1
GatewayOnlink=true

May 27 19:31:46 public-NY systemd-networkd[2452]: ens3: Could not set route: No route to host

share|improve this question

asked May 27 at 23:34

Foxie The YifferFoxie The Yiffer

61

share|improve this question

asked May 27 at 23:34

Foxie The YifferFoxie The Yiffer

61

asked May 27 at 23:34

Foxie The YifferFoxie The Yiffer

61

asked May 27 at 23:34

Foxie The YifferFoxie The Yiffer

61