[lkml]   [2006]   [Dec]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[patch 11/24] XFRM: Use output device disable_xfrm for forwarded packets
    2.6.18-stable review patch.  If anyone has any objections, please let us know.

    From: David Miller <>

    Currently the behaviour of disable_xfrm is inconsistent between
    locally generated and forwarded packets. For locally generated
    packets disable_xfrm disables the policy lookup if it is set on
    the output device, for forwarded traffic however it looks at the
    input device. This makes it impossible to disable xfrm on all
    devices but a dummy device and use normal routing to direct
    traffic to that device.

    Always use the output device when checking disable_xfrm.

    Signed-off-by: Patrick McHardy <>
    Signed-off-by: David S. Miller <>
    Signed-off-by: Chris Wright <>
    commit 9be2b4e36fb04bbc968693ef95a75acc17cf2931
    Author: Patrick McHardy <>
    Date: Mon Dec 4 19:59:00 2006 -0800

    net/ipv4/route.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    --- linux-
    +++ linux-
    @@ -1775,7 +1775,7 @@ static inline int __mkroute_input(struct
    if (in_dev->cnf.no_policy)
    rth->u.dst.flags |= DST_NOPOLICY;
    - if (in_dev->cnf.no_xfrm)
    + if (out_dev->cnf.no_xfrm)
    rth->u.dst.flags |= DST_NOXFRM;
    rth->fl.fl4_dst = daddr;
    rth->rt_dst = daddr;
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-12-15 03:05    [W:0.020 / U:19.400 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site