riot-ci/RIOT
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

examples: adapt doc on tapsetup for new sudo requirement

Browse Source
This commit is contained in:
Martine S. Lenders 2019-07-23 13:31:33 +02:00 committed by Martine Lenders
parent 38f76f951d
commit 64a0d73a0a
6 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
examples/ccn-lite-relay/README.md
View File

@ -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: An example usage of this application could be setup like this:
1. Open a terminal window, navigate to the RIOT directory, and enter 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 2. Open a second terminal window and navigate to this directory in both of
windows. windows.
3. Call `make -B clean all term` in the first terminal and `PORT=tap1 make 3. Call `make -B clean all term` in the first terminal and `PORT=tap1 make

2
examples/dtls-echo/README.md
View File

@ -12,7 +12,7 @@ Linux version of TinyDTLS. However, this is not tested yet.
Preparing the logical interfaces: Preparing the logical interfaces:
./../../dist/tools/tapsetup/tapsetup --create 2 sudo ./../../dist/tools/tapsetup/tapsetup --create 2
For the server instance: For the server instance:

2
examples/emcute_mqttsn/README.md
View File

@ -58,7 +58,7 @@ single RIOT native instance, we can do the following:
1. Setup `tap` and `tapbr` devices using RIOT's `tapsetup` script: 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 2. Assign a site-global prefix to the `tapbr0` interface (the name could be

2
examples/gnrc_networking/README.md
View File

@ -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 them. This constitutes a virtual network that the RIOT instances can
use to communicate. 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 Then, make sure you've compiled the application by calling `make` and
start the first RIOT instance by invoking `make term`. In the RIOT start the first RIOT instance by invoking `make term`. In the RIOT

2
examples/gnrc_tftp/README.md
View File

@ -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: 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 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): 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):

2
examples/ndn-ping/README.md
View File

@ -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: Create `tap` and `tapbr` devices using RIOT's `tapsetup` script before stating the application:
```bash ```bash
./RIOTDIR/dist/tools/tapsetup/tapsetup sudo ./RIOTDIR/dist/tools/tapsetup/tapsetup
``` ```
Then run the application on 2 different terminals : Then run the application on 2 different terminals :