Re: About NAT Traversal

2007-02-01 Thread Eric W. Bates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 VANHULLEBUS Yvan wrote: > On Thu, Feb 01, 2007 at 11:46:49AM -0500, Eric W. Bates wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> ashoke saha wrote: >>> basic kame (racoon) as NAT_T for IKE. It did not have >>> kernel support till 6.0.

Re: About NAT Traversal

2007-02-01 Thread VANHULLEBUS Yvan
On Thu, Feb 01, 2007 at 11:46:49AM -0500, Eric W. Bates wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > ashoke saha wrote: > > basic kame (racoon) as NAT_T for IKE. It did not have > > kernel support till 6.0. you can take the patch from > > there. > > also NAT_T has moved from draft

Re: About NAT Traversal

2007-02-01 Thread Eric W. Bates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ashoke saha wrote: > basic kame (racoon) as NAT_T for IKE. It did not have > kernel support till 6.0. you can take the patch from > there. > also NAT_T has moved from draft to RFC and do google > for NAT_T to get get the RFC's and also read the code

Re: About NAT Traversal

2007-01-26 Thread ashoke saha
basic kame (racoon) as NAT_T for IKE. It did not have kernel support till 6.0. you can take the patch from there. also NAT_T has moved from draft to RFC and do google for NAT_T to get get the RFC's and also read the code in the kernel patch and racoon. assuming you are talking about ipsec NAT_T.

Re: About NAT Traversal

2007-01-26 Thread Darren Pilgrim
Eric W. Bates wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Can someone please refer me to some documentation describing how to implement NAT Traversal? In what context? The methods required to traverse a NAT are highly protocol-specific. -- Darren Pilgrim __

About NAT Traversal

2007-01-26 Thread Eric W. Bates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Can someone please refer me to some documentation describing how to implement NAT Traversal? - -- Eric W. Bates [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.