Linux Container Development
 help / color / mirror / Atom feed
From: Dilip Daya <dilip.daya-VXdhtT5mjnY@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Help! - kernel: ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready
Date: Mon, 07 Nov 2011 14:43:07 -0500	[thread overview]
Message-ID: <1320694987.2564.14.camel@pro6455b.example.com> (raw)

Please let me know if this is the correct list for a network-namespace
question:

Environment:
- v3.0.8 kernel (x86_64)
- One system with 2 network-namespaces (netns0 and netns1) configured
  with multiple physical NICs assigned.
- LTP-network tests performed between these two network namespaces,
  by entering netns1 (# ip netns exec netns1 bash), then executing 
  LTP-network tests between netns0 and netns1.

The following LTP tests produced: "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.e. network stack with "ip_local_deliver_finish: proto 108 isn't
netns-ready":

ICMP / UDP / TCP
IPv4
IPComp (mode: transport)
IPSec

=> Does this mean that IPComp (mode: transport) is not network namespace
   ready?  Is this a bug or IPComp is not netns enabled?  since IPv6
    works fine.

Thanking you all in advance.

-DilipD.

                 reply	other threads:[~2011-11-07 19:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1320694987.2564.14.camel@pro6455b.example.com \
    --to=dilip.daya-vxdhtt5mjny@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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