[{"_1":2,"_173":-5,"_174":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_152":153},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":85,"_105":106,"_143":-5,"_144":11,"_145":17,"_146":11,"_147":-5,"_148":11,"_149":-5,"_150":151},"canonicalUrl","https://hub.docker.com/r/v6net/netshoot/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","v6net","reponame","netshoot","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":17,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2018-04-20T08:05:19.313016Z","description","Network trouble-shooting toolset based on nicolaka/netshoot","is_private","last_updated","2018-04-20T08:15:59.130565Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",1013,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","## netshoot: a Docker network trouble-shooting swiss-army container\n\n**Purpose:** Docker network tshooting can be difficult for network engineers. With proper understanding of how Docker networking works and the right set of tools, you can troubleshoot and resolve these networking issues. The `netshoot` container has a set of powerful networking tshooting tools that can be used to troubleshoot Docker networking issues. \n\n**Network Namespaces:** Before starting to use this tool, it's important to go over one key topic: **Network Namespaces**. Network namespaces provide isolation of the system resources associated with networking. Docker uses network and other type of namespaces (`pid`,`mount`,`user`..etc) to create an isolated environment for each container. Everything from interfaces, routes, and IPs is completely isolated within the network namespace of the container. \n\nCool thing about namespaces is that you can switch between them. You can enter a different container's network namespace, perform some troubleshooting on its network's stack with tools that aren't even installed on that container. Additionally, `netshoot` can be used to troubleshoot the host itself by using the host's network namespace. This allows you to perform any troubleshooting without installing any new packages directly on the host or your application's package. \n\n* **Container's Network Namespace:** If you're having networking issues with your application's container, you can launch `netshoot` with that container's network namespace like this :\n\n`$ docker run -it --net container: nicolaka/netshoot`\n\n* **Host's Network Namespace:** If you think the networking issue is on the host itself, you can launch `netshoot` with that host's network namespace. This is how:\n \n`$ docker run -it --net host nicolaka/netshoot`\n\n* **Network's Network Namespace:** If you want to troubleshoot a Docker network, you can enter the network's namespace using `nsenter`. This is explained in the `nsenter` section below.\n\n**Network Problems:** Many network issues could result in application performance degradations. Some of those issues could be related to the underlying networking infrastructure(underlay). Others could be related to misconfiguration at the host or Docker level. Let's take a look at common networking issues:\n\n* latency\n* routing \n* DNS resolution\n* firewall \n* incomplete ARPs\n\nTo troubleshoot these issues, `netshoot` includes a set of powerful tools as recommended by this diagram. \n\n![](http://www.brendangregg.com/Perf/linux_observability_tools.png)\n\n\n**Included Packages:** The following packages are included in `netshoot`. We'll go over some with some sample use-cases.\n\n * iperf \n * tcpdump \t\n * netstat\n * iftop \n * drill\n * netcat-openbsd \n * iproute2\n * util-linux(nsenter) \n * bridge-utils \n * iputils \n * curl\n * ethtool\n * nmap\n * ipvs\n * ngrep\n\n\n## iperf \n\nPurpose : test networking performance between two containers/hosts. \n\nCreate Overlay network:\n\n```\n$ docker network create -d overlay perf-test\n```\nLaunch two containers:\n\n```\n🐳 → docker service create --name perf-test-a --network perf-test nicolaka/netshoot iperf -s -p 9999\n7dkcckjs0g7b4eddv8e5ez9nv\n\n\n🐳 → docker service create --name perf-test-b --network perf-test nicolaka/netshoot iperf -c perf-test-a -p 9999\n2yb6fxls5ezfnav2z93lua8xl\n\n\n\n 🐳 → docker service ls\nID NAME REPLICAS IMAGE COMMAND\n2yb6fxls5ezf perf-test-b 1/1 nicolaka/netshoot iperf -c perf-test-a -p 9999\n7dkcckjs0g7b perf-test-a 1/1 nicolaka/netshoot iperf -s -p 9999\n\n\n\n🐳 → docker ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\nce4ff40a5456 nicolaka/netshoot:latest \"iperf -s -p 9999\" 31 seconds ago Up 30 seconds perf-test-a.1.bil2mo8inj3r9nyrss1g15qav\n\n🐳 → docker logs ce4ff40a5456\n------------------------------------------------------------\nServer listening on TCP port 9999\nTCP window size: 85.3 KByte (default)\n------------------------------------------------------------\n[ 4] local 10.0.3.3 port 9999 connected with 10.0.3.5 port 35102\n[ ID] Interval Transfer Bandwidth\n[ 4] 0.0-10.0 sec 32.7 GBytes 28.1 Gbits/sec\n[ 5] local 10.0.3.3 port 9999 connected with 10.0.3.5 port 35112\n\n```\n\n## tcpdump\n\n**tcpdump** is a powerful and common packet analyzer that runs under the command line. It allows the user to display TCP/IP and other packets being transmitted or received over an attached network interface. \n\n```\n# Continuing on the iperf example. Let's lauch netshoot with perf-test-a's container network namespace.\n\n🐳 → docker run -it --net container:perf-test-a.1.0qlf1kaka0cq38gojf7wcatoa nicolaka/netshoot \n\n# Capturing packets on eth0 and tcp port 9999.\n\n/ # tcpdump -i eth0 port 9999 -c 1 -Xvv\ntcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes\n23:14:09.771825 IP (tos 0x0, ttl 64, id 60898, offset 0, flags [DF], proto TCP (6), length 64360)\n 10.0.3.5.60032 > 0e2ccbf3d608.9999: Flags [.], cksum 0x1563 (incorrect -> 0x895d), seq 222376702:222441010, ack 3545090958, win 221, options [nop,nop,TS val 2488870 ecr 2488869], length 64308\n\t0x0000: 4500 fb68 ede2 4000 4006 37a5 0a00 0305 E..h..@.@.7.....\n\t0x0010: 0a00 0303 ea80 270f 0d41 32fe d34d cb8e ......'..A2..M..\n\t0x0020: 8010 00dd 1563 0000 0101 080a 0025 fa26 .....c.......%.&\n\t0x0030: 0025 fa25 0000 0000 0000 0001 0000 270f .%.%..........'.\n\t0x0040: 0000 0000 0000 0000 ffff d8f0 3435 3637 ............4567\n\t0x0050: 3839 3031 3233 3435 3637 3839 3031 3233 8901234567890123\n\t0x0060: 3435 3637 3839 3031 3233 3435 3637 3839 4567890123456789\n\t0x0070: 3031 3233 3435 3637 3839 3031 3233 3435 0123456789012345\n\t0x0080: 3637 3839 3031 3233 3435 3637 3839 3031 6789012345678901\n\t0x0090: 3233 3435 3637 3839 3031 3233 3435 3637 2345678901234567\n\t0x00a0: 3839 3031 3233 3435 3637 3839 3031 3233 8901234567890123\n\t0x00b0: 3435 3637 3839 3031 3233 3435 3637 3839 4567890123456789\n\t0x00c0: 3031 3233 3435 3637 3839 3031 3233 3435 0123456789012345\n\t0x00d0: 3637 3839 3031 3233 3435 3637 3839 3031 6789012345678901\n\t0x00e0: 3233 3435 3637 3839 3031 3233 3435 3637 2345678901234567\n\t0x00f0: 3839 3031 3233 3435 3637 3839 3031 3233 8901234567890123\n\t0x0100: 3435 3637 3839 3031 3233 3435 3637 3839 4567890123456789\n\t\n```\n\nMore info on `tcpdump` can be found [here](http://www.tcpdump.org/tcpdump_man.html).\n\n\n\n## netstat\n\nPurpose: `netstat` is a useful tool for checking your network configuration and activity. \n\nContinuing on from `iperf` example. Let's use `netstat` to confirm that it's listening on port `9999`. \n\n\n```\n🐳 → docker run -it --net container:perf-test-a.1.0qlf1kaka0cq38gojf7wcatoa nicolaka/netshoot \n\n/ # netstat -tulpn\nActive Internet connections (only servers)\nProto Recv-Q Send-Q Local Address Foreign Address State PID/Program name\ntcp 0 0 127.0.0.11:46727 0.0.0.0:* LISTEN -\ntcp 0 0 0.0.0.0:9999 0.0.0.0:* LISTEN -\nudp 0 0 127.0.0.11:39552 0.0.0.0:* -\n```\n\n## nmap\n`nmap` (\"Network Mapper\") is an open source tool for network exploration and security auditing. It is very useful for scanning to see which ports are open between a given set of hosts. This is a common thing to check for when installing Swarm or UCP because a range of ports is required for cluster communication. The command analyzes the connection pathway between the host where `nmap` is running and the given target address.\n\n```\n🐳 → docker run -it --privileged nicolaka/netshoot nmap -p 12376-12390 -dd 172.31.24.25\n\n...\nDiscovered closed port 12388/tcp on 172.31.24.25\nDiscovered closed port 12379/tcp on 172.31.24.25\nDiscovered closed port 12389/tcp on 172.31.24.25\nDiscovered closed port 12376/tcp on 172.31.24.25\n...\n```\nThere are several states that ports will be discovered as:\n\n- `open`: the pathway to the port is open and there is an application listening on this port.\n- `closed`: the pathway to the port is open but there is no application listening on this port.\n- `filtered`: the pathway to the port is closed, blocked by a firewall, routing rules, or host-based rules.\n\n\n## iftop\n\nPurpose: iftop does for network usage what top does for CPU usage. It listens to network traffic on a named interface and displays a table of current bandwidth usage by pairs of hosts.\n\nContinuing the `iperf` example.\n\n```\n → docker ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\nce4ff40a5456 nicolaka/netshoot:latest \"iperf -s -p 9999\" 5 minutes ago Up 5 minutes perf-test-a.1.bil2mo8inj3r9nyrss1g15qav\n\n🐳 → docker run -it --net container:perf-test-a.1.bil2mo8inj3r9nyrss1g15qav nicolaka/netshoot iftop -i eth0\n\n```\n\n![iftop.png](img/iftop.png)\n\n\n## drill\n\nPurpose: drill is a tool\tto designed to get all sorts of information out of the DNS.\n\nContinuing the `iperf` example, we'll use `drill` to understand how services' DNS is resolved in Docker. \n\n\n```\n🐳 → docker run -it --net container:perf-test-a.1.bil2mo8inj3r9nyrss1g15qav nicolaka/netshoot drill -V 5 perf-test-b\n;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0\n;; flags: rd ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0\n;; QUESTION SECTION:\n;; perf-test-b.\tIN\tA\n\n;; ANSWER SECTION:\n\n;; AUTHORITY SECTION:\n\n;; ADDITIONAL SECTION:\n\n;; Query time: 0 msec\n;; WHEN: Thu Aug 18 02:08:47 2016\n;; MSG SIZE rcvd: 0\n;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 52723\n;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0\n;; QUESTION SECTION:\n;; perf-test-b.\tIN\tA\n\n;; ANSWER SECTION:\nperf-test-b.\t600\tIN\tA\t10.0.3.4 <<<<<<<<<<<<<<<<<<<<<<<<<< Service VIP\n\n;; AUTHORITY SECTION:\n\n;; ADDITIONAL SECTION:\n\n;; Query time: 1 msec\n;; SERVER: 127.0.0.11 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Local resolver \n;; WHEN: Thu Aug 18 02:08:47 2016\n;; MSG SIZE rcvd: 56\n```\n\n## netcat\n\nPurpose: a simple Unix utility that reads and writes data across network connections, using the TCP or UDP protocol. It's useful for testing and troubleshooting TCP/UDP connections. If there's a firewall rule blocking certain ports, `netcat` can be used to detect\n\n```\n🐳 → docker network create -d overlay my-ovl\n55rohpeerwqx8og4n0byr0ehu\n\n🐳 → docker service create --name service-a --network my-ovl -p 8080:8080 nicolaka/netshoot nc -l 8080\nbnj517hh4ylpf7ewawsp9unrc\n\n🐳 → docker service create --name service-b --network my-ovl nicolaka/netshoot nc -vz service-a 8080\n3xv1ukbd3kr03j4uybmmlp27j\n\n🐳 → docker logs service-b.1.0c5wy4104aosovtl1z9oixiso\nConnection to service-a 8080 port [tcp/http-alt] succeeded!\n\n```\n## netgen\n`netgen` is a simple [script](netgen.sh) that will generate a packet of data between containers periodically using `netcat`. It's purpose is to use the generated traffic to demonstrate different features of the networking stack.\n\n\n`netgen ` will create a `netcat` server and client listening and sending to the same port.\n\nUsing `netgen` with `docker run`:\n\n```\n🐳 → docker network create -d bridge br\n01b167971453700cf0a40d7e1a0dc2b0021e024bbb119541cc8c1858343c9cfc\n\n🐳 → docker run -d --rm --net br --name c1 nicolaka/netshoot netgen c2 5000\n8c51eb2100c35d14244dcecb80839c780999159985415a684258c7154ec6bd42\n\n🐳 → docker run -it --rm --net br --name c2 nicolaka/netshoot netgen c1 5000\nListener started on port 5000\nSending traffic to c1 on port 5000 every 10 seconds\nSent 1 messages to c1:5000\nSent 2 messages to c1:5000\n\n🐳 → sudo tcpdump -vvvn -i eth0 port 5000\n...\n```\n\nUsing `netgen` with `docker services`:\n\n```\n🐳 → docker network create -d overlay ov\n01b167971453700cf0a40d7e1a0dc2b0021e024bbb119541cc8c1858343c9cfc\n\n🐳 → docker service create --network ov --replicas 3 --name srvc netshoot netgen srvc 5000\ny93t8mb9wgzsc27f7l2rdu5io\n\n🐳 → docker service logs srvc\nsrvc.1.vwklts5ybq5w@moby | Listener started on port 5000\nsrvc.1.vwklts5ybq5w@moby | Sending traffic to srvc on port 5000 every 10 seconds\nsrvc.1.vwklts5ybq5w@moby | Sent 1 messages to srvc:5000\nsrvc.3.dv4er00inlxo@moby | Listener started on port 5000\nsrvc.2.vu47gf0sdmje@moby | Listener started on port 5000\n...\n\n\n🐳 → sudo tcpdump -vvvn -i eth0 port 5000\n...\n```\n\n\n## iproute2\n\npurpose: a collection of utilities for controlling TCP / IP networking and traffic control in Linux.\n\n```\n# Sample routing and arp table of the docker host.\n\n🐳 → docker run -it --net host nicolaka/netshoot\n\n/ # ip route show\ndefault via 192.168.65.1 dev eth0 metric 204\n172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1\n172.19.0.0/16 dev br-fd694678f5c3 proto kernel scope link src 172.19.0.1 linkdown\n172.20.0.0/16 dev docker_gwbridge proto kernel scope link src 172.20.0.1\n172.21.0.0/16 dev br-0d73cc4ac114 proto kernel scope link src 172.21.0.1 linkdown\n172.22.0.0/16 dev br-1eb1f1e84df8 proto kernel scope link src 172.22.0.1 linkdown\n172.23.0.0/16 dev br-aafed4ec941f proto kernel scope link src 172.23.0.1 linkdown\n192.168.65.0/29 dev eth0 proto kernel scope link src 192.168.65.2\n\n/ # ip neigh show\n192.168.65.1 dev eth0 lladdr f6:16:36:bc:f9:c6 STALE\n172.17.0.7 dev docker0 lladdr 02:42:ac:11:00:07 STALE\n172.17.0.6 dev docker0 lladdr 02:42:ac:11:00:06 STALE\n172.17.0.5 dev docker0 lladdr 02:42:ac:11:00:05 STALE\n```\n\nMore info on `iproute2` [here](http://lartc.org/howto/lartc.iproute2.tour.html)\n\n## nsenter\n\nPrupose: `nsenter` is a powerful tool allowing you to enter into any namespaces. `nsenter` is available inside `netshoot` but requires `netshoot` to be run as a privileged container. Additionally, you may want to mount the `/var/run/docker/netns` directory to be able to enter any network namespace including bridge and overlay networks. \n\n\nWith `docker run --name container-B --net container:container-A `, docker uses `container-A`'s network namespace ( including interfaces and routes) when creating `container-B`. This approach is helpful for troubleshooting network issues at the container level. To troubleshoot network issues at the bridge or overlay network level, you need to enter the `namespace` of the network _itself_. `nsenter` allows you to do that. \n\nFor example, if we wanted to check the L2 forwarding table for a overlay network. We need to enter the overlay network namespace and use same tools in `netshoot` to check these entries. The following examples go over some use cases for using `nsenter` to understand what's happening within a docker network ( overlay in this case).\n\n```\n# Creating an overlay network\n🐳 → docker network create -d overlay nsenter-test\n9tp0f348donsdj75pktssd97b\n\n# Launching a simple busybox service with 3 replicas\n🐳 → docker service create --name nsenter-l2-table-test --replicas 3 --network nsenter-test busybox ping localhost\n3692i3q3u8nephdco2c10ro4c\n\n# Inspecting the service\n🐳 → docker network inspect nsenter-test\n[\n {\n \"Name\": \"nsenter-test\",\n \"Id\": \"9tp0f348donsdj75pktssd97b\",\n \"Scope\": \"swarm\",\n \"Driver\": \"overlay\",\n \"EnableIPv6\": false,\n \"IPAM\": {\n \"Driver\": \"default\",\n \"Options\": null,\n \"Config\": [\n {\n \"Subnet\": \"10.0.1.0/24\",\n \"Gateway\": \"10.0.1.1\"\n }\n ]\n },\n \"Internal\": false,\n \"Containers\": {\n \"0ebe0fab555d2e2ef2fcda634bef2071ad3f5842b06bd134b40f259ab9be4f13\": {\n \"Name\": \"nsenter-l2-table-test.2.83uezc16jcaz2rp6cjwyf4605\",\n \"EndpointID\": \"3064946bb0224a4b3647cefcba18dcbea71b90a2ba1c09212a7bc599ec1ed3eb\",\n \"MacAddress\": \"02:42:0a:00:01:04\",\n \"IPv4Address\": \"10.0.1.4/24\",\n \"IPv6Address\": \"\"\n },\n \"55065360ac1c71638fdef50a073a661dec53b693409c5e09f8f854abc7dbb373\": {\n \"Name\": \"nsenter-l2-table-test.1.4ryh3wmmv21nsrfwmilanypqq\",\n \"EndpointID\": \"f81ae5f979d6c54f60636ca9bb2107d95ebf9a08f64786c549e87a66190f1b1f\",\n \"MacAddress\": \"02:42:0a:00:01:03\",\n \"IPv4Address\": \"10.0.1.3/24\",\n \"IPv6Address\": \"\"\n },\n \"57eca277749bb01a488f0e6c4e91dc6720b7c8f08531536377b29a972971f54b\": {\n \"Name\": \"nsenter-l2-table-test.3.9cuoq5m2ue1wi4lsw64k88tvz\",\n \"EndpointID\": \"ff1a251ffd6c674cd5fd117386d1a197ab68b4ed708187035d91ff5bd5fe0251\",\n \"MacAddress\": \"02:42:0a:00:01:05\",\n \"IPv4Address\": \"10.0.1.5/24\",\n \"IPv6Address\": \"\"\n }\n },\n \"Options\": {\n \"com.docker.network.driver.overlay.vxlanid_list\": \"260\"\n },\n \"Labels\": {}\n }\n]\n\n# Launcing netshoot in privileged mode\n 🐳 → docker run -it --rm -v /var/run/docker/netns:/var/run/docker/netns --privileged=true nicolaka/netshoot\n \n# Listing all docker-created network namespaces\n \n / # cd /var/run/docker/netns/\n/var/run/docker/netns # ls\n0b1b36d33313 1-9tp0f348do 14d1428c3962 645eb414b538 816b96054426 916dbaa7ea76 db9fd2d68a9b e79049ce9994 f857b5c01ced\n1-9r17dodsxt 1159c401b8d8 1a508036acc8 7ca29d89293c 83b743f2f087 aeed676a57a5 default f22ffa5115a0\n\n\n# The overlay network that we created had an id of 9tp0f348donsdj75pktssd97b. All overlay networks are named -. We can see it in the list as `1-9tp0f348do`. To enter it:\n\n/ # nsenter --net=/var/run/docker/netns/1-9tp0f348do sh\n\n# Now all the commands we issue are within that namespace. \n\n/ # ifconfig\nbr0 Link encap:Ethernet HWaddr 02:15:B8:E7:DE:B3\n inet addr:10.0.1.1 Bcast:0.0.0.0 Mask:255.255.255.0\n inet6 addr: fe80::20ce:a5ff:fe63:437d%32621/64 Scope:Link\n UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1\n RX packets:36 errors:0 dropped:0 overruns:0 frame:0\n TX packets:18 errors:0 dropped:0 overruns:0 carrier:0\n collisions:0 txqueuelen:0\n RX bytes:2224 (2.1 KiB) TX bytes:1348 (1.3 KiB)\n\nlo Link encap:Local Loopback\n inet addr:127.0.0.1 Mask:255.0.0.0\n inet6 addr: ::1%32621/128 Scope:Host\n UP LOOPBACK RUNNING MTU:65536 Metric:1\n RX packets:4 errors:0 dropped:0 overruns:0 frame:0\n TX packets:4 errors:0 dropped:0 overruns:0 carrier:0\n collisions:0 txqueuelen:1\n RX bytes:336 (336.0 B) TX bytes:336 (336.0 B)\n\nveth2 Link encap:Ethernet HWaddr 02:15:B8:E7:DE:B3\n inet6 addr: fe80::15:b8ff:fee7:deb3%32621/64 Scope:Link\n UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1\n RX packets:9 errors:0 dropped:0 overruns:0 frame:0\n TX packets:32 errors:0 dropped:0 overruns:0 carrier:0\n collisions:0 txqueuelen:0\n RX bytes:690 (690.0 B) TX bytes:2460 (2.4 KiB)\n\nveth3 Link encap:Ethernet HWaddr 7E:55:C3:5C:C2:78\n inet6 addr: fe80::7c55:c3ff:fe5c:c278%32621/64 Scope:Link\n UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1\n RX packets:13 errors:0 dropped:0 overruns:0 frame:0\n TX packets:26 errors:0 dropped:0 overruns:0 carrier:0\n collisions:0 txqueuelen:0\n RX bytes:970 (970.0 B) TX bytes:1940 (1.8 KiB)\n\nveth4 Link encap:Ethernet HWaddr 72:95:AB:A1:6A:87\n inet6 addr: fe80::7095:abff:fea1:6a87%32621/64 Scope:Link\n UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1\n RX packets:14 errors:0 dropped:0 overruns:0 frame:0\n TX packets:27 errors:0 dropped:0 overruns:0 carrier:0\n collisions:0 txqueuelen:0\n RX bytes:1068 (1.0 KiB) TX bytes:2038 (1.9 KiB)\n\nvxlan1 Link encap:Ethernet HWaddr EA:EC:1D:B1:7D:D7\n inet6 addr: fe80::e8ec:1dff:feb1:7dd7%32621/64 Scope:Link\n UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1\n RX packets:0 errors:0 dropped:0 overruns:0 frame:0\n TX packets:0 errors:0 dropped:33 overruns:0 carrier:0\n collisions:0 txqueuelen:0\n RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)\n\n# Let's check out the L2 forwarding table. These MAC addresses belong to the tasks/containers in this service. \n\n/ # bridge fdb show br br0\n33:33:00:00:00:01 dev br0 self permanent\n01:00:5e:00:00:01 dev br0 self permanent\n33:33:ff:63:43:7d dev br0 self permanent\nea:ec:1d:b1:7d:d7 dev vxlan1 master br0 permanent\n02:15:b8:e7:de:b3 dev veth2 master br0 permanent\n33:33:00:00:00:01 dev veth2 self permanent\n01:00:5e:00:00:01 dev veth2 self permanent\n33:33:ff:e7:de:b3 dev veth2 self permanent\n7e:55:c3:5c:c2:78 dev veth3 master br0 permanent\n33:33:00:00:00:01 dev veth3 self permanent\n01:00:5e:00:00:01 dev veth3 self permanent\n33:33:ff:5c:c2:78 dev veth3 self permanent\n72:95:ab:a1:6a:87 dev veth4 master br0 permanent\n33:33:00:00:00:01 dev veth4 self permanent\n01:00:5e:00:00:01 dev veth4 self permanent\n33:33:ff:a1:6a:87 dev veth4 self permanent\n\n\n# ARP and routing tables. Note that an overlay network only routes traffic for that network. It only has a single route that matches the subnet of that network.\n\n/ # ip neigh show\n/ # ip route\n10.0.1.0/24 dev br0 proto kernel scope link src 10.0.1.1\n\n# Looks like the arp table is flushed. Let's ping some of the containers on this network.\n\n/ # ping 10.0.1.4\nPING 10.0.1.4 (10.0.1.4) 56(84) bytes of data.\n64 bytes from 10.0.1.4: icmp_seq=1 ttl=64 time=0.207 ms\n64 bytes from 10.0.1.4: icmp_seq=2 ttl=64 time=0.087 ms\n^C\n--- 10.0.1.4 ping statistics ---\n2 packets transmitted, 2 received, 0% packet loss, time 1002ms\nrtt min/avg/max/mdev = 0.087/0.147/0.207/0.060 ms\n\n/ # ip neigh show\n10.0.1.4 dev br0 lladdr 02:42:0a:00:01:04 REACHABLE\n\n# and using bridge-utils to show interfaces of the overlay network local bridge.\n\n/ # brctl show\nbridge name\tbridge id\t\tSTP enabled\tinterfaces\nbr0\t\t8000.0215b8e7deb3\tno\t\tvxlan1\n\t\t\t\t\t\t\tveth2\n\t\t\t\t\t\t\tveth3\n\t\t\t\t\t\t\tveth4\n\t\t\t\t\t\t\t\n```\n\n\n## Feedback + Contribution\n\nFeel free to provide feedback and contribute networking troubleshooting tools and use-cases by opening PRs.\n\n\n\n\n\n\n\n \n\n\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",40875504,"orgData",{"_86":87,"_88":89,"_90":91,"_92":29,"_93":94,"_95":94,"_96":97,"_98":94,"_99":100,"_101":94,"_102":94,"_103":94,"_104":17},"id","e7d06b985d744ce7986db2920a26c2cc","uuid","e7d06b98-5d74-4ce7-986d-b2920a26c2cc","type","organization","orgname","full_name","","location","company","version6.net","profile_url","date_joined","2015-04-04T10:53:26.889323Z","gravatar_url","gravatar_email","badge","is_active","recentTags",[107],{"_108":40,"_109":110,"_111":112,"_86":113,"_114":115,"_46":132,"_133":110,"_134":29,"_135":52,"_53":136,"_137":138,"_139":123,"_140":132,"_141":62,"_142":17},"content_type","creator",265262,"full_size",40871638,25978722,"images",[116],{"_117":118,"_119":120,"_121":94,"_122":123,"_124":125,"_126":127,"_128":94,"_129":-5,"_130":112,"_59":62,"_131":-5},"architecture","amd64","digest","sha256:dd2ee15f94755a06378d900862877d27eb40205903b676ee9173540acdc425d0","features","last_pulled","2026-09-24T02:55:06.719114141Z","last_pushed","2018-04-20T08:15:58Z","os","linux","os_features","os_version","size","variant","2018-04-20T08:15:57.881586Z","last_updater","last_updater_username","media_type","latest","repository",5411438,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":154,"_161":162,"_150":171,"_172":11},{"_36":155,"_38":156,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":157,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":158,"_75":17,"_76":160,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":159},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_163":60,"_164":-5,"_165":-5,"_166":167},"count","next","previous","results",[168],{"_108":40,"_109":110,"_111":112,"_86":113,"_114":169,"_46":132,"_133":110,"_134":29,"_135":52,"_53":136,"_137":138,"_139":123,"_140":132,"_141":62,"_142":17},[170],{"_117":118,"_119":120,"_121":94,"_122":123,"_124":125,"_126":127,"_128":94,"_129":-5,"_130":112,"_59":62,"_131":-5},[],"canDeleteTags","actionData","errors"]

v6net/netshoot

Tags for v6net/netshoot