I have no idea what packages the Debian based maintainers choose to include or what they may or may not select when they compile the kernel for the pi. The routes will be updated automagically as nodes enter or exit the network. Execute the following steps on the remaining Pis. If everything goes well, you should be on your way to a mesh network. And now we fire up babeld: # babeld wlan0 &. As you repeat these steps on each Pi, give the next one a different address, for example 192.168.13.34, and so forth.Ħ. Right now we need to manually assign each Pi a unique ip address: # ip addr add 192.168.13.33 dev wlan0. Now let’s configure the network: # iwconfig wlan0 mode ad-hoc channel 11 essid "mesh". Power up the wifi dongle: # ip link set wlan0 up. Now your Pi should be up and running again and the wifi dongle should not be powered up. To make sure your wifi card doesn’t associate on boot, execute # systemctl disable & reboot if you followed the previous tutorial.ģ. First we need to undo some of the previous steps used for a managed wireless connection. Note: If the Pi complains about system architecture, just change it in the PKGBUILD.Ģ. Before you unplug the ethernet, install this package # packer -S babeld. It helps if you do not have an ethernet connection and are just working to set up the wifi connection first on the target device.ġ. Setting up mesh networking on the Pi’s is fairly straight-forward. Now let’s take the next step and set up an ad-hoc, mesh network! Setting up Wireless Networking (ad-hoc) While no amazing feat, it was an important test to see how well the drivers functioned for the wifi dongle. In my previous post I outlined how to get wireless networking working on the Pi’s.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |