Date: Thu, 11 Jan 2007 23:31:26 +0100 From: Jeremie Le Hen <jeremie@le-hen.org> To: Vishal Patil <bsd.devil@gmail.com> Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: vpnc problem Message-ID: <20070111223126.GJ2616@obiwan.tataz.chchile.org> In-Reply-To: <eb7c8e2e0701031750o6bdb2076h6282b359a1a1a0c8@mail.gmail.com> References: <eb7c8e2e0701011241l624d7bbbp52329882c6efdf86@mail.gmail.com> <eb7c8e2e0701031750o6bdb2076h6282b359a1a1a0c8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Vishal,
First of all you should avoid cross-posting. Additionaly, I don't
think this is a question for -hackers@.
On Wed, Jan 03, 2007 at 08:50:26PM -0500, Vishal Patil wrote:
> I have found the answer to this question. I basically had to edit the
> vpnc-script and replace the body of the function "get_default_gw" with
>
> netstat -r -n | sed 's/default/0.0.0.0/' | grep '^0.0.0.0' | awk '{print
> $2}'
>
> So now I have vpnc-0.3.3 working on FreeBSD.
The port stands in security/vpnc, you should use it. It guess the
maintainer has tried it before updating the port and pushed the
appropriate patch into the ports tree.
Regards
--
Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070111223126.GJ2616>