Date: Fri, 22 Jun 2001 14:35:16 -0600 (MDT) From: Brad Waite <brad@wcubed.net> To: Shoichi Sakane <sakane@kame.net> Cc: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Problems with IPsec tunnel Message-ID: <Pine.BSF.4.21.0106221430270.12719-100000@mail.datausa.com> In-Reply-To: <20010622210338P.sakane@kame.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Soichi, Thanks for the response. As it turns out, the problem my own stupidity - I forgot to turn on IP forwarding on one of the gateways. sysctl -w net.inet.ip.forwarding=1 fixed things right up. :) And since you're coming from KAME, maybe you can answer something else for me. Can you tell me if I will run into any problems running NAT on my gateways? Thanks, Brad On Fri, 22 Jun 2001, Shoichi Sakane wrote: > > I'm having quite the time trying to set up a IPsec tunnel on 4.3-RELEASE. > > Host-to-host IPsec works fine - I can make connections all day long between my > > two gateways. But for the life of me, I can't get my windows boxen on each end > > to talk to the other. I've got identical psk.txt files (rw-------) on both > > gateways, but 10.0.1.2 can't ping 10.0.0.2 to save its life. I've told the PCs > > on each end to route the other's traffic through the near gate's inside addr, > > and still no go. IP forwarding is turned on and NAT is off on both gates as > > well as an "OPEN" fw ruleset. I've gone through the couple of HOW-TOs on the > > net, but while I understand exactly what they're saying, and I repeat the > > process, I can't get it working. > > Did you see any message on your gateways or your hosts ? > I think debugging message of raccoon and system messages could be help you. > and tcpdump also can be help to know what happened your network. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0106221430270.12719-100000>