892
edits
Difference between revisions of "Mesh/Relay setup"
→Test the broker
m |
|||
| Line 171: | Line 171: | ||
== Test the broker == | == Test the broker == | ||
To test the broker you need to install tunneldigger client on a different system. Ensure you have the L2TP modules loaded on your client system. | |||
Install tunneldigger client requirements on you client system: | |||
sudo aptitude install libnl-dev build-essential git | |||
Download tunneldigger on client system: | |||
cd | |||
git clone https://github.com/wlanslovenija/tunneldigger.git | |||
Compile tunneldigger client: | |||
cd tunneldigger | |||
make | |||
Ensure that the tunneldigger broker is running on your relay node and run the tunneldigger client: | |||
sudo ./l2tp_client -f -u foo -l <ip_of_your_relay_node>:<53> -i l2tp | |||
The tunneldigger client should inform you when the tunnel has been established. This is what you'd expect to see: | |||
l2tp-client: Performing broker selection... | |||
l2tp-client: Selected 192.157.221.200:53 as the best broker. | |||
l2tp-client: Tunnel successfully established. | |||
If you use the -L option for l2tp_client, you may get an error from the broker like: | |||
RTNETLINK answers: Invalid argument | |||
Don't worry about it. The broker is attempting to clear out a sometimes non-existent traffic control rule using the command: | |||
/sbin/tc qdisc del dev <tunnel_iface> root handle 1: htb default 0 | |||
This doesn't harm anything, but if you want to fix the behavior, look in traffic_control.py in the reset function. | |||
== Configure the broker to auto-start == | == Configure the broker to auto-start == | ||