<br><br><div class="gmail_quote">On Tue, Apr 26, 2011 at 6:03 PM, Mauras Olivier <span dir="ltr"><<a href="mailto:oliver.mauras@gmail.com">oliver.mauras@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><div></div><div class="h5"><br><br><div class="gmail_quote">On Sat, Apr 23, 2011 at 12:40 PM, Mauras Olivier <span dir="ltr"><<a href="mailto:oliver.mauras@gmail.com" target="_blank">oliver.mauras@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Geordy,<br><br>Thanks for your reply. The first one is actually already set here. I asked ESX folks to create me my own vswitch with promisc mode enabled.<br>I saw the second one coming, but didn't think that could make something... There's also a setting like "mac.verify" that can be set to false directly from the .vmx file to allow you to use another MAC than 00:50:56:xxxxxx for your VM.<br>
I'll try to force a high MAC in the 00:50:56 subset for my containers and see what happens.<br><br><br>I'll let you know,<br><br>Olivier<br><br><br><div class="gmail_quote"><div><div></div><div>On Sat, Apr 23, 2011 at 9:12 AM, Geordy Korte <span dir="ltr"><<a href="mailto:gkorte@gmail.com" target="_blank">gkorte@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div><div>On Sun, Apr 17, 2011 at 8:39 AM, Geordy Korte <span dir="ltr"><<a href="mailto:gkorte@gmail.com" target="_blank">gkorte@gmail.com</a>></span> wrote:<br>
</div><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
Thought about it some more and i think it might be an advanced esx feature that restricts this. Basically a couple of adv features block spoofing and mac changes on a vhost. I will try to find the specific command you need to run on an esx host tomorrow, or maybee someone can google it. I am 100% sure that it's not a bug in either esx or lxc and no modifications are needed on the lxc side.<br>
<br></blockquote></div><div><br>Hi,<br><br>Sorry for the delay, kids birthday and my new job has not left me with much time. Anyways I did some digging and founds some stuff that might help.<br><br>The first one is in the properties of the vswitch that is interconnecting the lxc host to the network. Edit the properties and in the Security Tab make sure that promiscus mode, Mac changes and forged macs are set to accept. Basically the vswitch will allow all mac's coming from the lxc and not block them.<br>
<br>The second tip is more of a maybee... ESX 3.x basically would allow to you to change the mac of the Vhost to whatever you wanted. In ESX 4.0 Vmware rewrote the code and would allow you to specify a mac only if it was in the vmware OUI range. To make sure that ESX does not cut the communication try to set the macs of you LXC containers to: 00:50:56:XX:YY:ZZ<br>
<br>I hope this helps a little. Give it a shot and let me know how it works out.<br><br>Geordy<br> </div></div>
<br></div></div>------------------------------------------------------------------------------<br>
Fulfilling the Lean Software Promise<br>
Lean software platforms are now widely adopted and the benefits have been<br>
demonstrated beyond question. Learn why your peers are replacing JEE<br>
containers with lightweight application servers - and what you can gain<br>
from the move. <a href="http://p.sf.net/sfu/vmware-sfemails" target="_blank">http://p.sf.net/sfu/vmware-sfemails</a><div><br>_______________________________________________<br>
Lxc-users mailing list<br>
<a href="mailto:Lxc-users@lists.sourceforge.net" target="_blank">Lxc-users@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/lxc-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/lxc-users</a><br>
<br></div></blockquote></div><br>
</blockquote></div><br></div></div>Hello,<br><br>Good news here!! Forcing container MAC to 00:50:56:xx:xx:xx make it work flawlessly! Two containers running at the same time without the need to restart network nor Kernel Panic. So far so good!!<br>
Problem solved for me, will be able to deploy some more containers now.<br><br>Thanks for your help.<br><font color="#888888"><br>Olivier<br><br>
</font></blockquote></div>And actually not quite well... I still have random container freezes with sometimes "eth0: received packet with own address as source address" in my dmesg.<br>The container can't access network for 30s then get's back randomly, can't find the reason of this :(<br>
<br>Still have KP with multiple containers up and running, have to check dump.<br><br>If anyone has any idea about theses network glitches...<br><br><br>Thanks,<br>Olivier<br>