Date: Sat, 24 Mar 2007 12:21:24 -0500 From: Les Mikesell lesmikesell@gmail.com Subject: Re: [CentOS] Samba config for Windows on VMWare To: CentOS mailing list centos@centos.org
Mark Hull-Richter wrote:>>
The vmware client is using a bridged Ethernet adapter (meaning same as the host, I think).
"Bridged" means the guest shares the host's network adapter directly but it looks like a completely different system to everyone else including the host - that is, it needs its own IP address on the same subnet.
Once that is set up, sharing files is exactly the same as with any other machine on the network.
Okay, I understand that. However, my computer is linked up to a DSL modem and has no subnet, per se, and the DSL host assigns my IP address. So:
1) Is tehre a way I can get around this and give my Windows VM its own IP address (and how)?
2) If not, how would I set up one of the other ethernet types to make this work? NAT doesn't look right for this, and I don't know enough to do a custom network, so that hints to me that host-only might work, but that calls for a vmnet1 device on the host, and I know nothing about this (but I will look - just hoped for a quickie answer here...).
Thanks.
On 3/25/07, Mark Hull-Richter mhullrich@gmail.com wrote:
"Bridged" means the guest shares the host's network adapter directly but it looks like a completely different system to everyone else including the host - that is, it needs its own IP address on the same subnet.
Okay, I understand that. However, my computer is linked up to a DSL modem and has no subnet, per se, and the DSL host assigns my IP address.
NAT is in fact exactly what you want here, I think. VMware will assign an IP from one of the unrouted ranges that are reserved for LANs for cummunication between the host and guest, but any connections from the guest to the internet will be translated to/from the host's DSL IP.
Mark Hull-Richter wrote:
The vmware client is using a bridged Ethernet adapter (meaning same as the host, I think).
"Bridged" means the guest shares the host's network adapter directly but it looks like a completely different system to everyone else including the host - that is, it needs its own IP address on the same subnet.
Once that is set up, sharing files is exactly the same as with any other machine on the network.
Okay, I understand that. However, my computer is linked up to a DSL modem and has no subnet, per se, and the DSL host assigns my IP address. So:
- Is tehre a way I can get around this and give my Windows VM its own
IP address (and how)?
Most people who want to run multiple systems behind a dsl or cablemodem get an inexpensive NAT router. With that, a bridged VM would just take another private address.
- If not, how would I set up one of the other ethernet types to make
this work? NAT doesn't look right for this, and I don't know enough to do a custom network, so that hints to me that host-only might work, but that calls for a vmnet1 device on the host, and I know nothing about this (but I will look - just hoped for a quickie answer here...).
If you only have one physical machine, the vmware NAT setup will do what you need, but it is harder to make inbound connections to the guest.
Mark Hull-Richter wrote:
Date: Sat, 24 Mar 2007 12:21:24 -0500 From: Les Mikesell lesmikesell@gmail.com Subject: Re: [CentOS] Samba config for Windows on VMWare To: CentOS mailing list centos@centos.org
Mark Hull-Richter wrote:>>
The vmware client is using a bridged Ethernet adapter (meaning same as the host, I think).
"Bridged" means the guest shares the host's network adapter directly but it looks like a completely different system to everyone else including the host - that is, it needs its own IP address on the same subnet.
Once that is set up, sharing files is exactly the same as with any other machine on the network.
Okay, I understand that. However, my computer is linked up to a DSL modem and has no subnet, per se, and the DSL host assigns my IP address. So:
- Is tehre a way I can get around this and give my Windows VM its own
IP address (and how)?
I don't know how vmware does it, but i'm sure it's possible. With xen, you do something like ifconfig dummy0 <whatever> and configure dummy0 into the bridge in place of eth0.
- If not, how would I set up one of the other ethernet types to make
this work? NAT doesn't look right for this, and I don't know enough to do a custom network, so that hints to me that host-only might work, but that calls for a vmnet1 device on the host, and I know nothing about this (but I will look - just hoped for a quickie answer here...).
If you want internet access for both concurrently, NAT is exactly what you want. See netfilter.org and consider installing shorewall.
-
Bart Schaefer -
John Summerfield -
Les Mikesell -
Mark Hull-Richter