[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Connecting two seperate networks with OpenBSD
On Fri, 2002-06-07 at 13:50, Dan Sveen Olsen wrote:
> I think I have to explain some more. :) Each side has a GW. On the "outside"
> of that gateway, we have the NAT server. I.e the NAT server is connected to
> both the GWs on the "outside" of the networks. So when either side wants to
> communicate with the other side, they talk to the aliases. The packet gets
> routed through the GW since the destination isn't local, and onwards to the
> NAT server which has been configured with static arp entries for the
> aliases. We hoped the NAT server could be configured
Well with one NAT server (btw, I don't see why you don't NAT on both Gws
if they are OpenBSD boxen or put invisible NATing bridges ahead of
each), I think you should advice the customer to kick the ass of the
fscking network(s) architect(s) who came up with this. Somebody down the
food chain is really really clueless.
Man. Why people enjoy complexity so much ?
Saad -- [pgp keyid: 35592A6D http://pgp.mit.edu]
[pgp fingerprint: BF7D D73E 1FCF 4B4F AF63 65EB 34F1 DBBF 3559 2A6D]
# booth slave for hire