From 362aaae7d69ef378d729bc9ae1481ee48bebb934 Mon Sep 17 00:00:00 2001 From: "Tristan B. Kildaire" Date: Mon, 1 Mar 2021 16:46:54 +0200 Subject: [PATCH] Update crxnv6.md --- docs/crxnv6.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/crxnv6.md b/docs/crxnv6.md index cd48a43..59dbcec 100644 --- a/docs/crxnv6.md +++ b/docs/crxnv6.md @@ -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] everyone can configure ipv6 +[15:56:54] even if they say it's impossible +[15:57:09] just do random things and believe in yourself +[15:57:17] 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.