Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
S
sroamd
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
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
sroamd
Commits
121f4956
Commit
121f4956
authored
4 years ago
by
Juliusz Chroboczek
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README.
parent
b63c15af
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
32 additions
and
19 deletions
+32
-19
README
README
+32
-19
No files found.
README
View file @
121f4956
...
@@ -56,25 +56,38 @@ If you're running BIRD, you're on your own.
...
@@ -56,25 +56,38 @@ If you're running BIRD, you're on your own.
### Run sroamd
### Run sroamd
You need to specify:
Choose an IPv4 prefix (at least /24) and an IPv6 prefix (at least /56) for
your roaming clients.
* the network prefixes used for roaming (`-P`);
* the nameserver(s) announced over DHCPv4 and RA (`-N`);
v4prefix=192.168.44.0/24
* the local UDP port used by the flooding algorithm (`-f`);
v6prefix=2001:0db8:1234::/48
* the address and port of two or three remote peers (`-F`) (optional);
* the set of interfaces used for roaming.
Choose a set of nameservers to advertise to your clients:
In our example, you could say:
ns1=192.168.43.43
ns2=2001:0db8:4343::43
sroamd -P 2001:db8:4444::/48 -P 192.168.44.0/24 \
-f 4444 -F [2001:db8:4444::1234]:4444 \
Pick one or two stable sroamd instances, call them A and B, to act as
-N 2001:db8:1234::42 -N 10.0.0.42 \
flooding servers:
wlan0
On A:
The flooding algorithm relies on normal unicast traffic, so the sroamd
instances need not be neighbours. There is no automatic peer discovery,
sroamd -P $v4prefix -P $v6prefix -N $ns1 -N $ns2 -f 4444 wlan0
you must specify enough remote peer addresses to make sure your network
remains connected even when some of them crash.
On B:
sroamd -P $v4prefix -P $v6prefix -N $ns1 -N $ns2 -f 4444 -F A:4444 wlan0
On all other sroamd instances:
sroamd -P $v4prefix -P $v6prefix -N $nameserver -f 4444 -F A:4444 -F B:4444 wlan0
Notes:
* you must use the same prefixes (-P) on all instances, but you may use
different nameservers;
* the servers need not act as DHCPv4 and RA servers, in which case they
need not run babeld or hostapd and you should omit the interface name.
### Find the bugs
### Find the bugs
...
...
This diff is collapsed.
Click to expand it.
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