Host-Only Networking Woes
Adrian B.
within my virtual machine running win98. I basically followed the guide
found at http://www.vmware.com/support/reference/linux/ipmasq_linux.html
I have one network card connected to a cable modem and thus my
ISP. This is bound to an IP at boot time by dhcp. There's also a
virtual interface vmware sets up, listed as:
eth0 Link encap:Ethernet HWaddr 00:E0:29:65:77:CD
inet addr:144.132.17.59 Bcast:144.132.31.255
Mask:255.255.240.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13574 errors:0 dropped:0 overruns:0 frame:0
TX packets:12361 errors:0 dropped:0 overruns:0 carrier:0
collisions:129 txqueuelen:100
RX bytes:9069917 (8.6 Mb) TX bytes:1277797 (1.2 Mb)
Interrupt:11 Base address:0xd800
vmnet1 Link encap:Ethernet HWaddr 00:50:56:01:00:00
inet addr:172.16.221.1 Bcast:172.16.221.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:72 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Now, Ive looked through other people's questions about host-only
networking and havent seen an address like 172.x.x.x reported. 172.x
doesnt seem really "right" to me, as most people have
192.168.x. Nevertheless it was the address recommended when I installed
vmware, so I pushed on.
Ive got lines in /etc/hosts like:
127.0.0.1 localhost
# For a dummy network device
192.168.1.42 ailsa.dummydomain.com Ailsa
# Used for reverse DNS on my incoming ppp line
10.0.0.1 dup1.dummydomain.com dup1
# Added for vmware networking
10.0.1.1 gateway.linuxbogus.com gateway
172.16.221.1 win98.linuxbogus.com win98
Then I run:
echo 1 > /proc/sys/net/ipv4/ip_forward
ipchains -F
ipchains -X
ipchains -P forward DENY
ipchains -A forward -s 172.16.221.1/24 -j MASQ
Lastly, I more or less run through what the vmware docs state and just
replace their IPs with mine, as follows:
Windows 95 or Windows 98
Go to Control Panel > Network.
In the TCP/IP properties dialog, go to IP Address and set the IP
addresses as follows:
172.16.221.1/254 for host-only networking
Subnet Mask:255.255.255.0
In the Gateway section, enter the following:
Gateway: 10.0.1.1
In the DNS Section, enter the same DNS entries your original host
uses. So if the DNS server on the host is 205.178.44.3, that's the
IP you want inside your virtual machine as well.
My DNS server is 61.9.128.13, but Im not sure what to enter in the
"Host" and "Domain" fields.
Well, after all that it still doesnt work. When windows starts up and
is attempting to connect to web sites etc, I get loads of
martian packet reports in /var/log/messages:
Mar 6 15:50:55 ailsa kernel: martian source 01dd10ac for 01dd10ac, dev
vmnet1
Mar 6 15:50:55 ailsa kernel: ll header: ff ff ff ff ff ff 00 50 56 d9
36 3c 08 06
Any clue what's wrong?
Bob G
"Adrian B." <midn...@bigpond.net.au> wrote in message
news:3AA46D99...@bigpond.net.au...
> [...]
>
> In the Gateway section, enter the following:
>
> Gateway: 10.0.1.1
Use your Linux host's INTERNAL IP address for vmnet1 (172.16.221.1 ) as your
gateway and set up the guest with it's OWN UNIQUE IP on that same subnet
(ie. 172.16.221.2 mask 255.255.255.0). Think of each guest as a UNIQUE
computer plugged into the vmnet1 'hub' with the host as your router/gateway
out. The same rules apply.
> In the DNS Section, enter the same DNS entries your original host
> uses. So if the DNS server on the host is 205.178.44.3, that's the
> IP you want inside your virtual machine as well.
>
> My DNS server is 61.9.128.13, but Im not sure what to enter in the
> "Host" and "Domain" fields.
Those host and domain fields aren't overly critical. In the Domain field,
use whatever your ISP used (if anything) (ie. theirdomain.com). Whatever
settings work under the Linux host for the domain should work OK on the
guest. The hostname should normally be unique within a domain, but the guest
won't be visible externally anyhow. I'd just use whatever you call the guest
there.
The DNS server settings ARE important, and should match the host's settings.
That doc page actually does show how to do it, but the details can be
confusing if you're new to it all. Try those settings and see how it works.
Once it works, re-read that page and make some notes for next time.
Good luck!
- Bob
Adrian B.
everything :-) Now onto getting Samba going...
Bosmarmot
This still doesn't work for me
I've did everything you said, but, It still doesn't work
I've taken the vmnet1-nr as my gateway (172.16.40.128) and gave the guest an ip in that range
(172.16.40.129). DNS - server : I took the hosts-ipnr (172.16.40.128)
And, still it doesn't work :((
I can't even make a 'ping 172.16.40.128' a succes.
What am I still doing wrong ?
Thx in advance
In article <9820uf$6h0$1...@london.vmware.com>, "Bob G"
Bob G
"Bosmarmot" <Bosm...@het.grote.bos.com> wrote in message
news:20010307.1...@bitcruiser.localdomain...
> [...]
> This still doesn't work for me
> I've did everything you said, but, It still doesn't work
OK, we need the usual:
Info on host and guest (OS, versions etc.)
Output of routing tables (netstat -rn Unicen or route print for Windows)
Interface configurations (ifconfig for Unicen or ipconfig /all for Windows)
A few hints as to what you're trying to accomplish.
"It still doesn't work" leaves much to the imagination. "Well, fix what's
wrong" is about the most assistance you can expect for that! :)
- Bob