diff --git a/examples/ccn-lite-relay/README.md b/examples/ccn-lite-relay/README.md
index 012cdb50f8..c8326bb347 100644
--- a/examples/ccn-lite-relay/README.md
+++ b/examples/ccn-lite-relay/README.md
@@ -39,7 +39,7 @@ RIOT provides three shell to interact with the CCN-Lite stack:
 
 An example usage of this application could be setup like this:
 1. Open a terminal window, navigate to the RIOT directory, and enter
-   `dist/tools/tapsetup/tapsetup -c`.
+   `sudo dist/tools/tapsetup/tapsetup -c`.
 2. Open a second terminal window and navigate to this directory in both of
    windows.
 3. Call `make -B clean all term` in the first terminal and `PORT=tap1 make
diff --git a/examples/dtls-echo/README.md b/examples/dtls-echo/README.md
index 616d065eca..047a11b6be 100644
--- a/examples/dtls-echo/README.md
+++ b/examples/dtls-echo/README.md
@@ -12,7 +12,7 @@ Linux version of TinyDTLS. However, this is not tested yet.
 
 Preparing the logical interfaces:
 
-    ./../../dist/tools/tapsetup/tapsetup --create 2
+    sudo ./../../dist/tools/tapsetup/tapsetup --create 2
 
 For the server instance:
 
diff --git a/examples/emcute_mqttsn/README.md b/examples/emcute_mqttsn/README.md
index 57ccc6565d..c3acdb9cbc 100644
--- a/examples/emcute_mqttsn/README.md
+++ b/examples/emcute_mqttsn/README.md
@@ -58,7 +58,7 @@ single RIOT native instance, we can do the following:
 
 1. Setup `tap` and `tapbr` devices using RIOT's `tapsetup` script:
 ```
-./RIOTDIR/dist/tools/tapsetup/tapsetup
+sudo ./RIOTDIR/dist/tools/tapsetup/tapsetup
 ```
 
 2. Assign a site-global prefix to the `tapbr0` interface (the name could be
diff --git a/examples/gnrc_networking/README.md b/examples/gnrc_networking/README.md
index fa9f0a1d1f..5f3073b3b5 100644
--- a/examples/gnrc_networking/README.md
+++ b/examples/gnrc_networking/README.md
@@ -104,7 +104,7 @@ you first need to set up two tap devices and a bridge that connects
 them. This constitutes a virtual network that the RIOT instances can
 use to communicate.
 
-    ./../../dist/tools/tapsetup/tapsetup --create 2
+    sudo ./../../dist/tools/tapsetup/tapsetup --create 2
 
 Then, make sure you've compiled the application by calling `make` and
 start the first RIOT instance by invoking `make term`. In the RIOT
@@ -156,4 +156,4 @@ In your first terminal, you should now see output that looks like this.
     dst_l2addr: 62:fc:3c:5e:40:df
     ~~ PKT    -  4 snips, total size:  79 byte
 
-[sso]: https://stackoverflow.com/questions/14478167/bind-socket-to-network-interface#14478657
\ No newline at end of file
+[sso]: https://stackoverflow.com/questions/14478167/bind-socket-to-network-interface#14478657
diff --git a/examples/gnrc_tftp/README.md b/examples/gnrc_tftp/README.md
index 2627976a2e..19b5a499a9 100644
--- a/examples/gnrc_tftp/README.md
+++ b/examples/gnrc_tftp/README.md
@@ -12,7 +12,7 @@ however show up in Wireshark, which can be confusing). So be sure to adjust your
 
 First, create a tap interface (to which RIOT will connect) and a bridge (to which Linux will connect) from the RIOT main directory run:
 
-    ./dist/tools/tapsetup/tapsetup -c 1
+    sudo ./dist/tools/tapsetup/tapsetup -c 1
 
 Now you can start the `gnrc_tftp` example by invoking `make term`. This should automatically connect to the `tap0` interface. If
 this doesn't work for some reason, run `make` without any arguments, and then run the binary manually like so (assuming you are in the `examples/gnrc_tftp` directory):
diff --git a/examples/ndn-ping/README.md b/examples/ndn-ping/README.md
index d8335a9740..54dced636b 100644
--- a/examples/ndn-ping/README.md
+++ b/examples/ndn-ping/README.md
@@ -8,7 +8,7 @@ Any board with a default netdev can be used to run this example.
 
 Create `tap` and `tapbr` devices using RIOT's `tapsetup` script before stating the application:
 ```bash
-./RIOTDIR/dist/tools/tapsetup/tapsetup
+sudo ./RIOTDIR/dist/tools/tapsetup/tapsetup
 ```
 
 Then run the application on 2 different terminals :