From: Dilip Daya <dilip.daya@hp.com>
To: linux-kernel@vger.kernel.org
Cc: ebiederm@xmission.com, jmorris@namei.org
Subject: ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready
Date: Wed, 09 Nov 2011 12:11:46 -0500 [thread overview]
Message-ID: <1320858706.2531.45.camel@pro6455b.example.com> (raw)
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?
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
-DilipD.
next reply other threads:[~2011-11-09 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 17:11 Dilip Daya [this message]
2011-11-09 22:38 ` ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready Eric W. Biederman
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=1320858706.2531.45.camel@pro6455b.example.com \
--to=dilip.daya@hp.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@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