Michael,
Have you tried pinging the two machines prior to implementing the ipchains
configuration? It may not be an ipchains problem but some type of weird
network configuration error. Also, you will want to set up bind as a
caching DNS server most likely (that is what I did for my internal network).
What is the ip address of eth0 using DHCP? I have seen problems if eth0
ends up on the same subnet at eth1. In other words, if eht0 is
192.168.1.XXX (with XXX being from 1-254) I have seen weird errors with that
configuration.
I hope this helps.
steven westbrook
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael
Yuan
Sent: Wednesday, September 06, 2000 10:05 PM
To: [EMAIL PROTECTED]
Subject: IP MASQ problem
Hi Guys,
Me again! I still can not get my IP MASQ working and I could not figure
out why ...
My Linux is the gateway with two NICs (as many people have suggested)
eth0 is the DHCP one with the external IP;
eth1 is linked to the hub with an IP 192.168.1.1 (mask 255.255.255.0)
Win2000 is also connected with the hub and I configured it to have
IP: 192.168.1.2
MASK: 255.255.255.0
Gateway: 192.168.1.1
I ran the ipchain firewall script (copied and edited from IP-MASQ
How-TO) after Linux boot.
Linux can PING itself at both eth0 address and 192.168.1.1 but cannot PING
192.168.1.2 (the error is "Destination Host Unreachable")
Win2000 can PING itself at 192.168.1.2 but cannot PING 192.168.1.1 (the
error is "time out")
I did check the cable and individual NICs. They seem to work OK. And the
hub is brand new ... That just drove me crazy ...
Any suggestion would be highly appreciated!
Thanks a lot in advance!
Michael
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
