In this blog, we gonna learn how network namespaces works.<\/p>\n
First off, install openvswitch in your Ubuntu<\/p>\n
Now let us create a namespace<\/p>\n You can seen these new namespaces created at<\/p>\n In order to see the ip link at each namespaces<\/p>\n Similar will be the case with the blue namespace<\/p>\n In order the red to communicate with blue namespace, they needs to connected via virtual switch. For this we use OVS. First OpenSwitch<\/strong><\/p>\n This will create a bridge named OVS1 with a default interface OVS1<\/p>\n Next to show the virtual switch<\/p>\n Now in the root namespace or in the host if you issue “ip link” command you will see the interface OVS1 added<\/p>\n We have red, blue and OVS1 namespaces and now lets connect altogether, for this we veth interfaces. Veth acts like a pipe connecting Now to add the other end to OVS issue the command<\/p>\n The veth-r will be now in OVS1 switch<\/p>\n Let us repeat the entire steps for the blue namespace as well<\/p>\n Now the network is set, but all the links are down and without an IP to communicate. So let’s follow the below steps<\/p>\n Similar for blue<\/p>\n Instead of using Now try pinging<\/p>\n If you are going with Linux Bridge follow the below steps<\/strong><\/p>\n ip link add linbr-0 type bridge<\/p>\n In this blog, we gonna learn how network namespaces works. First off, install openvswitch in your Ubuntu apt-get update apt-get install openvswitch-switch Now let us<\/p>\n","protected":false},"author":3,"featured_media":5026,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[6],"tags":[],"class_list":["post-4706","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux"],"acf":[],"yoast_head":"\napt-get update<\/code>
\napt-get install openvswitch-switch<\/code><\/p>\nip netns add red <\/code>
\nip netns add blue <\/code><\/p>\nls \/var\/run\/netns
\nred blue <\/code><\/p>\n ip netns exec red ip link <\/code><\/p>\n1: lo: mtu 65536 qdisc noop state DOWN mode DEFAULT group default qlen 1000
\nlink\/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 <\/code><\/p>\n
\nWe will first create a virtual bridge using Openswitch <\/strong> or Linux Bridge<\/strong> We will show both ways here.<\/p>\n ovs-vsctl add-br OVS1<\/code><\/p>\n ovs-vsctl show <\/code>
\n cf8eb0c9-306c-47ee-8149-a6caa10584ed
\nBridge OVS1
\nPort OVS1
\nInterface OVS1
\ntype: internal
\novs_version: \"2.13.8\" <\/code><\/p>\nip link<\/code><\/p>\n
\nthese namespaces<\/p>\nip link add eth0-r type veth peer name veth-r<\/code>
\nWe will connect eth0-r in red namespace and veth-r in OVS1 namespace<\/p>\nip link set eth0-r netns red <\/code>
\nNow you no longer can see eth0-r in host or root namespace but it can be seen in the “red namespace” You can verify this by
\n“ip netns exec red ip link”<\/p>\novs-vsctl add-port OVS1 veth-r <\/code><\/p>\nip link set dev veth-r up<\/code> #This is important<\/p>\novs-vsctl show<\/code>
\ncf8eb0c9-306c-47ee-8149-a6caa10584ed
\nBridge OVS1
\nPort OVS1
\nInterface OVS1
\ntype: internal
\nPort veth-r
\nInterface veth-r
\novs_version: \"2.13.8\"<\/code><\/p>\nip link add eth0-b type veth peer name veth-b<\/code>
\nip link set eth0-b netns blue <\/code>
\novs-vsctl add-port OVS1 veth-b<\/code><\/p>\nip link set dev veth-b up #This is important<\/code><\/p>\nip netns exec red ip link set dev lo up<\/code>
\nip netns exec red ip link set dev eth0-r up<\/code>
\nip netns exec red ip address add 10.0.0.1\/24 dev eth0-r<\/code><\/p>\nip netns exec blue ip link set dev lo up<\/code>
\nip netns exec blue ip link set dev eth0-b up<\/code>
\nip netns exec blue ip address add 10.0.0.2\/24 dev eth0-b<\/code><\/p>\nip netns exec blue\/red<\/code> We can directly enter the namespace of each by<\/p>\nip netns exec blue\/red bash<\/code> and execute the ip link<\/code> commands directly. You can type “exit” to get out of that
\nparticular namespace.<\/p>\n ip link add veth-red type veth peer name veth-red-br
\nip link add veth-green type veth peer name veth-green-br
\nip link set veth-red netns red
\nip link set veth-red-br master linbr-0
\nip link set veth-green netns green
\nip link set veth-green-br master linbr-0
\nip -n red addr add 10.0.0.1\/24 dev veth-red
\nip -n green addr add 10.0.0.2\/24 dev veth-green
\nip -n red link set veth-red up
\nip link set veth-red-br up
\nip -n green link set veth-green up
\nip link set veth-green-br up
\nip addr add 10.0.0.10\/24 dev linbr-0
\nip netns exec red bash
\nping 10.0.0.2 <\/code><\/p>\n","protected":false},"excerpt":{"rendered":"