parent
8997c536a1
commit
7537457067
|
@ -99,9 +99,6 @@ Now we need to fill in the peer details of the node you are connecting to:
|
||||||
|
|
||||||
> The `float yes` is to allow the peer with the provided public key to connect to you using a source address **other** than the one specified (as fastd does authenticate against that). The parameter is optional.
|
> The `float yes` is to allow the peer with the provided public key to connect to you using a source address **other** than the one specified (as fastd does authenticate against that). The parameter is optional.
|
||||||
|
|
||||||
|
|
||||||
The last thing to configure now is to rise the interface up when fastd starts (as it normally doesn't rise it for you), all occurences of `<interfaceName>` here should match the one in the `interface <interfaceName>;` declaration as shown earlier.
|
|
||||||
|
|
||||||
### Modes
|
### Modes
|
||||||
|
|
||||||
Fastd can provide a tunnel with `multitap` mode on layer 2 or a tunnel with `tun` mode on layer 3. Note that the fatsd has 20 bytes less overhead when using tun.
|
Fastd can provide a tunnel with `multitap` mode on layer 2 or a tunnel with `tun` mode on layer 3. Note that the fatsd has 20 bytes less overhead when using tun.
|
||||||
|
|
Loading…
Reference in New Issue