<div dir="ltr">Normally you'd bring an interface thats going to be part of a bridge up without an IP address, then add it to the bridge and assign an ip address to the bridge. Weird shit happens when you add an interface with an IP to a bridge.<div>
<br></div><div>Try something like</div><div>ifconfig eth0:1 0.0.0.0</div><div>brctl addbr br100</div><div>brctl addif br100 eth0:1</div><div>ifconfig br100 <ip mess that I cant remember></div><div><br></div><div>Or come to LCA and ask all the openstack guys here directly :P</div>
<div><br></div><div>Adam</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 9, 2014 at 11:28 AM, Rowcliffe Browne <span dir="ltr"><<a href="mailto:rbkbrowne@gmail.com" target="_blank">rbkbrowne@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi All,<div><br></div><div>I'm new to the list, but have been recommended by a colleague that i post my issue here incase any of you can help. I've been a linux user since the mid 90's and administrating for the last 4-5 years or so.<br clear="all">
<div><br></div><div>my issue is with an Openstack (havana) install on Ubuntu 13.10 in the following all-in-one configuration:</div><div>controller on eth0 (192.168.1.90)</div><div>compute on eth0:1 (192.168.1.91)</div><div>
nova-network is set to create bridge br100 on eth0:1 for the VM's flat network (<a href="http://10.0.0.0/24" target="_blank">10.0.0.0/24</a>)</div><div><br></div><div>The problems i'm having so far are:</div><div>
1) on bootup, br100 seems to come up before eth0 is ready, and fails</div>
<div>2) on bootup, eth0 (Realtek RTL8111/8168/8411) is in a failed state (ifconfig shows no configured IP's) and requires module reinsertion (rmmod r8169 ; modprobe r8169) before it starts working</div><div>3) restarting nova-network after fixing eth0 breaks network connectivity until i manually remove eth0:1 from the bridge (brctl delif br100 eth0:1) and restart the networking service. Setting up the bridge on eth0 also causes the same failure. </div>
<div><br></div><div>i'm not particularly concerned with #1 and #2 as they can possibly be fixed with init ordering/dependencies, or at worst, rc.local hacks.</div><div><br></div><div>#3 is doing my head in, and unfortunately i havent played with bridging enough to know what normal configuration / behaviour should be. </div>
<div><br></div><div>default routing is correct (default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0) and working.</div><div><br></div><div>so my questions to you linux/openstack guru's out there:</div>
<div>1) can you bridge to a virtual interface? (google finds no similar examples)</div><div>2) nova-network is handling the configuration of br100, but it has no IP. is this correct?</div><div>3) do i need to add routing for br100, or will the default gateway setup be enough?</div>
<div><br></div><div>i'm happy to provide config or output if it will help debug.</div><div><br></div><div>any input would be greatly appreciated!</div><div><br></div><div>cheers,</div><div>rowy.</div><span class="HOEnZb"><font color="#888888"><div>
<br></div>-- </font></span></div><span class="HOEnZb"><font color="#888888">
<div>we are the music makers, we are the dreamers of dreams. -- Arthur O'Shaughnessy
</div></font></span></div>
<br>_______________________________________________<br>
PLUG discussion list: <a href="mailto:plug@plug.org.au">plug@plug.org.au</a><br>
<a href="http://lists.plug.org.au/mailman/listinfo/plug" target="_blank">http://lists.plug.org.au/mailman/listinfo/plug</a><br>
Committee e-mail: <a href="mailto:committee@plug.org.au">committee@plug.org.au</a><br>
PLUG Membership: <a href="http://www.plug.org.au/membership" target="_blank">http://www.plug.org.au/membership</a><br></blockquote></div><br></div>