Re: IPSec in 4.0-current questions..
> >I've been messing about with IPSEC in 4.0-current, and have observed some > >unexpected behavior. Is there someone I can swap some email with off > >the list to determine if what I'm seeing is a bug, or I'm just confused? > >It has to do with security policy specifications and what SAID is being > >selected when a TCP connection is being opened. > > could you try sending details to [EMAIL PROTECTED] (KAME users > mailing list, you may want to subscribe it - see www.kam.enet). There might be also a possibility of freebsd specific problem, and also, usual freebsd users might also wish to know the issue. How about cross posting [EMAIL PROTECTED] and freebsd-security ? Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPSec in 4.0-current questions..
>I've been messing about with IPSEC in 4.0-current, and have observed some >unexpected behavior. Is there someone I can swap some email with off >the list to determine if what I'm seeing is a bug, or I'm just confused? >It has to do with security policy specifications and what SAID is being >selected when a TCP connection is being opened. could you try sending details to [EMAIL PROTECTED] (KAME users mailing list, you may want to subscribe it - see www.kam.enet). itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IPSec in 4.0-current questions..
I've been messing about with IPSEC in 4.0-current, and have observed some unexpected behavior. Is there someone I can swap some email with off the list to determine if what I'm seeing is a bug, or I'm just confused? It has to do with security policy specifications and what SAID is being selected when a TCP connection is being opened. Thanks! louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
