Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Issue\s+on\s+packets\s+sending\s+through\s+ip_route_output_key\(\)\s+to\s+xfrm_lookup\(\)\s+in\s+native\s+IPsec\s*$/: 4 ]

Total 4 documents matching your query.

1. ion cleanup + fixes (score: 1)

Author: jamal <hadi@xxxxxxxxxx>

Date: Thu, 30 Dec 2004 20:51:06 -0800 (PST)

sons (i hope i am not offending anyone)]. Ok, sounds like a good plan (gives me more time to work with the driver stuff which is getting out of control ;->): I

/archives/netdev/2004-12/msg00908.html (8,639 bytes)

2. in U32 classifier. (score: 1)

Author: di@xxxxxxxxxx>

Date: Thu, 30 Dec 2004 21:07:09 -0800 (PST)

t teaching tc to stash something there that it understands on how to translate. Thinking about it now, this may not be sufficient: perhaps we need a few bits i

/archives/netdev/2004-12/msg00910.html (8,627 bytes)

3. Issue on packets sending through ip_route_output_key() to xfrm_lookup() in native IPsec (score: 1)

Author: Park Lee <parklee_sel@xxxxxxxxx>

Date: Thu, 30 Dec 2004 20:51:06 -0800 (PST)

Hi, In Linux native IPsec, there is a function xfrm_lookup(struct dst_entry **dst_p, struct flowi *fl, struct sock *sk, int flags) (in /usr/src/linux-2.6.5-1.358/net/xfrm/xfrm_policy.c). Whenever a p

/archives/netdev/2004-12/msg01859.html (8,654 bytes)

4. Issue on packets sending through ip_route_output_key() to xfrm_lookup() in native IPsec (score: 1)

Author: Park Lee <parklee_sel@xxxxxxxxx>

Date: Thu, 30 Dec 2004 21:07:09 -0800 (PST)

Hi, In Linux native IPsec, there is a function xfrm_lookup(struct dst_entry **dst_p, struct flowi *fl, struct sock *sk, int flags) (in /usr/src/linux-2.6.5-1.358/net/xfrm/xfrm_policy.c). Whenever a p

/archives/netdev/2004-12/msg01861.html (8,642 bytes)

Current List: 1 - 4
Page: [1]