Re: Kernel-native IPSec - no traceroute

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

 



On Tue, Jun 22, 2004 at 05:16:38PM -0700, David S. Miller wrote:
> 
> > In any case, RFC2401 section 5.1.2 requires that the TTL in the outer
> > header be independent of that in the inner header.  So we may even
> > need to change the default setting to comply.
> 
> The IPIP tunnel driver allows the user to specify a specific TTL,
> and if none specified we use the inner IPH TTL.  Perhaps instead,
> the backup logic should use the route's TTL and that logic copied over
> to xfrm4_tunnel.c
> 
> What do you think?

I agree.  But before we code that, it would be good to merge the
tunnel code from ah4/esp4/ipcomp so that we don't have to do such
changes three times.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email:  Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
: 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