Update README.md
This commit is contained in:
parent
50bbcfa363
commit
554fd4f62d
@ -14,7 +14,7 @@ Run: `tincd -n lixonet -K`
|
|||||||
|
|
||||||
All options are supplied in the `name=value` format on individual lines, i.e. `name=test_name_lixo`
|
All options are supplied in the `name=value` format on individual lines, i.e. `name=test_name_lixo`
|
||||||
|
|
||||||
* `name` - The global neighbor name. Tinc and Bird use this to identify a peer in the network, and to exclude your own pre-packed config automagically from BIRD so you don't connect to yourself over and over again.
|
* `name` - The global neighbor name. Tinc and Bird use this to identify a peer in the network, and to exclude your own pre-packed config automagically from Tinc and BIRD dialing out so you don't connect to yourself over and over again.
|
||||||
* `address` - The *router* address to use. This is your Lixonet routing layer address: 172.xxx.0.xxx
|
* `address` - The *router* address to use. This is your Lixonet routing layer address: 172.xxx.0.xxx
|
||||||
* `asn` - The BGP ASN to use. We usually follow the format `4206969XXX` where _XXX_ is the last octet of your `address`, zero-padded (i.e. 008 or 212)
|
* `asn` - The BGP ASN to use. We usually follow the format `4206969XXX` where _XXX_ is the last octet of your `address`, zero-padded (i.e. 008 or 212)
|
||||||
* `netmask` - The routing layer netmask to use. This should be `255.255.255.0` in most cases as our routing layer has always been a ``/24` subnet. Used by Tinc and BIRD for the L2 mesh and route security ingress filtering respectively.
|
* `netmask` - The routing layer netmask to use. This should be `255.255.255.0` in most cases as our routing layer has always been a ``/24` subnet. Used by Tinc and BIRD for the L2 mesh and route security ingress filtering respectively.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user