On Wed, Jun 13, 2012 at 9:12 PM, Les Mikesell <lesmikesell@xxxxxxxxx> wrote:
> On Wed, Jun 13, 2012 at 1:52 AM, Sanjay Arora <sanjay.k.arora@xxxxxxxxx> wrote:
>>
> OK, I don't quite understand what 'reserved for LAN' use means. I'll
> assume it means someone else controls it and they won't cooperate if
Correct.
> you bridge you VM's to the LAN. In most scenarios, the adsl router
> would give out DHCP addresses and unless you run out, bridged machines
> would just grab their own address and work just like a new physical
> machine.
>
True Enough but the adsl Ip range is not in my control as you have
assumed correctly.
>> Now My machine has a second card for LTSP Network (it is a LTSP
>> Server) with IP 172.16.1.0/24
>>
>> I want Virtual hosts on my machine so I have to have a different IP
>> range....say 192.168.2.0/24
>>
>> And I want routing among three as well as Internet access through the
>> NATTED adsl router which has a dynamic IP.
>>
>> This is my problem.
>
> You still don't say what kind of access you need
Basically accessing the VMs from the Internet....ssh, vnc, rdp, ftp &
so on...different needs for different vm.
> - or why you can't
> bridge on the 172.16.1.0 side which eliminates half of the problem.
> Outbound connections are easy - your LTSP clients probably already
> have that via NAT on the server, and they also should be using the
> server as their default gateway.
Yes LTSP has outward NAT access...require the same inward access there too...
> If you don't want the VM guests on
> the same subnet, you can create a new guest-only subnet with the same
> setup as the LTSP side (server is default gateway and can route among
> all networks). So you only have a problem if you need to accept
> inbound connections from the LAN or internet. You probably don't have
> that now for the LTSP subnet. Do you need it for the VMs?
Yes to both.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
