Re: VMware: Linux (host) / XP (guest)
From: Douglas Mayne (doug_at_SLACKWARE-1.localnet)
Date: 06/08/05
- Next message: dave_at_umiacs.umd.edu: "Re: reverse command"
- Previous message: Cliff: "Port binding"
- In reply to: Bruno: "Re: VMware: Linux (host) / XP (guest)"
- Next in thread: Bruno: "Re: VMware: Linux (host) / XP (guest)"
- Reply: Bruno: "Re: VMware: Linux (host) / XP (guest)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 08 Jun 2005 08:31:36 -0600
On Wed, 08 Jun 2005 08:23:58 +0200, Bruno wrote:
> Douglas Mayne wrote:
>
>> 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)
>>>>>
<snip>
>
Your linux host has no trouble connecting to the internet, right? Your
setup is a little different than the machines I have used.
When you install VMWare the first time, there are several questions which
affect the global settings for the host. These control the vmware
services which start at bootup. It looks like you did setup for NAT, and
it selected the 172.16.192.0 network to use as a virtual network. If you
are still not able to connect to the internet through the virtual
host, then the problem could be any of these:
1. Bad routing table.
2. Bad startup order for services (VMWare after DSL modem ppp??)
3. Improper firewall settings at linux host (virtual network blocked.)
4. Improper DNS configuration.
5. IP forwarding needs to be enabled. I think that this is required with
your setup to allow forwarding across interfaces: DSL modem (ppp0) <->
virtual network (vmnetx).
Here are some things to check (in the same order as above):
1. route -n
2. Restart vmware services after DSL connection active.
I am not running Fedora, so I don't know exactly where vmware installs its
startup script, (look for the file vmware somewhere below /etc/rc.d
/etc/rc.d/init.d/vmware ?).
3. iptables -L
4. cat /etc/resolv.conf
5. echo 1>/proc/sys/net/ipv4/ipforward
- Next message: dave_at_umiacs.umd.edu: "Re: reverse command"
- Previous message: Cliff: "Port binding"
- In reply to: Bruno: "Re: VMware: Linux (host) / XP (guest)"
- Next in thread: Bruno: "Re: VMware: Linux (host) / XP (guest)"
- Reply: Bruno: "Re: VMware: Linux (host) / XP (guest)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
