On Fri, 5 Jun 1998, Michael Zaniboni wrote:
> Date: Fri, 5 Jun 1998 15:34:47 +0200 (MET DST)
> From: Michael Zaniboni <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: [masq] ip-masq misses rest of net
>
> Hi,
>
> IP-Masq just won't connect another box properly to the net.
>
> Here my boxes setup:
>
> Win-Box A---------------Linux-Box B (LAN)
> 192.168.1.2 | 192.168.1.3
> |
> |
> Router C
> 192.168.1.3
> |
> |
> |
> WWW-Server D----------------DNS-Box E (another network)
> 193.100.1.1 193.100.1.2
> |
> |
> Firewall F
> |
> |
> |
> Internet and rest of the world
>
> And here the problem:
>
> Win-Box A can use WWW-Server D (both IP-address and www-adress work) while
> Linux-Box B is up (only then), but can't get to another address (e.g.
> 194.x or www.yahoo.com).
> IP-Masq seems to work somehow because Win-Box A only can use WWW-Server D
> when Linux-Box B is up and IPFWADM is running (above commands).
> What do I miss here, or does the Firewall F just doesn't like my IP-Masq?
From the topology of your network, it would appear that you should
setup your win-a box to use router-c instead of linux-b as it's gateway.
Logically, they are on the same network. And from the diagram you
provided, they appear to be on the same physical network. And if that is
the case, then there should be no reason to use linux-b as the gateway for
win-a.
Also, router-c and linux-b share the same IP, which is not
possible if they share the same physical network. But I would assume that
this is a typo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
