OLSR Tips and Tricks
I've been fighting with olsrd lately and decided to start a thread where I can share information I wish was all in one place when I started.
A way to see what the olsr.conf file looks like, go to Diagnostics>Edit File. At the top of the page enter "/var/etc/olsr.conf" without the quotes and click on load. I have tried to save changes through the Edit File GUI but they don't seem to stick. It's as if there is another configuration file being used to change olsr.conf back to previous settings.
hoba last edited by
All config files are created dynamically when needed (changing IP, changing package config, etc). This will overwrite your changes.
jeroen234 last edited by
setup olsr tru services olsr
I finally got my pfSense mesh node to work. I have a computer using two LAN and one WLAN cards, running pfSense, and using it as an OLSR gateway to the internet. I have two windows computers running OLSR.exe and they seem to be relaying packets rather well. The problem I was having was with a mesh node I made with pfSense who's only job was to relay packets as an MPR. I have a WLAN card and a LAN card in it, the WLAN card is set to WAN and the LAN card is set to LAN. The reason I had so much trouble getting it to relay packets is because I had disabled the firewall in System>Advanced. After enabling the firewall it started relaying packets properly. I wanted to access the WebConfig through the wireless card so I put a "pass any" rule in the WAN firewall rules table.
I've found that on my gateway, if I check the box in the OLSR page that says "Enable Dynamic Gateway" clients on both the WLAN and LAN will no longer access the internet. I have "Announce self as dynamic gateway" checked but have left "Enable Dynamic Gateway" unchecked and it seems to work good like that.
Ok, I got Traffic Shaper and Captive Portal to work on my gateway computer. I had to put these rules in the Allowed IP Addresses tab in the Captive Portal page:
any > 10.8.100.1 (WiFi card IP address)
any > 10.8.100.255
10.8.100.255 > any
These are necessary for the gateway to recognize its neighbors (MPR's), otherwise all the neighbors will attempt to be redirected to the captive portal when getting/sending topology information.
I had to re-run the Traffic Shaper Wizard after I got everything set up the way I wanted it, otherwise nothing would get through the gateway.
I kept having intermittent problems so I changed my setup. I think having OLSR and Captive Portal and Traffic Shaper, etc, running on one machine was too much for it. So now the computer that was a pure MPR is now an OLSR "access point" of sorts. I have OLSR bound to WAN, and LAN is bound to the wired LAN card with a cable running to my firewall/router which acts as captive portal, bandwidth manager, and other things. I have OLSR turned off on the firewall/router computer.
I had gotten everything working good but when I turned on the Captive Portal I had a problem. The https captive portal page would come up and when I typed in my name and password the browser would try to reach my homepage and then get redirected to the Captive Portal page again. This happened every time I clicked on the Continue button on the captive portal page.
I finally got it to work by putting the MAC address of the "access points" LAN card in Pass-through MAC. I also had to put a check next to Disable MAC Filtering under the Captive Portal tab.
Now when I start up my browser and the homepage tries to come up I get redirected properly to the captive portal and then get directed to my homepage after logging in. Everything seems more stable with this setup.