Re: Kernel-native IPSec - no traceroute

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 22 June 2004 03:58, Herbert Xu wrote:
> Gavin Hamill <gdh@acentral.co.uk> wrote:
> >> > Does this make sense to anyone?
>
> What's happening is that the TTL is being copied as is by the IPsec
> encapsulation.  With the KLIPS implementation, the TTL on the outside
> is set to a default value after encapsulation.

OK that makes sense.. The next question, as I'm sure you expected, is "How can 
I fix this?"

There appears to be precious little information on the web for the 
kernel-native IPSec (certainly when you compare it to the wealth of 
FreeS/WAN / KLIPS specific material) so any extra 'HOWTO' info stored 
publically must surely benefit many others! :)

Cheers,
Gavin.
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux