Here are my command when I set up the interface:

sudo ip tuntap add dev router0 mod tun
sudo ip addr add dev router0
sudo ip link set dev router0 up

Here is the output of ip addr show dev router0

8: router0: <NO-CARRIER,POINTOPOINT,MULTICAST,NOARP,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 500
    inet scope global router0
       valid_lft forever preferred_lft forever

When I try to ping listen on the interface using tshark via sudo tshark -i router0, nothing happens.

Here is my ping output:

PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=64 time=0.063 ms
64 bytes from icmp_seq=2 ttl=64 time=0.058 ms

Here is my sudo tshark -i router0 output:

Capturing on 'router0'

Nothing is coming through

1 Answer 1


Because the ping actually doesn't reach a physical device, where tshark taps into it to listen for packets.

When you add an address to your computer, to any interface, it creates a special route in the table local (check your sudo ip route show table local). There will be some local routes. Any communication with local routes is designed to skip several layers of networking stack to enhance efficiency. Your packets should appears on the lo interface, so to see them you have to run sudo tshark -i lo.

  • If I were to communicate to the IP on a different machine, would tshark or any program be able to read from the device? I am creating a program that reads from devices and need to read from that interface. tshark was just my test program. Commented Jun 15, 2022 at 12:25
  • Packets appear on the lo because you ping the host itself. The same will be if you ping your address you configured on e.g. Ethernet or WiFi interface. If you ping the address that is behind the interface, packets will appear on the interface. For your case, try pinging; you'll see no answers, but tshark will still see the pings going out to router0. But that only seems to work once you open the back-end of router0 in your program (otherwise the route will have a linkdown tag and still nothing will be sent to the device) Commented Jun 15, 2022 at 12:45
  • Thank you for your answer! So, if I were to ping on the same network, not on my machine, tshark would be able to read the device? How can I put the state to UP so that I can consistently read and write to to the interface Commented Jun 15, 2022 at 19:56
  • You need to actually open the device backend in your program. The OS will consider that as "establisted link". If you send packets there, it will send it to the device and they appear in your program, and at the same time you will be able to capture them using tshrak. Commented Jun 16, 2022 at 3:18
  • "You need to actually open the device backend in your program" How do I achieve this? Do I need to bind a socket to an interface. e.g., use setsockopt Commented Jun 16, 2022 at 3:26

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .