CRXN
/
docs
mirror of http://deavmi.assigned.network/git/CRXN/docs
1
0
Fork 0
Code Releases Activity

Merge https://codeberg.org/CRXN/docs

This commit is contained in:
Marek Küthe 2022-12-21 13:35:55 +01:00
parent 016714c38c 37f45918da
commit 82ecb5f53d
No known key found for this signature in database
GPG Key ID: 7E869146699108C7
2 changed files with 25 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/routing/bird.md
View File

@ -115,8 +115,6 @@ TODO: Add a check about not installing RTD_UNREACHABLEs which babel will generat
### Direct protocol ### Direct protocol
TODO: fix/finish this section
This provides BIRD with a manner of picking up the `subnet/prefix` pair that is assigned to local interfaces such that these can be imported into BIRD and later advertised. This provides BIRD with a manner of picking up the `subnet/prefix` pair that is assigned to local interfaces such that these can be imported into BIRD and later advertised.
``` ```
@ -127,11 +125,31 @@ protocol direct crxnDirect
table crxn; table crxn;
import filter crxnFilter; import filter crxnFilter;
}; };
# Interfaces to find neighbours on
# Interfaces to find neighbors on
interface "eth*"; interface "eth*";
} }
``` ```
### Kernel protocol
We need to sync the routes from the BIRD routing table `crxn` to the actual kernel's routing table such that it can be used in forwarding decisions. This is accomplished with the following declaration:
```
protocol kernel crxnKernel
{
ipv6 {
# bird's crxn table -> kernel
table crxn;
export filter crxnFilter;
};
persist;
}
```
1. The `persist` option means that when BIRD exits it will not flush the routing table. This is useful if you want to do maintenance and still want to allow forwarding of traffic for a little while (of course other routers may expire routes to you but at least not that fast)
--- ---
Old stuff below WIP): Old stuff below WIP):

4
docs/tunneling/fastd.md
View File

@ -47,6 +47,7 @@ peer "<peerName>"
remote <type> "<ip>" port <port>; remote <type> "<ip>" port <port>;
key "<peer's public key>"; key "<peer's public key>";
interface "<interface>"; interface "<interface>";
float yes;
} }
``` ```
@ -94,6 +95,9 @@ Now we need to fill in the peer details of the node you are connecting to:
5. `"<peer's public key>"` 5. `"<peer's public key>"`
* Set this to your peer's public key * Set this to your peer's public key
> 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). [Read more](https://fastd.readthedocs.io/en/stable/manual/config.html#main-configuration).
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. 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.
### Starting and maintaining the daemon ### Starting and maintaining the daemon