Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
B
babeld
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
babeld
Commits
3b2817f9
Commit
3b2817f9
authored
Oct 29, 2009
by
Juliusz Chroboczek
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix README.
parent
9206b056
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
13 deletions
+15
-13
README
README
+15
-13
No files found.
README
View file @
3b2817f9
...
...
@@ -37,10 +37,12 @@ address, and/or a unique IPv4 address.
On every node, run something like:
# ip addr add 192.168.13.33/32 dev eth1
# ip -6 addr add $(
ahcp-generate
-address -r)/128 dev eth1
# ip -6 addr add $(
generate-ipv6
-address -r)/128 dev eth1
You will find the ahcp-generate-address utility, which can generate
random IPv6 addresses according to RFC 4193, in the ahcpd package.
You will find the generate-ipv6-address utility, which can generate random
IPv6 addresses according to RFC 4193, on
http://www.pps.jussieu.fr/~jch/software/files/
A note about tunnels and VPNs
...
...
@@ -63,12 +65,12 @@ interface. This can be done by running e.g.
Run Babel on every node, specifying the set of interfaces that it
should consider:
# babel eth1
# babel
d
eth1
If your node has multiple interfaces which you want to participate in
the Babel network, just list them all:
# babel eth0 eth1 sit1
# babel
d
eth0 eth1 sit1
4. Setting up an Internet gateway
...
...
@@ -83,25 +85,25 @@ attached, so you must say something like:
In order to redistribute all routes, you will say:
# babel -C 'redistribute metric 128' eth1
# babel
d
-C 'redistribute metric 128' eth1
You may also be more selective in the routes you redistribute, for
instance by specifying the interface over which the route goes out:
# babel -C 'redistribute if eth0 metric 128' eth1
# babel
d
-C 'redistribute if eth0 metric 128' eth1
or by constraining the prefix length:
# babel -C 'redistribute ip ::/0 le 64 metric 128' \
-C 'redistribute ip 0.0.0.0/0 le 28 metric 128' \
eth1
# babel
d
-C 'redistribute ip ::/0 le 64 metric 128' \
-C 'redistribute ip 0.0.0.0/0 le 28 metric 128' \
eth1
You may also want to constrain which local routes (routes to local
interface addresses) you advertise:
# babel -C 'redistribute local if eth1' -C 'redistribute local deny' \
-C 'redistribute metric 128' \
eth1
# babel
d
-C 'redistribute local if eth1' -C 'redistribute local deny' \
-C 'redistribute metric 128' \
eth1
If you find all of this too complicated and error-prone (as I do), you
may want to consider autoconfiguring your routing domain using AHCP:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment