Topic: IP-Masquerade Control for Local Interface

[Kevin Kimmell]

Is there a way to tell the esmith gateway to NOT Masquerade packets that stay on the local net? For example, I've got a router on the "fake" network that connect to an offsite office. I've already added that office's network as a local network. The problem occurs when NETBIOS type things try to communcate from their end to mine. The packets get to the intended client on my side of the router, the responses go to the e-smith machine which sees that it needs to forward the packets to the router, but it is tagging it with its own "fake" ip address rather than just passing the actual client's IP.

Any help appreciated.

Kevin

[Charlie Brady]

Kevin Kimmell wrote:

> Is there a way to tell the esmith gateway to NOT Masquerade
> packets that stay on the local net? For example, I've got a
> router on the "fake" network that connect to an offsite
> office. I've already added that office's network as a local
> network. The problem occurs when NETBIOS type things try to
> communcate from their end to mine. The packets get to the
> intended client on my side of the router, the responses go to
> the e-smith machine which sees that it needs to forward the
> packets to the router, but it is tagging it with its own
> "fake" ip address rather than just passing the actual
> client's IP.

Your client machines need to have a specific network route so that they use the router for the remote network, not the e-smith server (which is the default route).

Charlie

[Kevin Kimmell]

So I do have to put a persistent route on every single client? There's no way to configure an IP-MASQ machine to not masq local nets?

Thanks,

Kevin