{"id":5256,"date":"2025-02-28T06:34:26","date_gmt":"2025-02-28T06:34:26","guid":{"rendered":"https:\/\/www.liainfraservices.com\/blog\/?p=5256"},"modified":"2025-04-05T18:25:51","modified_gmt":"2025-04-05T18:25:51","slug":"how-to-create-and-manage-network-namespaces-in-a-linux-using-netns","status":"publish","type":"post","link":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/","title":{"rendered":"What is Network Namespace in Linux?"},"content":{"rendered":"<\/span> 8<\/span> min read<\/span><\/span>
<\/span> 3,072<\/span><\/div>\n

Understanding Network Interfaces in Linux<\/strong><\/p>\n\n\n\n

Onboard & PCI slot<\/p>\n\n\n\n

         Onboard: When the interface is integrated directly into motherboard<\/p>\n\n\n\n

         PCI: Its an external card integrated into motherboard<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The ethernet names are changed, During physical days, we used eth0, eth1 as a name for ethernet card and the link name<\/p>\n\n\n\n

But, due to virtualization, now even the links names are changed based on types of interface & Physical topology<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Based on Types of Interfaces<\/strong>:<\/span><\/p>\n\n\n\n

Ex: Ethernet interface begins with en<\/code><\/p>\n\n\n\n

WLAN interface begins with wl<\/code><\/p>\n\n\n\n

WWAN interface begins with ww<\/code><\/p>\n\n\n\n

Based on Physical Topology<\/strong>:<\/span><\/p>\n\n\n\n

If there is \u201coN<\/code><\/strong>\u201d \u2013 Its an (o)onboard<\/code> card & (N<\/code>): Number of Device<\/p>\n\n\n\n

         : ex: eno1 \u2013 Its an onboarded Ethernet and its on Device 1, means on 1st<\/sup> slot<\/p>\n\n\n\n

If there is \u201csN<\/code><\/strong>\u201d –  s: It\u2019s a PCI pluggable device.<\/p>\n\n\n\n

         : ex: ens4 : PCI slotted Ethernet card and its on 4th<\/sup> sloth or 4th<\/sup> device.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

To list the interfaces attached to a server: ip link<\/code><\/p>\n\n\n\n

To check if there is any IP attached to these interface : ip a show <\/code> [ ip address show]<\/p>\n\n\n\n

To see the info about a specific interface :ip link show ens4<\/code><\/p>\n\n\n\n

To know the traffic pass through that interface: (Check the stats -s) : ip -s link show ens4<\/kbd><\/code> [ Very important command for real life troubleshooting]<\/em><\/p>\n\n\n\n

: it has these metrices like<\/p>\n\n\n\n

TX<\/code>: no of packet transmitted out<\/p>\n\n\n\n

RX<\/code>: no of packet Received<\/p>\n\n\n\n

Error\/drop<\/code>: these shows how many packets are dropped etc<\/p>\n\n\n\n

To check if the host can communicate with other host on different network<\/p>\n\n\n\n

    \n
  • For that we need to check the host route table : route -n<\/code><\/li>\n<\/ul>\n\n\n\n

    o   This gives the info, about the gateway through which the traffic would pass through<\/p>\n\n\n\n

      \n
    • If there is no route, we have to add the route<\/li>\n<\/ul>\n\n\n\n

      o   ip route add destination_network via router_gateway<\/code><\/p>\n\n\n\n

        \n
      • Ex: Host IP: 192.168.1.4 wants to communicate with host 192.168.5.4<\/li>\n<\/ul>\n\n\n\n

        o   ip route add 192.168.5.0\/24 via 192.168.1.0<\/code><\/p>\n\n\n\n

        o   ip route add default via 192.168.1.0<\/code> # Default is same as 0.0.0.0(Internet)<\/p>\n\n\n\n

        Host wants to connect to another host, but is unable to remember the IP, so it’s good to remember using some name and for that DNS server is needed.<\/p>\n\n\n\n

        DNS records are stored in \/etc\/resolv.conf<\/code> file on each host<\/p>\n\n\n\n

        <\/p>\n\n\n\n

        Now, the host is connected to internet and lot of services are running in the host, like nginx, ftp etc<\/p>\n\n\n\n

        \"\"\/<\/figure>\n\n\n\n
          \n
        • How to check the services and their ports which are opened in the host: netstat -tulnp<\/code><\/li>\n<\/ul>\n\n\n\n

          –   But, netstat command became old and now ss command is used<\/p>\n\n\n\n

          –   ss<\/code> : show socket  [ socket statistics]<\/p>\n\n\n\n

          –   check all socket info for all traffic for TCP : ss -ta<\/code><\/p>\n\n\n\n

          So, far we have seen only the LIST of Network, but to do any modification, we would need a service like NetworkManager<\/mark> or systemd-networkd.service<\/mark><\/p>\n\n\n\n

          Check if the service is loaded : systemctl list-units --type=service | grep -i \"network\"<\/code><\/p>\n\n\n\n

          To manage the networks like create, edit, list new connections, we need a tool which belongs to NetworkManager service<\/p>\n\n\n\n

          nmcli <\/code><\/p>\n\n\n\n

          <\/p>\n\n\n\n

          The IP configurations are not directly done on the interfaces. To understand how that works, we need to understand a very important concept about Connection<\/strong> & Device<\/strong> <\/p>\n\n\n\n

          Device Vs Connection<\/strong><\/p>\n\n\n\n

          \"\"<\/figure>\n\n\n\n

          Device<\/strong>: Device is the physical interface like en01, but we don\u2019t assign IPs to the device these days directly<\/p>\n\n\n\n

          Connection<\/strong>: It\u2019s a software component, where we assign the IP, Subet, DNS etc<\/p>\n\n\n\n

          And then we attach the connection to LAN card, so its decoupled now,<\/p>\n\n\n\n

          Connection can be assigned to any LAN, one at a time.<\/p>\n\n\n\n

          \"\"\/<\/figure>\n\n\n\n

          So, we can have many connections created with different configurations and attach them to LAN when needed.<\/p>\n\n\n\n

          How to see the list of connections: nmcli con show<\/code> [con = connection]<\/p>\n\n\n\n

          How to check the info about a particular connection : nmcli con show connection_name<\/code><\/p>\n\n\n\n

          –   ipv4.method \u2013 This shows if its static or dynamic IP assigned<\/p>\n\n\n\n

          <\/p>\n\n\n\n

          Lets uncover some critical commands and concepts related to connection and how that is attached to an interface<\/strong><\/p>\n\n\n\n

          How to create a new connection:\u00a0<\/strong><\/p>\n\n\n\n

          nmcli con add con-name my_connection ifname eth0 type ethernet<\/code><\/p>\n\n\n\n

          <\/p>\n\n\n\n

          How to modify the existing connection:\u00a0<\/strong><\/p>\n\n\n\n

          nmcli connection modify my_connection ipv4.method manual ipv4.address 192.168.1.19\/32 ipv4.gateway 192.169.1.1 ipv4.dns 192.168.1.1<\/code><\/p>\n\n\n\n

          <\/p>\n\n\n\n

          How to connect the connection with the ethernet device<\/strong>: nmcli connection up my_connection<\/code><\/p>\n\n\n\n

          <\/p>\n\n\n\n

          To check the status of all network interface<\/strong> : nmcli dev status<\/code><\/p>\n\n\n\n

          <\/p>\n\n\n\n

          Docker Networking & Namespace Isolation<\/strong><\/p>\n\n\n\n

          In the below section, I am trying to show how a container runtime engine like Docker isolates the network using network namespace in a Linux Kernel based Host:<\/p>\n\n\n\n

          We have got some fair understanding on the Networking on Linux host, lets understand how the networking works for the isolated namespace called containers<\/p>\n\n\n\n

          As we know, when we work with Linux, most of the process run on the global namespace, but if some process needs isolation, we can use namespace for that, <\/p>\n\n\n\n

          For an example: <\/p>\n\n\n\n

          Filesystem: chroot
          Network : ip netns
          Process : unshare PID<\/code><\/p>\n\n\n\n

          List of all namespace : lsns -t pid<\/code><\/p>\n\n\n\n

          So, when we create a container, its in its own namespace and it does not have any communication in or out. To establish connection, we have to use the concept that we have seen above, like creating interfaces, making them up and the add an IP and route, but for that we would need to create the network namespace using netns.<\/p>\n\n\n\n

          Now, whatever we would see below are the manual way of isolating the network in its own namespace and then attaching the interface and enabling connection, but, please note, docker or other container runtime engine is making it easier by providing the simple commands. <\/p>\n\n\n\n

          Docker network works on CNM (container Network model), when we install docker in Host, it automatically creates the default network (docker0) and it uses bridge driver.<\/p>\n\n\n\n

          To check that: nmcli con show<\/code><\/p>\n\n\n\n

          To check more about the connection: nmcli con show docker0<\/code><\/p>\n\n\n\n

          To check its link and ip : ip link show & ip a show<\/code><\/p>\n\n\n\n

          How to find more info about docker : docker info<\/p>\n\n\n\n

          How to check more about the docker bridge network : brctl show<\/code><\/p>\n\n\n\n

          \"\"\/<\/figure>\n\n\n\n

          We can see that, It does not have any interface attached.<\/p>\n\n\n\n

          But, the moment we create a container, it creates a veth interface connecting the container to the docker0 network.<\/p>\n\n\n\n

          \"\"\/<\/figure>\n\n\n\n

          But, from the inside of the container, it assumes that it created two interfaces, loopback and eth0 interface.<\/p>\n\n\n\n

          Since the container is connected to docker0 network, so it gets the IP in this network range<\/p>\n\n\n\n

          \"\"\/<\/figure>\n\n\n\n
          \"\"\/<\/figure>\n\n\n\n

          Docker can create a bridge network using a bridge driver<\/p>\n\n\n\n

          : docker network create -d bridge my_doc_bridge
          : Delete: docker network rm my_doc_bridge<\/code><\/p>\n\n\n\n

          But, even the Linux also can create a bridge network<\/p>\n\n\n\n

          : sudo ip link add Linux_bridge type bridge
          : Delete: sudo ip link delete my_bridge type bridge<\/code><\/p>\n\n\n\n

          Linux uses namespace to isolate the container:<\/strong><\/p>\n\n\n\n

          \"\"\/<\/figure>\n\n\n\n

          How to create a process namespace: sudo unshare -f --pid --mount-proc bash<\/code><\/p>\n\n\n\n

            \n
          • this creates a container with isolated process<\/li>\n\n\n\n
          •  ps -ef shows only one process from inside the container<\/li>\n<\/ul>\n\n\n\n

            Before we jump into network isolation, we need to understand what VLAN IS<\/strong><\/p>\n\n\n\n

            \"\"<\/figure>\n\n\n\n
              \n
            • Network devices like laptops, printers in one LAN are connected by a switch and all can communicate among each other, because all share the same broadcast domain.<\/li>\n\n\n\n
            • But, as the network grows, the network traffic management and security is a concern, so we designate few ports for one set of devices and other for other set, so that the traffic from one host does not broadcast to all available hosts on the switch, instead it can retain its broadcast traffic within its designated virtual LAN.<\/li>\n<\/ul>\n\n\n\n

              How to create a network namespace [ ip netns]<\/strong><\/p>\n\n\n\n

              sudo ip netns add isolated_net<\/code><\/p>\n\n\n\n

              \"\"\/<\/figure>\n\n\n\n

              How to list the isolated network: ip netns list<\/code><\/p>\n\n\n\n

              For more help: ip netns help<\/code><\/p>\n\n\n\n

              How to perform any task inside that isolated network: we need to use exec<\/strong><\/p>\n\n\n\n

              How to see the interface info : sudo ip netns exec isolated_net ip link<\/code><\/p>\n\n\n\n

              The isolated network has only one device \u201clo\u201d and its down and its only for loopback.<\/p>\n\n\n\n

              But, to make the isolated nw to communicate with outside, we need a way to connect them both with a virtual ethernet cable which obviously has two interfaces<\/p>\n\n\n\n

                \n
              • So, now lets create that virtual ethernet with two interfaces peered<\/li>\n<\/ul>\n\n\n\n

                On our host:<\/strong><\/p>\n\n\n\n

                Create Two Virtual Interfaces: <\/strong><\/p>\n\n\n\n

                  \n
                • create two virtual interfaces veth1 & veth2 and if we peer them, they are virtually connected.<\/li>\n<\/ul>\n\n\n\n

                  ip link add veth1 type veth peer name veth2<\/code><\/p>\n\n\n\n

                    \n
                  • List the new interface on the host: ip link list<\/code><\/li>\n<\/ul>\n\n\n\n

                    Add one interface to Host and other interface to the new isolated Network<\/strong><\/p>\n\n\n\n

                    ip link set veth2 netns isolated_net #<\/code> Added the veth2 interface to the isolated nw<\/p>\n\n\n\n

                    Check the isolated network and we can see the new interface is set to that now<\/p>\n\n\n\n

                    ip netns exec isolated_net ip link<\/code><\/p>\n\n\n\n

                    Now, we have to bring the isolated interface up<\/strong><\/p>\n\n\n\n

                      ip netns exec isolated_net ip link set dev veth2 up<\/code><\/p>\n\n\n\n

                    But, since the lowerlayer is down, so we have to  bring the peer interface on host also up : <\/p>\n\n\n\n

                    Bring up the host interface<\/strong><\/p>\n\n\n\n

                    ip link set dev veth1 up<\/code><\/p>\n\n\n\n

                    Now the interface inside the isolated nw is also up : <\/p>\n\n\n\n

                    ip netns exec isolated_net ip link<\/code><\/p>\n\n\n\n

                    Assign an IP to the Isolated Interface<\/strong><\/p>\n\n\n\n

                    ip netns exec isolated_net ip addr add 192.168.1.4\/24 dev veth2<\/code><\/p>\n\n\n\n

                    Assign IP to the host interface:<\/strong> <\/p>\n\n\n\n

                    ip addr add 192.168.1.5\/24 dev veth01<\/code><\/p>\n\n\n\n

                    Check the communication:<\/strong><\/p>\n\n\n\n

                    Able to communicate from host to virtual host: ip addr add 192.168.1.2\/24 dev veth01<\/code><\/p>\n\n\n\n

                    From isolated network to host nw: ip netns exec isolated_net ping -c 2 192.168.1.2<\/code><\/p>\n\n\n\n

                    This is exactly what docker does when we create a container using docker run<\/code> command.<\/p>\n\n\n\n

                    It automatically does all these manual work for us and get the container connected with docker internal network docker0 through veth<\/p>\n\n\n\n

                    Some useful handy command to manage network in Linux.<\/span><\/p>\n\n\n\n

                    Step<\/td>Task<\/td>Command<\/td><\/tr>
                    1<\/td>Check available network interfaces<\/td>ip link<\/code><\/td><\/tr>
                    2<\/td>Create a new virtual network device (veth, bridge, etc.)<\/td>ip link add <name> type <type><\/code><\/td><\/tr>
                    3<\/td>Bring the newly created device up<\/td>ip link set <name> up<\/code><\/td><\/tr>
                    4<\/td>Assign an IP address to an interface<\/td>ip addr add <ip_address>\/<subnet> dev <interface><\/code><\/td><\/tr>
                    5<\/td>View assigned IP addresses<\/td>ip a show<\/code><\/td><\/tr>
                    6<\/td>Attach a veth device to a network namespace<\/td>ip link set <interface> netns <namespace><\/code><\/td><\/tr>
                    7<\/td>Create a new Network Namespace<\/td>ip netns add <net_name> && ip netns list<\/code><\/td><\/tr>
                    8<\/td>Execute commands inside the namespace (check networking)<\/td>ip netns exec <namespace> ip link<\/code><\/td><\/tr>
                    9<\/td>Set default gateway (routing)<\/td>ip route add default via <gateway><\/code><\/td><\/tr>
                    10<\/td>Verify routes<\/td>route -n <\/code>OR ip route show<\/code><\/td><\/tr>
                    11<\/td>Delete a device<\/td>ip link delete <interface><\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                    <\/p>\n","protected":false},"excerpt":{"rendered":"

                    <\/span> 8<\/span> min read<\/span><\/span>3,072 Understanding Network Interfaces in Linux Onboard & PCI slot          Onboard: When the interface is integrated directly into motherboard          PCI: Its an external card integrated into motherboard The<\/p>\n","protected":false},"author":1,"featured_media":5325,"comment_status":"open","ping_status":"open","sticky":true,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"footnotes":""},"categories":[972],"tags":[],"class_list":["post-5256","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux"],"yoast_head":"\nWhat is Network Namespace in Linux? - Blog | Liainfraservices<\/title>\n<meta name=\"description\" content=\"What is network namespace in Linux, what is netns, Linux network namespace, how to create network namespace using netns\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What is Network Namespace in Linux? - Blog | Liainfraservices\" \/>\n<meta property=\"og:description\" content=\"What is network namespace in Linux, what is netns, Linux network namespace, how to create network namespace using netns\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog | Liainfraservices\" \/>\n<meta property=\"article:published_time\" content=\"2025-02-28T06:34:26+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-04-05T18:25:51+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.liainfraservices.com\/blog\/wp-content\/uploads\/2025\/02\/Containers-and-Network-Namespace-in-Linux.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2240\" \/>\n\t<meta property=\"og:image:height\" content=\"1260\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Partho\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Partho\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/\"},\"author\":{\"name\":\"Partho\",\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/#\\\/schema\\\/person\\\/b5a729cb152dd3bc7f07550ca9d223e4\"},\"headline\":\"What is Network Namespace in Linux?\",\"datePublished\":\"2025-02-28T06:34:26+00:00\",\"dateModified\":\"2025-04-05T18:25:51+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/\"},\"wordCount\":1470,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/02\\\/Containers-and-Network-Namespace-in-Linux.png\",\"articleSection\":[\"Linux\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/\",\"url\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/\",\"name\":\"What is Network Namespace in Linux? - Blog | Liainfraservices\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/02\\\/Containers-and-Network-Namespace-in-Linux.png\",\"datePublished\":\"2025-02-28T06:34:26+00:00\",\"dateModified\":\"2025-04-05T18:25:51+00:00\",\"description\":\"What is network namespace in Linux, what is netns, Linux network namespace, how to create network namespace using netns\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/02\\\/Containers-and-Network-Namespace-in-Linux.png\",\"contentUrl\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/02\\\/Containers-and-Network-Namespace-in-Linux.png\",\"width\":2240,\"height\":1260,\"caption\":\"Containers and Network Namespace in Linux\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Linux\",\"item\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/category\\\/linux\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"What is Network Namespace in Linux?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/\",\"name\":\"Blog | Liainfraservices\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/#organization\",\"name\":\"Blog | Liainfraservices\",\"url\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/10\\\/lia-logo-b-e1635340384244.png\",\"contentUrl\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/10\\\/lia-logo-b-e1635340384244.png\",\"width\":308,\"height\":96,\"caption\":\"Blog | Liainfraservices\"},\"image\":{\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.liainfraservices.com\\\/blog\\\/#\\\/schema\\\/person\\\/b5a729cb152dd3bc7f07550ca9d223e4\",\"name\":\"Partho\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6c5fc8918cc5dbc844eccbeaaf854eef27d2c79ab17ff0022304f712805d6959?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6c5fc8918cc5dbc844eccbeaaf854eef27d2c79ab17ff0022304f712805d6959?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6c5fc8918cc5dbc844eccbeaaf854eef27d2c79ab17ff0022304f712805d6959?s=96&d=mm&r=g\",\"caption\":\"Partho\"},\"description\":\"Partho Das, founder of Lia Infraservices, has 15+ years of expertise in cloud solutions, DevOps, and infrastructure security. He provides consultation on architecture planning, DevOps setup, Kubernetes, and cloud migrations. Partho holds multiple AWS and Azure certifications, along with CISCO CCNA & CCNP. Connect on LinkedIn\",\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/partho-dev\\\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What is Network Namespace in Linux? - Blog | Liainfraservices","description":"What is network namespace in Linux, what is netns, Linux network namespace, how to create network namespace using netns","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/","og_locale":"en_US","og_type":"article","og_title":"What is Network Namespace in Linux? - Blog | Liainfraservices","og_description":"What is network namespace in Linux, what is netns, Linux network namespace, how to create network namespace using netns","og_url":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/","og_site_name":"Blog | Liainfraservices","article_published_time":"2025-02-28T06:34:26+00:00","article_modified_time":"2025-04-05T18:25:51+00:00","og_image":[{"width":2240,"height":1260,"url":"https:\/\/www.liainfraservices.com\/blog\/wp-content\/uploads\/2025\/02\/Containers-and-Network-Namespace-in-Linux.png","type":"image\/png"}],"author":"Partho","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Partho","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/#article","isPartOf":{"@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/"},"author":{"name":"Partho","@id":"https:\/\/www.liainfraservices.com\/blog\/#\/schema\/person\/b5a729cb152dd3bc7f07550ca9d223e4"},"headline":"What is Network Namespace in Linux?","datePublished":"2025-02-28T06:34:26+00:00","dateModified":"2025-04-05T18:25:51+00:00","mainEntityOfPage":{"@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/"},"wordCount":1470,"commentCount":0,"publisher":{"@id":"https:\/\/www.liainfraservices.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/#primaryimage"},"thumbnailUrl":"https:\/\/www.liainfraservices.com\/blog\/wp-content\/uploads\/2025\/02\/Containers-and-Network-Namespace-in-Linux.png","articleSection":["Linux"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/","url":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/","name":"What is Network Namespace in Linux? - Blog | Liainfraservices","isPartOf":{"@id":"https:\/\/www.liainfraservices.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/#primaryimage"},"image":{"@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/#primaryimage"},"thumbnailUrl":"https:\/\/www.liainfraservices.com\/blog\/wp-content\/uploads\/2025\/02\/Containers-and-Network-Namespace-in-Linux.png","datePublished":"2025-02-28T06:34:26+00:00","dateModified":"2025-04-05T18:25:51+00:00","description":"What is network namespace in Linux, what is netns, Linux network namespace, how to create network namespace using netns","breadcrumb":{"@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/#primaryimage","url":"https:\/\/www.liainfraservices.com\/blog\/wp-content\/uploads\/2025\/02\/Containers-and-Network-Namespace-in-Linux.png","contentUrl":"https:\/\/www.liainfraservices.com\/blog\/wp-content\/uploads\/2025\/02\/Containers-and-Network-Namespace-in-Linux.png","width":2240,"height":1260,"caption":"Containers and Network Namespace in Linux"},{"@type":"BreadcrumbList","@id":"https:\/\/www.liainfraservices.com\/blog\/how-to-create-and-manage-network-namespaces-in-a-linux-using-netns\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.liainfraservices.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Linux","item":"https:\/\/www.liainfraservices.com\/blog\/category\/linux\/"},{"@type":"ListItem","position":3,"name":"What is Network Namespace in Linux?"}]},{"@type":"WebSite","@id":"https:\/\/www.liainfraservices.com\/blog\/#website","url":"https:\/\/www.liainfraservices.com\/blog\/","name":"Blog | Liainfraservices","description":"","publisher":{"@id":"https:\/\/www.liainfraservices.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.liainfraservices.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.liainfraservices.com\/blog\/#organization","name":"Blog | Liainfraservices","url":"https:\/\/www.liainfraservices.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.liainfraservices.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.liainfraservices.com\/blog\/wp-content\/uploads\/2021\/10\/lia-logo-b-e1635340384244.png","contentUrl":"https:\/\/www.liainfraservices.com\/blog\/wp-content\/uploads\/2021\/10\/lia-logo-b-e1635340384244.png","width":308,"height":96,"caption":"Blog | Liainfraservices"},"image":{"@id":"https:\/\/www.liainfraservices.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.liainfraservices.com\/blog\/#\/schema\/person\/b5a729cb152dd3bc7f07550ca9d223e4","name":"Partho","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/6c5fc8918cc5dbc844eccbeaaf854eef27d2c79ab17ff0022304f712805d6959?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/6c5fc8918cc5dbc844eccbeaaf854eef27d2c79ab17ff0022304f712805d6959?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6c5fc8918cc5dbc844eccbeaaf854eef27d2c79ab17ff0022304f712805d6959?s=96&d=mm&r=g","caption":"Partho"},"description":"Partho Das, founder of Lia Infraservices, has 15+ years of expertise in cloud solutions, DevOps, and infrastructure security. He provides consultation on architecture planning, DevOps setup, Kubernetes, and cloud migrations. Partho holds multiple AWS and Azure certifications, along with CISCO CCNA & CCNP. Connect on LinkedIn","sameAs":["https:\/\/www.linkedin.com\/in\/partho-dev\/"]}]}},"_links":{"self":[{"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/posts\/5256","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/comments?post=5256"}],"version-history":[{"count":28,"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/posts\/5256\/revisions"}],"predecessor-version":[{"id":5338,"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/posts\/5256\/revisions\/5338"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/media\/5325"}],"wp:attachment":[{"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/media?parent=5256"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/categories?post=5256"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.liainfraservices.com\/blog\/wp-json\/wp\/v2\/tags?post=5256"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}