On Sat, 2015-11-14 at 15:18 +0530, Ritesh Raj Sarraf wrote: > That said, it still does not work. And the odd part is, networking is > only broken for IPv4.
From within the container, this reporting from networkctl is interesting. It states: root@deb-template:~# networkctl status ● State: routable Address: 172.16.221.159 on host0 169.254.190.70 on host0 fe80::c48a:3cff:feae:252 on host0 Gateway: 172.16.20.1 on host0 root@deb-template:~# networkctl status -a ● 1: lo Link File: n/a Network File: n/a Type: loopback State: carrier (unmanaged) MTU: 65536 Address: 127.0.0.1 ::1 ● 2: host0 Link File: n/a Network File: /lib/systemd/network/80-container-host0.network Type: ether State: routable (configured) HW Address: c6:8a:3c:ae:02:52 MTU: 1500 Address: 172.16.221.159 169.254.190.70 fe80::c48a:3cff:feae:252 Gateway: 172.16.20.1 root@deb-template:~# ping 172.16.20.1 PING 172.16.20.1 (172.16.20.1) 56(84) bytes of data. ^C --- 172.16.20.1 ping statistics --- 9 packets transmitted, 0 received, 100% packet loss, time 7999ms root@deb-template:~# I am not sure how it determines the "routable" status. The default gateway is 172.16.20.1, which is not pingable. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
