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

Update crxnv6.md

This commit is contained in:
Tristan B. Kildaire 2021-03-01 16:46:54 +02:00 committed by GitHub
parent 7e5e93fcc5
commit 362aaae7d6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/crxnv6.md
View File

@ -3,6 +3,17 @@ 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.