Re: VMware: Linux (host) / XP (guest)

From: Douglas Mayne (doug_at_SLACKWARE-1.localnet)
Date: 06/08/05 

Date: Tue, 07 Jun 2005 17:38:28 -0600

On Tue, 07 Jun 2005 21:55:18 +0200, Bruno wrote:

> Douglas Mayne wrote:
>
>> On Mon, 06 Jun 2005 19:03:50 +0200, Bruno wrote:
>>
>>> Hello,
>>>
>>> how to concretely setup Windows XP (guest) to connect to Internet from
>>> Linux (host) ?
>>> I use a xDSL connection in Linux and already have interfaces setup (see
>>> hereafter ifconfig) and ping (to/from) between guest and host working.
>>> So now what it is the next step ? Gateway ? Routing ?
>>> Thanks.
>>>
>>>
>>> eth0 Link encap:Ethernet HWaddr 00:50:BA:2A:64:82
>>> inet6 addr: fe80::250:baff:fe2a:6482/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:8801 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:6605 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:3 txqueuelen:1000
>>> RX bytes:3987069 (3.8 MiB) TX bytes:437800 (427.5 KiB)
>>> Interrupt:50 Base address:0x6c00
>>>
>>> lo Link encap:Local Loopback
>>> inet addr:127.0.0.1 Mask:255.0.0.0
>>> inet6 addr: ::1/128 Scope:Host
>>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>>> RX packets:1673 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:1673 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:0
>>> RX bytes:1574890 (1.5 MiB) TX bytes:1574890 (1.5 MiB)
>>>
>>> ppp0 Link encap:Point-to-Point Protocol
>>> inet addr:83.134.237.86 P-t-P:83.134.237.1
>>> Mask:255.255.255.255
>>> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
>>> RX packets:5437 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:3236 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:3
>>> RX bytes:3665537 (3.4 MiB) TX bytes:265253 (259.0 KiB)
>>>
>>> vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
>>> inet addr:192.168.213.1 Bcast:192.168.213.255
>>> Mask:255.255.255.0 inet6 addr: fe80::250:56ff:fec0:1/64
>>> Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>>
>>> vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
>>> inet addr:172.16.192.1 Bcast:172.16.192.255
>>> Mask:255.255.255.0 inet6 addr: fe80::250:56ff:fec0:8/64
>>> Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:629 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>>
>>> Thanks,
>>> Bruno
>>>
>> When you "build" a virtual machine to boot with VMWare, there is a dialog
>> where networking is selected. The networking choices are
>> bridged, NAT, or host-only. Either bridged or NAT will give your box
>> access to the same network as your VMWare host. I have only used NAT, but
>> I think bridged networking should give the virtual box more direct
>> access to other computers on the same subnet.
>>
>> It looks like you have properly installed VMWare (vmnetxx interfaces are
>> running.) Does your virtual box get assigned an address? Are you using
>> dialup (the ppp0 interface)? If so, double check the routing table.
>> Also, I could be wrong, but you may have to restart vmware
>> services after a establishing a dialup link or otherwise changing your
>> routing table.
>>
>> BTW: I have used VMWare running on a Linux host for a W2k guest.
>> The iptables firewall is a better firewall than possible with any firewall
>> running on top of windows, IMHO.
>
> Virtual box get assigned IP address (172.16.192.1).
> Indeed I'm using ppp0 on Linux (host). Ping XP to/from Linux is OK.
>
> Current problem seems NAT is missing as 172.16.192.x is dedicated to private
> network and so will not connect anyway to Internet. NAT should be installed
> on Linux network to allow Internet access.
>
> Bruno
>
I have no experience with IPv6 (the eth0 interface seems to be running
that). Don't you need an IPv4 address?

I don't think your virtual box is getting the address you
stated: 172.16.192.1. That address is the Linux host address (see
vmnet8). You can get the virtual address from a DOS box on your virtual
box with the command: ipconfig /all. If you don't know the address of the
boxes (or are making bad assumptions) then your ping tests are useless.

Relevant Pages

  • Re: OSX 10.3 / Linux / Windows - Ability to access instances on the same host?
    ... Its not really relevant to compare VMWare to VPC-Mac...unless you've ... (not Linux or BSD hosts), ... Using Bridged Networking with a Wireless NIC ...
    (microsoft.public.mac.virtualpc)
  • Re: Aspiring Pen-Tester Seeking Advice
    ... VMWare networking is not bad, the host OS has to be in promisc mode ... is probably best for application- and OS-level attacks (where a good ... buy it or download a solution FREE today! ...
    (Pen-Test)
  • VMWare 2 works on FreeBSD 4.10-Stable (except for NIC)
    ... I have everything working except for the networking (which is proving to ... I followed Phusion's guide for VMWare 2 and FreeBSD 4.10 located here: ... My Win 2000 Pro virtual machine can ping itself, ... FreeBSD 4.10-Stable PC ...
    (freebsd-questions)
  • Re: latest vmware beta
    ... I had a similar issue with VMWare 2 RCx, good thing I found a fix on the ... I downloaded the beta current as of an hour or so ago...ran the ... You have already setup networking. ... Modify settings or unsubscribe at: ...
    (Ubuntu)
  • Re: VMWare network setup (newbie)
    ... networking devices in its control panel. ... isnt configured and unlike what it says in the VMWare ... In the vmware configuration, you can select NAT networking, and that will grab ... a new IP address from your wireless connection, but only if it sees the ...
    (Debian-User)
Loading