From: Patrick McHardy <kaber@trash.net>
To: gerrit@erg.abdn.ac.uk
Cc: davem@davemloft.net, jmorris@namei.org, alan@lxorguk.ukuu.org.uk,
kuznet@ms2.inr.ac.ru, pekkas@netcore.fi, kaber@coreworks.de,
yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCHv2 2.6.18-rc4-mm3 3/3] net/ipv4: misc. support files
Date: Mon, 28 Aug 2006 20:28:46 +0200 [thread overview]
Message-ID: <44F335DE.5030307@trash.net> (raw)
In-Reply-To: <200608281910.50647@strip-the-willow>
gerrit@erg.abdn.ac.uk wrote:
> [Net/IPv4]: REVISED Miscellaneous changes which complete the
> v4 support for UDP-Lite.
>
> --- a/include/net/xfrm.h
> +++ b/include/net/xfrm.h
> @@ -467,6 +467,7 @@ u16 xfrm_flowi_sport(struct flowi *fl)
> switch(fl->proto) {
> case IPPROTO_TCP:
> case IPPROTO_UDP:
> + case IPPROTO_UDPLITE:
> case IPPROTO_SCTP:
> port = fl->fl_ip_sport;
> break;
> @@ -492,6 +493,7 @@ u16 xfrm_flowi_dport(struct flowi *fl)
> switch(fl->proto) {
> case IPPROTO_TCP:
> case IPPROTO_UDP:
> + case IPPROTO_UDPLITE:
> case IPPROTO_SCTP:
> port = fl->fl_ip_dport;
> break;
You also need to adapt _decode_session[46] in xfrm[46]_policy.c for
IPsec. While you're at it you might consider adjusting xt_tcpudp,
xt_multiport, ipt_LOG and ip6t_LOG as well to get some basic
netfilter support. I'm going to take care of connection tracking
and NAT once this is in mainline.
next prev parent reply other threads:[~2006-08-28 18:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 10:50 [RFC][PATCH 0/3] net: a lighter UDP-Lite (RFC 3828) gerrit
2006-08-28 10:59 ` gerrit
2006-08-28 12:48 ` Arnaldo Carvalho de Melo
2006-08-28 14:13 ` gerrit
2006-08-28 14:18 ` Arnaldo Carvalho de Melo
2006-08-28 18:10 ` [RFC][PATCHv2 2.6.18-rc4-mm3 1/3] net/ipv4: UDP-Lite extensions gerrit
2006-08-28 18:10 ` [RFC][PATCHv2 2.6.18-rc4-mm3 2/3] net/ipv4: UDP and generic UDP(-Lite) processing gerrit
2006-08-28 18:10 ` [RFC][PATCHv2 2.6.18-rc4-mm3 3/3] net/ipv4: misc. support files gerrit
2006-08-28 18:28 ` Patrick McHardy [this message]
2006-08-29 10:18 ` gerrit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F335DE.5030307@trash.net \
--to=kaber@trash.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=gerrit@erg.abdn.ac.uk \
--cc=jmorris@namei.org \
--cc=kaber@coreworks.de \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).