Date: Tue, 28 Oct 2003 16:25:48 -0700 From: "Brent Wiese" <brently@bjwcs.com> To: "'Micheal Patterson'" <micheal@tsgincorporated.com>, <freebsd-questions@freebsd.org> Subject: RE: IPSEC tunnel issue.. Message-ID: <20031028232154.XGJZ2935.fed1mtao01.cox.net@SAMBA>
next in thread | raw e-mail | index | archive | help
> Here's my situation. > > I've got 2 networks at different facilities that are using > public routable > IP's. Each end has a fbsd box in bridge mode as their > firewall between the > lan and the cisco routers at each end. I've been tasked to establish a > secure tunnel between these two networks and I'm having some > trouble. I've > searched google for ipsec information on this but every thing > that I have > found depicts a private lan behind the public ip's of the > tunnel endpoints. > Has anyone been able to establish this type of tunnel > successfully? If so, > can you please direct me to some information on this? So if I understand correctly, you're running the FreeBSD firewall in "transparent" mode? Hosts behind the firewall use public addresses on the same subnet as the firewall public? I think you may need to switch to NAT mode so you're running a non-net-routeable (private) LAN. You can always stack more public Ips on the firewall and port forward. Or, if you run a routing daemon and have all your hosts point to it as the default gateway, build the tunnel and route anything that isn't through the tunnel at your real gateway. Or, build the tunnel and add routes to all the hosts specifing the FreeBSD box as the gateway for the remote network. This can be a pain to admin long term, but if, for instance, you run a Windows domain, you can run a "route add" batch file when users log into the network. Brent
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031028232154.XGJZ2935.fed1mtao01.cox.net>