<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Jun 10, 2017 at 12:38 PM, Michael Johnson <span dir="ltr"><<a href="mailto:johnson@cognitech-ut.com" target="_blank">johnson@cognitech-ut.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks for all the suggestions. I seem to have magically fixed it. When<br>
I changed the parent from lxdbr0 to br0 it now works. Lxdbr0 was a<br>
'network' I created with 'lxc network create' and br0 was the host<br>
bridge I configured by hand. This probably makes sense to someone who<br>
understands how lxd works. There seems to be a conflict between static<br>
ip addresses and the way 'lxc network create' defines a bridge. Possibly<br>
I missed a config option for routing that is necessary when static ip is<br>
combined with 'lxc network create'.<br>
<br></blockquote><div><br></div><div><br></div><div>You seem misunderstood some concept:</div><div><br></div><div>(1) lxc network create </div><div>- basically creates a bridge, managed by lxd, optionally with its own DHCP server (dnsmasq). </div><div>- it is a SEPARATE network from your host's network (e.g. eth0)</div><div>- you CAN assign "static ip" on this bridge. Or to be more accurate, configure the dhcp server to always assign a specific IP for that container</div><div><br></div><div>(2) host bridge (should be br0 in your example)</div><div>- on the same L2 network with your host interface</div><div>- use whatever DHCP server available on the network (if available). You should NOT create your own dhcp server on this bridge</div><div><br></div><div>(3) container's interface config</div><div>- there are some ways to setup an container's IP address</div><div>- a container can, most of the times, overide IP address assignment on lxc config</div><div>- the best setup, IMHO, is to either:</div><div>--> have container using dhcp, and setup the DHCP server (which include lxd's dnsmasq) to assign persistent ip address. This is the example listed on <a href="https://stgraber.org/2016/10/27/network-management-with-lxd-2-3/">https://stgraber.org/2016/10/27/network-management-with-lxd-2-3/</a> . OR</div><div>--> configure the container OS (e.g. on /etc/network/interfaces, or equivalent distro location) to use static IP</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Did not work:<br>
<br>
devices:<br>
default:<br>
ipv4.address: <a href="http://192.168.0.36/24" rel="noreferrer" target="_blank">192.168.0.36/24</a><br>
name: eth0<br>
<span class="gmail-"> nictype: bridged<br>
parent: lxdbr0<br>
type: nic<br>
<br></span></blockquote><div><br></div><div>Which is the correct behavior. Since lxdbr0 is on separate network from your host's eth0</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
</span>Did work:<br>
<br>
devices:<br>
default:<br>
ipv4.address: <a href="http://192.168.0.36/24" rel="noreferrer" target="_blank">192.168.0.36/24</a><br>
name: eth0<br>
nictype: bridged<br>
parent: br0<br>
type: nic<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br></div></div></blockquote><div><br></div><div>This is probably where you don't setup any IP configuration on the container side, so it continue to use whatever address assigned by lxd when the container started. For this type of setup though, I recommend to NOT rely on lxc config file, but rather set it up directly in the container OS.</div><div><br></div><div>-- </div><div>Fajar</div></div></div></div>