Mailinglist Archive: opensuse (3442 mails)
| < Previous | Next > |
Masquerading and VMWare
- From: Clayton Cornell <c.cornell@xxxxxxxxx>
- Date: Thu, 13 Dec 2001 08:25:38 +0100
- Message-id: <20011213072550.WWRK1203.amsfep13-int.chello.nl@there>
A quick run down of the setup before I get to the problem:
- SuSE7.3 on AMD 1GHz, 256MB
- Using PMFirewall and masquerading turned on
- The local network is 2 NICs
- eth0 to the web
- eth1 to 192.168.0.1 (on local hub)
The local hub has only one other PC connected (with Win98). IP forwarding
works fine on this client system (using IP 192.168.0.2) - I can use the
internet etc from the client... so no problems there.
I installed VMWare Express a couple of days ago, and installed Win98 into it.
I config'ed it virtually the same as the working client, assigning it
192.168.0.3, and setting the gateway to 192.168.0.1. From VMWare (in a DOS
box) I can ping the host IP on eth1 at 192.168.0.1. I can ping from the host
to the VMWare client too. So, that tells me there is some sort of
communication happening there.
It fails though if I try to ping the IP of eth0, or any external web IP.
I have tried various things to track down the problem:
- disconnecting the working client, setting the IP to 192.168.0.2 (the
confirmed working IP from the working client) to check if I mistakenly set
the firewall to only masquerade the one IP. No difference, still get
timeouts on the VMware side if I try to ping the external world.
- set the VMWare ethernet to Host-only (suggested on the VMware newsgroup).
I get nothing then.... I cannot even ping the local network then. It only
works in Bridged mode.
Any ideas or suggestions here? What might have I missed?
Clayton
- SuSE7.3 on AMD 1GHz, 256MB
- Using PMFirewall and masquerading turned on
- The local network is 2 NICs
- eth0 to the web
- eth1 to 192.168.0.1 (on local hub)
The local hub has only one other PC connected (with Win98). IP forwarding
works fine on this client system (using IP 192.168.0.2) - I can use the
internet etc from the client... so no problems there.
I installed VMWare Express a couple of days ago, and installed Win98 into it.
I config'ed it virtually the same as the working client, assigning it
192.168.0.3, and setting the gateway to 192.168.0.1. From VMWare (in a DOS
box) I can ping the host IP on eth1 at 192.168.0.1. I can ping from the host
to the VMWare client too. So, that tells me there is some sort of
communication happening there.
It fails though if I try to ping the IP of eth0, or any external web IP.
I have tried various things to track down the problem:
- disconnecting the working client, setting the IP to 192.168.0.2 (the
confirmed working IP from the working client) to check if I mistakenly set
the firewall to only masquerade the one IP. No difference, still get
timeouts on the VMware side if I try to ping the external world.
- set the VMWare ethernet to Host-only (suggested on the VMware newsgroup).
I get nothing then.... I cannot even ping the local network then. It only
works in Bridged mode.
Any ideas or suggestions here? What might have I missed?
Clayton
| < Previous | Next > |