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
3da1ac29
Commit
3da1ac29
authored
Jun 06, 2007
by
Juliusz Chroboczek
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README.
parent
91e69d82
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
2 deletions
+13
-2
README
README
+13
-2
No files found.
README
View file @
3da1ac29
...
...
@@ -28,6 +28,12 @@ the Babel netowk, just list them all:
# babel $IPv6 eth0 eth1 sit1
If your node has multiple addresses and you want all of them to
participate in the routing protocol, inject the other addresses as
zero-cost external routes:
# babel -X $IPv6-2 0 -X $IPv6-3 0 $IPv6 eth1
On an access point, you'll probably want to inject external routes
into the Babel network. First check that you have a default route
on your access point:
...
...
@@ -37,6 +43,11 @@ on your access point:
Then run the routing daemon as so:
# babel -n default 256 $IPv6 eth1
# babel -x default 256 $IPv6 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:
http://www.pps.jussieu.fr/~jch/software/ahcp/
Juliusz
Juliusz
Chroboczek
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