OLSR mesh GUI $400 {awarded}
-
I just tried to enable olsr and got this error page…
Warning: fopen(/usr/local/etc/olsrkey.txt): failed to open stream: Read-only file system in /usr/local/www/pkg_edit.php(172) : eval()'d code on line 1 Warning: fwrite(): supplied argument is not a valid stream resource in /usr/local/www/pkg_edit.php(172) : eval()'d code on line 1 Warning: fclose(): supplied argument is not a valid stream resource in /usr/local/www/pkg_edit.php(172) : eval()'d code on line 1 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/pkg_edit.php(172) :
eval()'d code:1) in /usr/local/www/pkg_edit.php on line 186Will try again next beta snapshot release. Thanks,-Pete
-
This is already fixed in CVS.
-
explain what the config entries looks like
I haven't attempted to set OLSR up without a gui yet.
The OLSR windows version has an easy installer and a decent gui to study.
Perhaps it also writes config files that are compatible with other platforms? -
Issues I've noticed so far that are needed to finish up this bounty …
1. Need a Check box for "Link Quality Extensions".
x2. Tabs/Check-boxes for capability to enable OLSR on multiple Network Interfaces. {done: use Ctrl key to multi-select}
3. I tried to enable and view the olsr web stats but it was just an empty page; am I using this correctly?
4. When olsr is checked enabled, alter the DHCP server/forwarding GUI so that DHCP may be enabled on wan/all interfaces.
5. For HNA (Dynamic Internet gateway) to function, I read on the olsr-users mailing list that the Wan Gateway should
be unset, which is currently not possible in the gui. Is this correct? Perhaps there is more to making this work.Thanks,
-Pete -
2. Tabs/Check-boxes for capability to enable OLSR on multiple Network Interfaces.
Uhh that works now. Hold down the CTRL key and select the interfaces you want. I'll look into the others.
-
Good grief, I'm sorry I had no idea the Ctrl key could be used like that. Thanks, -Pete
-
Sounds like we need to add a blurb under the interface control describing this behavior.
-
Issues I've noticed so far that are needed to finish up this bounty …
1. Need a Check box for "Link Quality Extensions".
x. Tabs/Check-boxes for capability to enable OLSR on multiple Network Interfaces. {done: use Ctrl key to multi-select}
3. I tried to enable and view the olsr web stats but it was just an empty page; am I using this correctly?
4. When olsr is checked enabled, alter the DHCP server/forwarding GUI so that DHCP may be enabled on wan/all interfaces.
5. For HNA (Dynamic Internet gateway) to function, I read on the olsr-users mailing list that the Wan Gateway should
be unset, which is currently not possible in the gui. Is this correct? Perhaps there is more to making this work.Thanks,
-PeteAll of these with exception of #3 should be resolved.
Please do a cvs_sync.sh RELENG_1 and test.
Thanks!
-
Thanks Scott! We plan to run a small test tomorrow at work with 3 pfSense ad-hoc olsr nodes
(placing node#1 & node#3 out of range of each other) and several non-olsr wi-fi & lan clients.Here are a couple replies I received from the olsr-users mailing list so far regarding olsr configuration…
Quote: " On OLSR nodes, you'd leave gateway unset, as the HNA announcement
of 0.0.0.0 sets the default gateway on all nodes that hear it. For DNS, I
have it manually set, though there's a plugin for this apparently in OLSR. "
--Me: Is he referring to the "Nameservice" plugin? Automatically setting DNS to the HNA would be great.--Me: I want our olsr nodes to also serve Non-olsr client PCs.
--Should the node's DHCP server serve the node's own IP address as
--the Gateway & DNS to the Non-olsr client PCs?
Quote: " Yes, at least that's how I've setup our network. "Quote: " If nodes dont see each other (dont show up in the list), then
there is propably something wrong with their broadcast addresses. "Thank you, -Pete
-
I tried that upgrade command but it gave the following errors:
(I am running beta3 embedded)cvs_sync.sh RELENG_1
Setting CVS_IP to cvs.pfsense.com
Cannot find cvsup, pkg_add in progress
/usr/local/sbin/cvs_sync.sh: /usr/sbin/pkg_add: not found
Cannot find cvs, fetching static cvs…
fetch: http://www.pfsense.com/~sullrich/extra/cvs: Temporary Redirect
chmod: /usr/bin/cvs: No such file or directory
Syncing with pfSense.com
Checking out RELENG_1
mkdir: /root/pfSense: Read-only file system
cd: can't cd to /root/pfSense//..
mkdir: /root/pfSenseCO: Read-only file system
cd: can't cd to /root/pfSenseCO/
cd: can't cd to /root/pfSenseCO//
cd: can't cd to /root/pfSenseCO//
Installing new files...cd: can't cd to /root/pfSenseCO//pfSense
x .
x .cshrc: Can't open '.cshrc': File exists
x .login: Can't open '.login': Read-only file system
x .profile: Can't open '.profile': File exists
x .shrc: Can't open '.shrc': Read-only file system
x .tcshrc: Can't open '.tcshrc': Read-only file system
x .hushlogin: Can't open '.hushlogin': Read-only file system
CVS Sync CompleteRestarting webConfigurator... done.
-
You cannot cvs_sync.sh on embedded. Wait for the next snapshot or beta4.
-
No problem. I think we can go ahead with tests today; it seems functional.
I did get the olsr stats (issue#3) to function; I far as I can recall I don't think I did anything different.
A couple more issues…
6. I have noticed that sometimes when I click [Save] on the OLSR configuration page it fails to start OLSR.
I would check the logs and there would be No listing for "olsrd[4494]: olsr.org - 0.4.10 successfully started".
7. It also seems OLSR won't start on boot so far; I must open the olsr config page and [Save] to get it running.
Thanks,-Pete -
Alright, I've made some monitor adjustments to the start code. Let's see what happens on next testing image.
-
Another note, I have the feeling that issue#3 may be related to issues#6 & #7.
-
Yep, sure is.
I just fixed this one as well.
-
" You cannot cvs_sync.sh on embedded. Wait for the next snapshot or beta4. "
Will do. We'll run our final tests after the next snapshot is released.I was curious, on the olsr GUI, is the "Enable Secure Mode" referring to the "Secure OLSR Plugin"?
I haven't tried that feature yet, but it should prove quite useful.Are the following plugins in pfSense yet?
"Nameservice" – we hope to use this to automatically assign DNS to the HNA (gateway), so no need to hard-code dns.
"Dot topology information plugin" -- for visually rendering the mesh; just icing for now, but would be handy after the mesh grows.Thank you, -Pete
-
" You cannot cvs_sync.sh on embedded. Wait for the next snapshot or beta4. "
Will do. We'll run our final tests after the next snapshot is released.I was curious, on the olsr GUI, is the "Enable Secure Mode" referring to the "Secure OLSR Plugin"?
I haven't tried that feature yet, but it should prove quite useful.Are the following plugins in pfSense yet?
"Nameservice" – we hope to use this to automatically assign DNS to the HNA (gateway), so no need to hard-code dns.
"Dot topology information plugin" -- for visually rendering the mesh; just icing for now, but would be handy after the mesh grows.Thank you, -Pete
LOL – yes, secure mode is what you wanted? The other items wheren't mentioned in the original bounty?
-
Back when I posted the bounty I knew too little about olsr "under the hood" so I was
a bit inspecific "… add great olsr extensions ..." which I realize is really too open ended.
I figured the dynamic gateway plugin would also set the dns, seemed logical but alas.
Please, is it going to be too much trouble to add the "Nameserver plugin"?
Thank you, -Pete -
Not at all, I'm just giving you grief. I'll get it rolling this weekend.
-
Issues encountered today while testing (still using beta3 embedded)…
8. When I "Enable Dynamic Gateway", the node doesn't show up as HNA on the other node's stats.
I tried to verify that " HNA4 { ... "0.0.0.0 0.0.0.0" } " existed in olsrd.conf but I couldn't find the file.
9. If I attempt to enable olsr on both Lan and Wan, it starts for a few seconds, both interface's IPs briefly
appear in the node list of other olsr systems, then the olsr stops or crashes, and they both disappear.
Thanks,-Pete