mirror of https://codeberg.org/CRXN/docs.git
Deleted old files
This commit is contained in:
parent
b095b6153b
commit
e8eaeeb8d3
|
|
@ -1,59 +0,0 @@
|
|||
Bird configuration
|
||||
==================
|
||||
|
||||
Neil Alexander has provided his Bird config for those who want to run a CRXN router using enterprise software. Obviously there is a blacholed route, you won't want that and also the IP numbers must be changed to suit your configuration.
|
||||
|
||||
```bird
|
||||
filter crxn4 {
|
||||
if source = RTS_STATIC then accept;
|
||||
if net ~ [ 10.0.0.0/8+ ] then accept;
|
||||
reject;
|
||||
};
|
||||
|
||||
filter crxn6 {
|
||||
if source = RTS_STATIC then accept;
|
||||
if net ~ [ fd8a:6111:3b1a::/48+ ] then accept;
|
||||
reject;
|
||||
};
|
||||
|
||||
protocol static {
|
||||
ipv4;
|
||||
route 10.4.3.0/24 blackhole;
|
||||
}
|
||||
|
||||
protocol static {
|
||||
ipv6;
|
||||
route fd8a:6111:3b1a:eeee::/64 blackhole;
|
||||
}
|
||||
|
||||
protocol babel {
|
||||
randomize router id yes;
|
||||
ipv4 {
|
||||
import filter crxn4;
|
||||
export filter crxn4;
|
||||
};
|
||||
ipv6 {
|
||||
import filter crxn6;
|
||||
export filter crxn6;
|
||||
};
|
||||
interface "crxn*" {
|
||||
type wired;
|
||||
};
|
||||
}
|
||||
|
||||
protocol device {
|
||||
scan time 60;
|
||||
}
|
||||
|
||||
protocol direct {
|
||||
ipv4;
|
||||
ipv6;
|
||||
}
|
||||
|
||||
protocol kernel {
|
||||
ipv4 {
|
||||
export all;
|
||||
import none;
|
||||
};
|
||||
}
|
||||
```
|
||||
|
|
@ -1,59 +0,0 @@
|
|||
IPv6 configuration
|
||||
==================
|
||||
|
||||
Getting IPv6 working on your router is actually easier than IPv4. This is because `babeld` doesn't require you specify an address on the interface which it will use as the next-hop address when redistributing routes from itself to neighbouring routers. Okay, that's a bit of a lie, it **does** require them but when you have IPv6 enabled an interface on Linux it automatically gets an IPv6 link-loal address which will be used as the next-hop address. You still however will want to add an IPv6 address to **any one** of your interfaces though so it can accept packets destined to it, this can be done however on any interface.
|
||||
|
||||
## Step 0: Some hope
|
||||
|
||||
Message from BNET `#crxn` on 3rd March 2021.
|
||||
|
||||
```
|
||||
[15:56:46] <zhoreeq> everyone can configure ipv6
|
||||
[15:56:54] <zhoreeq> even if they say it's impossible
|
||||
[15:57:09] <zhoreeq> just do random things and believe in yourself
|
||||
[15:57:17] <zhoreeq> and eventually it will work
|
||||
```
|
||||
|
||||
## Step 1: Add interface to babel
|
||||
|
||||
Enable IPv6 on the interfaces you intend to run `babeld` on. I have no idea how to do this, but by default it is enabled, atleast on Raspbian.
|
||||
|
||||
**TODO:** Can someone figure out
|
||||
|
||||
## Step 2: Configure babeld
|
||||
|
||||
As with the previous tutorial on peering all you need to do is to have an interface line declared in your `/etc/babeld.conf`, nothing really changes just because you are doing IPv6. You will need to make sure you redistribute the following, so add this to your configuration:
|
||||
|
||||
```
|
||||
# Redistribute all CRXN (IPv6 - fd8a:6111:3b1a::/48)
|
||||
redistribute ip fd8a:6111:3b1a::/48 ge 48
|
||||
```
|
||||
|
||||
## Step 3: Allocate a subnet on Netbox
|
||||
|
||||
Now what you need to do is to find a `/56` available in the `fd8a:6111:3b1a::/48` range on Netbox, allocate it, and then a `/64` within said allocated subnet. It is this `/64` that we will be using for configuring your node for IPv6.
|
||||
|
||||
You can register a prefix here and find a list of all prefixes [here](https://crxn.chrisnew.de/netbox/ipam/aggregates/8/) and allocate a new one [here](https://crxn.chrisnew.de/netbox/ipam/prefixes/add/).
|
||||
|
||||
## Step 4: Add this subnet and address to your machine
|
||||
|
||||
If you recall the `on up` part to your fastd configuration then you can put this code in there if you want. A systemd unit will do as well.
|
||||
|
||||
```
|
||||
ip addr add <address>/<prefix> dev <interface>
|
||||
```
|
||||
|
||||
You can make `<interface>` the interface the subnet belongs to, for example, `eth0`, if you intend to have your IPs within your subnet accessed from your router over the LAN it is conneted to on `eth0`.
|
||||
|
||||
`ip addr` will also add a local route whne doing so (via `<interface>`). Obviously make sure `<address>` is within your chosen subnet.
|
||||
|
||||
## Step 5: Configure your client access via your router
|
||||
|
||||
Now choose your second IP from your range and run the following (this is an example where the router's IP is `fd8a:6111:3b1a:ab00::1` and the subnet allocated is `fd8a:6111:3b1a:ab00::/64` and also the client's IP is `fd8a:6111:3b1a:ab00::2`):
|
||||
|
||||
```
|
||||
ip addr add fd8a:6111:3b1a:ab00::2/64 dev ethernetForExample
|
||||
ip route add fd8a:6111:3b1a::/48 dev ethernetForExample via fd8a:6111:3b1a:ab00::1
|
||||
```
|
||||
|
||||
Where the router is on the ethernet LAN attached to interface `ethernetForExample`.
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
IP Address Management
|
||||
=====================
|
||||
|
||||
IP Address management or _IPAM_ for short is done all through our Netbox instance.
|
||||
|
||||
* [CRXN Netbox](https://crxn.chrisnew.de/netbox) (login required)
|
||||
* [View all allocations](https://crxn.chrisnew.de/netbox/ipam/prefixes/) (no login required)
|
||||
|
|
@ -1 +0,0 @@
|
|||
|
||||
Loading…
Reference in New Issue