I got it to work!
There were some addresses in the SA file (ipsec.conf) that were wrong, ie
192.168 vs. 192.186
Helluva nice error message, I was looking for a literal sending error.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mail
Yeah the whole GIF interface thing seemed weird to me too. I'm in much the
same situation I'm connecting to a Watchguard device, similar to the router
I guess you are hooking to.
I did get it to start trying to send, using the ping command. Never
thought I had to kick start the data going to it
Chris Benesch writes:
> Looking at the manual, it says to create a gif interface with the
> other end.
Are you referring to chapter 15.9 in the FreeBSD Handbook? I don't
know why it starts with tunneling over a GIF (IP-in-IP) interface.
Why don't you try a pure IPsec tunnel, instead? I assume y
2012/7/5 Andrew Thompson
> On 6 July 2012 04:43, Vyacheslav Kulikovskyy wrote:
> > 2012/7/4 Andrew Thompson
> >>
> >> On 4 July 2012 23:30, Vyacheslav Kulikovskyy
> wrote:
> >> > i have sever with two 1G links (em) aggregated by lagg0
> >> >
> >> > after 1700Megabits i have collisions/errors o
