All of lore.kernel.org
 help / color / mirror / Atom feed
* Help! - kernel: ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready
@ 2011-11-07 19:43 Dilip Daya
  0 siblings, 0 replies; only message in thread
From: Dilip Daya @ 2011-11-07 19:43 UTC (permalink / raw)
  To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA

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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2011-11-07 19:43 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-07 19:43 Help! - kernel: ip_local_deliver_finish: proto 108 (IPComp) isn't netns-ready Dilip Daya

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.