From: Charles Duffy (cduffy_at_spamcop.net)
Date: Wed Dec 25 2002 - 21:36:41 CET
Quoting "Stephen J. Bevan" <stephen_at_dino.dnsalias.com>:
> If both the user-level and kernel are
> reporting _kb3 then that can probably be ruled out. In that case, any
> chance you could try out your scenario with an older version of Super
> FreeS/WAN say, 1.99_kb2 or 1.99_kb1? If your scenario works with
> either of those then it would definitely point the finger at a bad
> NAT-T and selectors interaction. If your scenario still fails with
> _kb[12] then I'm off the hook :-)
Both kernel and userspace components agreed on kb3rc3 (equivalent to kb3 release
except in documentation, if I read my diffs correctly). Downgrading to _kb2
fixed the issue (though I'm still fighting a few other issues relating to
routing and virtual IP assignement, I'm fairly sure they're misconfiguration
issues on my part and hope to be able to power through them on my own).
Thanks!
_______________________________________________
Users mailing list
Users_at_lists.freeswan.org
http://lists.freeswan.org/mailman/listinfo/users
This archive was generated by hypermail 2.1.5 : Thu Dec 26 2002 - 05:21:13 CET