it is not large, is it: I will set up the tunnel and attach what you want. I have set up the tunnel. systemd-networkd configured it immediately when I issued ip tunnel add with parameters. here is ip addr output:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 00:25:90:31:ec:c6 brd ff:ff:ff:ff:ff:ff
inet 91.121.100.5/24 brd 91.121.100.255 scope global dynamic eth0
valid_lft 572sec preferred_lft 572sec
inet6 fe80::225:90ff:fe31:ecc6/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 00:25:90:31:ec:c7 brd ff:ff:ff:ff:ff:ff
4: vmnet: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP group default qlen 1000
link/ether 32:1b:ee:cb:a8:59 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.1/24 brd 10.0.0.255 scope global vmnet
valid_lft forever preferred_lft forever
inet6 2001:470:71:796::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::301b:eeff:fecb:a859/64 scope link
valid_lft forever preferred_lft forever
17: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
master vmnet state UNKNOWN group default qlen 1000
link/ether fe:ab:50:47:ec:78 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcab:50ff:fe47:ec78/64 scope link
valid_lft forever preferred_lft forever
18: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
link/sit 0.0.0.0 brd 0.0.0.0
19: ipv6@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue
state UNKNOWN group default qlen 1
link/sit 91.121.100.5 peer 216.66.80.162
inet6 2001:470:71:796::1/128 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5b79:6405/64 scope link
valid_lft forever preferred_lft forever
Here are configs:
ipv4.network:
[Match]
Name=eth0
[Network]
DHCP=ipv4
IPv6AcceptRouterAdvertisements=false
Tunnel=ipv6
ipv6.netdev:
[NetDev]
Name=ipv6
Kind=sit
[Tunnel]
Local=91.121.100.5
Remote=216.66.80.162
ipv6.network:
[Match]
Name=ipv6
[Network]
Address=2001:470:71:796::1/128
IPv6AcceptRouterAdvertisements=false
[Route]
Destination=::/0
PreferredSource=2001:470:71:796::1
W dniu 27.05.2016 o 18:37, Tom Gundersen pisze:
> On Fri, May 27, 2016 at 5:11 PM, Michał Zegan
> <webczat_...@poczta.onet.pl <mailto:webczat_...@poczta.onet.pl>> wrote:
>
> Hello, I have encountered a very interesting problem: I have a wired
> ipv4 network configured via systemd-network, and an ipv6 sit tunnel.
> The problem is it does not start. trying to restart systemd-networkd
> gives the error like both local and remote addresses of the tunnel are
> incompatible. I assume that means there is no interface matching those
> ipv4 addresses. I know that eth0 interface is configured *after* this
> sit one, and it is configured via dhcp, so it is quite possible. What is
> happening?
>
>
> Hi Michał,
>
> Could you configure it manually (using ip(8) or something) and paste the
> output of `ip link` and `ip addr`, and also attach the networkd
> configuration you tried to use (would be great of course if you could
> make it as minimal as possible, but still showing your problem).
>
> Cheers,
>
> Tom
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
