mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
README.md: remove tapsetup note
This commit is contained in:
parent
b5b3491726
commit
5c84aeb096
14
README.md
14
README.md
@ -86,20 +86,6 @@ For specific toolchain installation, follow instructions in the
|
|||||||
version of the documentation is uploaded daily to
|
version of the documentation is uploaded daily to
|
||||||
[riot-os.org/api](https://riot-os.org/api).
|
[riot-os.org/api](https://riot-os.org/api).
|
||||||
|
|
||||||
### USING THE NATIVE PORT WITH NETWORKING
|
|
||||||
If you compile RIOT for the native cpu and include the `netdev_tap` module,
|
|
||||||
you can specify a network interface like this: `PORT=tap0 make term`
|
|
||||||
|
|
||||||
#### SETTING UP A TAP NETWORK
|
|
||||||
There is a shell script in `RIOT/dist/tools/tapsetup` called `tapsetup` which
|
|
||||||
you can use to create a network of tap interfaces.
|
|
||||||
|
|
||||||
*USAGE*
|
|
||||||
|
|
||||||
To create a bridge and two (or `count` at your option) tap interfaces:
|
|
||||||
|
|
||||||
sudo ./dist/tools/tapsetup/tapsetup [-c [<count>]]
|
|
||||||
|
|
||||||
## CONTRIBUTE
|
## CONTRIBUTE
|
||||||
|
|
||||||
To contribute something to RIOT, please refer to our
|
To contribute something to RIOT, please refer to our
|
||||||
|
Loading…
Reference in New Issue
Block a user