Skip to content

netns: add linux-vrf features via network namespaces

Vivien Chappelier containers 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest6 patches 13 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6netns: add in ida ID to identify the network namespaceinclude/net/net_namespace.h net/core/net_namespace.c+26 -00 replies
2/6netns: export nets id to /proc/net/netnsnet/core/net_namespace.c+50 -00 replies
3/6add get_net_ns_by_id() to get a reference to a network namespace from its nsid.include/net/net_namespace.h net/core/net_namespace.c+43 -30 replies
4/6add SO_NSID and SO_NETNS socket optionsarch/alpha/include/asm/socket.h arch/arm/include/asm/socket.h arch/avr32/include/asm/socket.h +17 more+122 -11 reply
5/6netlink: add IFLA_NET_NS to move interface to network namespace by nsidinclude/linux/if_link.h net/core/rtnetlink.c+17 -00 replies
6/6netns: configurable number of initial network namespacesnet/Kconfig net/core/net_namespace.c+25 -10 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/6] netns: add linux-vrf features via network namespaces

Hi,

The recently introduced network namespaces allow separate standalone
network stacks to coexist on the same machine. This is a very useful functionality that we have been needing and using in our products for some time, through the VRF ptchset (http://linux-vrf.sourceforge.net/). The goal of the VRF patchset and network namespaces are very similar, yet some features of the VRF are missing that these patches intend to provide.

The network namespaces are currently tied to a process, and
referenced by its pid. However, a networking stack has no particular reason to be associated with any process and it should be possible to use and setup additional networking stacks without the need to clone() or unshare(). The initial version of the "Coexist with the sysfs limitations" patches by Benjamin Thery introduced the notion of a unique network namespace identifier (nsid) that is perfectly fit for the purpose of referencing networking stacks independently of any process. The first two patches of his set are therefore reused here to identify networking stacks.

These patches additionally introduce the following features that
were initially provided by the VRF patchset:
- the ability to move a socket to a different network namespace, through the new SO_NSID setsockopt(), given the nsid
- the ability to move a process to an existing network namespace, through the new SO_NETNS setsockopt(), given the nsid
- the ability to move an interface to a different namespace by nsid instead of pid
- the ability to create additional network namespaces on startup (dynamic addition/deletion is not supported but should be easy to add)

To test those features, the chvrf tools attached in this mail have
been ported to the new setsockopt() API. Example usage:

$ chnetns 1 /bin/sh   # This will attach a shell to existing network namespace 1
$ port -n 1 -p 3434   # This will open a listening socket on port 3434 of network namespace 1

Also attached is a patch to iproute2 to add the ability to move an
interface to a different namespace by nsid, used this way:

$ ip link set eth0 nsid 1    # This will move eth0 to network namespace 1

The patches should apply cleanly to net-next-2.6, version 2.6.28-rc2,
commit 3891845e1ef6e6807075d4241966b26f6ecb0a5c.

I would be glad to have your impressions and comments on these
patches, and to have them merged upstream once everybody is satisfied with them.

regards,
Vivien Chappelier.

From 698eb7aeb60baca7fc7f0fda9080174c96f92e02 Mon Sep 17 00:00:00 2001
From: Vivien Chappelier <[email protected]>
Date: Tue, 28 Oct 2008 18:06:13 +0100
Subject: [PATCH] Add support for testing IFLA_NET_NS

---
 include/linux/if_link.h |    2 ++
 ip/iplink.c             |    9 +++++++++
 misc/Makefile           |    2 +-
 3 files changed, 12 insertions(+), 1 deletions(-)
include/linux/if_link.h +2 -0
index c948395..fab393d 100644
@@ -79,6 +79,8 @@ enum
 	IFLA_LINKINFO,
 #define IFLA_LINKINFO IFLA_LINKINFO
 	IFLA_NET_NS_PID,
+	IFLA_IFALIAS,
+	IFLA_NET_NS,
 	__IFLA_MAX
 };
 
ip/iplink.c +9 -0
index fd23db1..ffb0d39 100644
@@ -67,6 +67,7 @@ void iplink_usage(void)
 	fprintf(stderr, "	                  [ broadcast LLADDR ]\n");
 	fprintf(stderr, "	                  [ mtu MTU ]\n");
 	fprintf(stderr, "	                  [ netns PID ]\n");
+	fprintf(stderr, "	                  [ nsid NSID ]\n");
 	fprintf(stderr, "       ip link show [ DEVICE ]\n");
 
 	if (iplink_have_newlink()) {
@@ -179,6 +180,7 @@ int iplink_parse(int argc, char **argv, struct iplink_req *req,
 	char abuf[32];
 	int qlen = -1;
 	int mtu = -1;
+	int net = -1;
 	int netns = -1;
 
 	ret = argc;
@@ -228,6 +230,13 @@ int iplink_parse(int argc, char **argv, struct iplink_req *req,
                         if (get_integer(&netns, *argv, 0))
                                 invarg("Invalid \"netns\" value\n", *argv);
                         addattr_l(&req->n, sizeof(*req), IFLA_NET_NS_PID, &netns, 4);
+		} else if (strcmp(*argv, "nsid") == 0) {
+                        NEXT_ARG();
+                        if (net != -1)
+                                duparg("nsid", *argv);
+                        if (get_integer(&net, *argv, 0))
+                                invarg("Invalid \"nsid\" value\n", *argv);
+                        addattr_l(&req->n, sizeof(*req), IFLA_NET_NS, &net, 4);
 		} else if (strcmp(*argv, "multicast") == 0) {
 			NEXT_ARG();
 			req->i.ifi_change |= IFF_MULTICAST;
misc/Makefile +1 -1
index 8c25381..a4c9591 100644
@@ -1,7 +1,7 @@
 SSOBJ=ss.o ssfilter.o
 LNSTATOBJ=lnstat.o lnstat_util.o
 
-TARGETS=ss nstat ifstat rtacct arpd lnstat
+TARGETS=ss nstat ifstat rtacct lnstat
 
 include ../Config
 
Signature · 1 line
1.5.4.4

_______________________________________________
Containers mailing list Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linux-foundation.org/mailman/listinfo/containers