From: ebiederm@xmission.com (Eric W. Biederman)
To: dilip.daya@hp.com
Cc: linux-kernel@vger.kernel.org, jmorris@namei.org,
<netdev@vger.kernel.org>,
adobrian@gmail.com
Subject: Re: ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready
Date: Wed, 09 Nov 2011 14:38:16 -0800 [thread overview]
Message-ID: <m1d3d0oraf.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1320858706.2531.45.camel@pro6455b.example.com> (Dilip Daya's message of "Wed, 09 Nov 2011 12:11:46 -0500")
Dilip Daya <dilip.daya@hp.com> writes:
> Hi All,
>
> LTP-network tests produced:
>
> "ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready"
>
> Question:
> Is the above a bug or feature (IPComp, mode: transport) not netns
> enabled?
I would call it a missing feature.
> Environment:
>
> * v3.1-stable kernel.
>
> * Configured two network-namespaces via "ip netns add ...".
> on a single system: netns0 (assigned as server) and
> netns1 (assigned as client).
> - assigned multiple physical NICs to netns0 and netns1.
>
> * Entered netns1 (ip netns exec netns1 bash) to execute
> ltp-network suite of tests between netns1 and netns0.
>
> * The following LTP tests produced messages:
>
> "kernel: ip_local_deliver_finish: proto 108 isn't netns-ready"
>
> - /usr/lib/ltp/testcases/bin/icmp4-multi-diffip06
> - /usr/lib/ltp/testcases/bin/tcp4-multi-diffip13
> - /usr/lib/ltp/testcases/bin/udp4-multi-diffip06
> - /usr/lib/ltp/testcases/bin/udp4-multi-diffnic06
> - /usr/lib/ltp/testcases/bin/udp4-multi-diffport06
>
> * I also noticed missing ".netns_ok = 1" in:
> - http://lxr.linux.no/linux+v3.1/net/ipv4/ipcomp.c#L150
The .netns_ok flag indicates that someone has audited the code and made
certain it all works with network namespaces.
Skimming the code I don't see anything that jumps out as me as
wrong. And it looks like Alexy did the work in Jan of 2010.
commit a92df2545402c1a08e7a158f4477a52dea0eeeed
Author: Alexey Dobriyan <adobriyan@gmail.com>
Date: Mon Jan 25 10:38:34 2010 +0000
netns xfrm: ipcomp support
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
However it is clear that no one has actually tested ipcomp with
network namespaces.
If you have a clue what is going on with ip compression my
recommendation would be to add .netns_ok = 1. Verify that the
everything works and send the patch. You probably want to
verify and test ipv6 as well. It really looks like the code
is fine and it just needs to be enabled.
Eric
next prev parent reply other threads:[~2011-11-09 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 17:11 ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready Dilip Daya
2011-11-09 22:38 ` Eric W. Biederman [this message]
2011-11-16 15:01 ` Dilip Daya
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=m1d3d0oraf.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=adobrian@gmail.com \
--cc=dilip.daya@hp.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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