<p>To be visible to outside the LAN does not require a second physical NIC, there are a number of ways to do that binding to a single NIC.</p>
<p>The OP needs to post a more detailed description of his topology.</p>
<p>Tony</p>
<div class="gmail_quote">On Aug 3, 2013 4:49 PM, "Kevin LaTona" <<a href="mailto:lists@studiosola.com">lists@studiosola.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Tony,<br>
<br>
You are correct I did make an assumption about the OP.<br>
<br>
When it mentioned wanting a container to be "visible from the outside".<br>
<br>
I made the assumption that meant from outside of the local LAN.<br>
<br>
Which may or may not be the end case.<br>
<br>
<br>
-Kevin<br>
<br>
<br>
<br>
<br>
On Aug 3, 2013, at 2:49 PM, Tony Su <<a href="mailto:tonysu@su-networking.com">tonysu@su-networking.com</a>> wrote:<br>
<br>
> Kevin<br>
><br>
> I don't see anywhere the OP described his Host as multi-homed, much<br>
> less that the Container would be.<br>
><br>
> On general principles multiple NICs only make sense when connecting to<br>
> multiple <physical> networks, isolated from one another...<br>
><br>
> But, given the information posted, that is a very big assumption. If<br>
> nothing of the like is described, then I assume only one physical NIC<br>
> connecting to a single network which can support any number of IP<br>
> addresses and bridged devices which could in turn support any number<br>
> of virtual networks with their own addresses.<br>
><br>
> Tony<br>
><br>
> On Thu, Aug 1, 2013 at 1:44 PM, Kevin LaTona <<a href="mailto:lists@studiosola.com">lists@studiosola.com</a>> wrote:<br>
>> Tony,<br>
>><br>
>> If the container is being made available to both a public ip connection and<br>
>> a private ip connection at the same time.<br>
>><br>
>> Would it not require either 2 NICS's that are connected to 2 different<br>
>> networks.<br>
>><br>
>> For example one would be running on a private bridged network and the other<br>
>> on a public bridged network via these different NIC cards.<br>
>><br>
>> Or a router using NAT to punch a hole into the local network that this<br>
>> container is on?<br>
>><br>
>> -Kevin<br>
>><br>
>><br>
>><br>
>><br>
>> On Aug 1, 2013, at 8:57 AM, Tony Su <<a href="mailto:tonysu@su-networking.com">tonysu@su-networking.com</a>> wrote:<br>
>><br>
>> ---------- Forwarded message ----------<br>
>> From: "Tony Su" <<a href="mailto:tonysu@su-networking.com">tonysu@su-networking.com</a>><br>
>> Date: Aug 1, 2013 8:56 AM<br>
>> Subject: Re: [Lxc-users] Setting up server in lxc container for dummies<br>
>> To: "Kevin LaTona" <<a href="mailto:lists@studiosola.com">lists@studiosola.com</a>><br>
>> Cc:<br>
>><br>
>> You don't need multiple hardware NICs.<br>
>> Just bind your Container network config to the same bridge device that<br>
>> connects to the proper physical network and configure your IP address in the<br>
>> Container if not already specified in your LXCconfig.<br>
>><br>
>> Assumes you're configuring static addressing and not using DHCP.<br>
>><br>
>> Tony<br>
>><br>
>> On Jul 31, 2013 10:33 PM, "Kevin LaTona" <<a href="mailto:lists@studiosola.com">lists@studiosola.com</a>> wrote:<br>
>>><br>
>>><br>
>>> On Jul 31, 2013, at 8:24 PM, Dan Kegel <<a href="mailto:dank@kegel.com">dank@kegel.com</a>> wrote:<br>
>>><br>
>>> There are plenty of web pages about this, but they seem to<br>
>>> assume that you've created the lxc config file by hand.<br>
>>> I have never done that; I just use whatever lxc-create creates.<br>
>>><br>
>>><br>
>>><br>
>>> I should also add that much of lxc files are created for you when creating<br>
>>> the container as you stated earlier.<br>
>>><br>
>>> All I've been doing is tweaking these pre fab files to work in a bridged<br>
>>> static ip mode vs dhcp mode.<br>
>>><br>
>>><br>
>>><br>
>>> In other words you are not going to have to be writing all the config<br>
>>> files from square one.<br>
>>><br>
>>> Rather tweaking and adding a few lines here and there.<br>
>>><br>
>>><br>
>>> -Kevin<br>
>>><br>
>>><br>
>>> ------------------------------------------------------------------------------<br>
>>> Get your SQL database under version control now!<br>
>>> Version control is standard for application code, but databases havent<br>
>>> caught up. So what steps can you take to put your SQL databases under<br>
>>> version control? Why should you start doing it? Read more to find out.<br>
>>><br>
>>> <a href="http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk</a><br>
>>> _______________________________________________<br>
>>> Lxc-users mailing list<br>
>>> <a href="mailto:Lxc-users@lists.sourceforge.net">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>
>> ------------------------------------------------------------------------------<br>
>> Get your SQL database under version control now!<br>
>> Version control is standard for application code, but databases havent<br>
>> caught up. So what steps can you take to put your SQL databases under<br>
>> version control? Why should you start doing it? Read more to find out.<br>
>> <a href="http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________</a><br>
>> Lxc-users mailing list<br>
>> <a href="mailto:Lxc-users@lists.sourceforge.net">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>
>><br>
><br>
> ------------------------------------------------------------------------------<br>
> Get your SQL database under version control now!<br>
> Version control is standard for application code, but databases havent<br>
> caught up. So what steps can you take to put your SQL databases under<br>
> version control? Why should you start doing it? Read more to find out.<br>
> <a href="http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk</a><br>
> _______________________________________________<br>
> Lxc-users mailing list<br>
> <a href="mailto:Lxc-users@lists.sourceforge.net">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>
<br>
</blockquote></div>