<html><head><style>blockquote.cite
{margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right: 0px; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204);}
blockquote.cite2
{margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right: 0px; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 3px; padding-top: 0px;}
a img
{border: 0px;}
body, #x4bd0089f34a5444
{font-family: Tahoma; font-size: 12pt;}
</style></head><body background=""><div>Just want to point out that the restriction only occurs between the host and its containers. Outside of it, it can talk without problems.</div><div id="signature_old"><div style="font-family: Tahoma; font-size: 12 pt;"><hr>
<p><strong>Christian Tardif</strong></p></div></div><div><br></div><div><br></div><div><br></div>
<div>------ Message d'origine ------</div>
<div>De: "Christian Tardif" <<a href="mailto:christian.tardif@servinfo.ca">christian.tardif@servinfo.ca</a>></div>
<div>À: "LXC users mailing-list" <<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a>></div>
<div>Envoyé : 2016-11-07 22:09:40</div>
<div>Objet : Re: [lxc-users] Something catastrophic just happened to LXC networking</div><div><br></div>
<div id="x4bd0089f34a5444"><blockquote cite="em10a38157-a732-402f-ac17-60d7fade2c05@tardich052015" type="cite" class="cite2">
<div>This is normal behavior with both macvlan's and ipvlan's</div><div><br></div><div>Even if I have seen it working a few times, I can't explain the exact details. But normally, MACVLAN and IPVLAN do not support communications from and to the master host:</div><div><br></div><div><a href="https://people.netfilter.org/pablo/netdev0.1/papers/IPVLAN-The-beginning.pdf">https://people.netfilter.org/pablo/netdev0.1/papers/IPVLAN-The-beginning.pdf</a></div><div><br></div><div id="signature_old"><div style="font-family: Tahoma; font-size: 12 pt;"><hr>
<p><strong>Christian Tardif</strong></p></div></div><div><br></div><div><br></div><div><br></div>
<div>------ Message d'origine ------</div>
<div>De: "Saint Michael" <<a href="mailto:venefax@gmail.com">venefax@gmail.com</a>></div>
<div>À: "LXC users mailing-list" <<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a>></div>
<div>Envoyé : 2016-11-07 10:57:43</div>
<div>Objet : [lxc-users] Something catastrophic just happened to LXC networking</div><div><br></div>
<div id="xc52ed814d1fe4ed"><blockquote cite="CAC9cSOCDB9j8QqRRuJ8dZVS4fy5gdwQH+US8h3cpxXJgrB1+Mg@mail.gmail.com" type="cite" class="cite2">
<div dir="ltr"><div style="font-size:small" class="gmail_default">Since the last update to Ubuntu, now I cannot ping or ssh into any container, from the same network. It seems the packets go to the router, for I can ping and communicate to the containers from outside my network. This problem did not happen until a few days ago.<br><br></div><div style="font-size:small" class="gmail_default">My networking at the container level is:<br><br>lxc.network.type=macvlan<br>lxc.network.macvlan.mode=bridge<br>lxc.network.link=eth0<br><a href="http://lxc.network.name">lxc.network.name</a> = eth1<br>lxc.network.flags=up<br>lxc.network.hwaddr = mac.add.re.ss<br>lxc.network.ipv4 = <a href="http://0.0.0.0/24">0.0.0.0/24</a><br></div><br><div style="font-size:small" class="gmail_default">on the host, the interface eth0 is also used by the host, but I tried with another interface which is UP but it has no IP, and it still does not allow me to reach my containers, in fact taking my business down since I execute a lot of stuff remotely.<br></div><div style="font-size:small" class="gmail_default">Any idea?<br></div><div style="font-size:small" class="gmail_default"><br></div><br></div>
</blockquote></div>
</blockquote></div>
</body></html>