OLSR mesh GUI $400 {awarded}

pcatiprodotnet

Can you do me a favor and test RC1 and let me know what we need to wrap up? Somewhat unsure what bugs are still lingering…. Thanks!!

I hope to find some free time for testing RC1 within a week. I must build a spare PC to test it, since all of our WRAP units are currently deployed in production because we're very pleased using pfSense along with the olsr & dnsmasq config files I copy/pasted into this post ( http://forum.pfsense.org/index.php?topic=677.msg8294#msg8294 ). If the olsr gui was updated just a little more to be capable of auto-generating configs like these, I could do some quick and easy testing on our production mesh.

Also, I solved issue #17 by using dnsmasq, instead of dhcpd, to allow a "manually entered Netmask" to function without errors; could the solution be implemented as described in this post http://forum.pfsense.org/index.php?topic=677.msg8294#msg8294

@pcatiprodotnet:

17. Please allow in the DHCP GUI, a manually entered Netmask, when OLSR is enabled on that interface.
(the purpose of this is to force a node's non-olsr ad-hoc wifi clients to route through the current node as a gateway onto olsr, so it may communicate with nodes that are otherwise out-of-range for non-olsr wifi clients when they use the netmask of the interface).

@pcatiprodotnet:

We'll up the total bounty payout to $400 if the issues directly above can be resolved within a week, and made available in an imbedded snapshot/beta shortly thereafter.

Thank you,

Pete
pc@ipro.net
Internet Professionals, LLC

sullrich

Any updates? I would like to get this sucker sealed and delivered as it is one of the holdupds of release.

pcatiprodotnet

Will test latest snapshot this weekend; we just got a few extra WRAP units.

sullrich

Thanks!!

pcatiprodotnet

Using Embedded Snapshot 7-10-06. I get this on a blank white page after checking olsr and pressing submit…
Warning: Invalid argument supplied for foreach() in /etc/inc/services.inc on line 1134 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/services.inc:1134) in /usr/local/www/pkg_edit.php on line 35

sullrich

Believe it or not, this bug wasn't my fault ;D

run this from a shell:

/etc/rc.conf_mount_rw
fetch -o /etc/inc/services.inc http://www.pfsense.com/~sullrich/services.inc
/etc/rc.conf_mount_ro

Then test again.

Altern

So, the maker of the OLSR GUI was actually awarded $400?

billm

@Altern:

So, the maker of the OLSR GUI was actually awarded $400?

Yes

thedan

@sullrich:

Sounds good. We'll be releasing RC1 soon and as soon as that happens I would like to wrap up the OLSR and get that solid.

Can someone please clarify whether or not the OLSR gui is "solid" yet? I have been struggling to get a mesh working between two WRAP boards, a linux box and a windows box. One of the WRAP boards is to be a DHCP server for the other nodes. Currently there is no route to the Internet but that may change. Any advice would very much be appreciated…

pcatiprodotnet

" So, the maker of the OLSR GUI was actually awarded $400? "
Hi thedan,
The OLSR GUI is not quite finished yet, but that is mostly my fault for not having free time lately test changes and post debug suggestions to Sullrich. And, it may be another month or two before I get such free time again. In the mean time, anyone may feel free to test the current OLSR GUI and post bug reports here. Rest assured we have not given up on this bounty.
If you need a solid OLSR immediately, please see the following forum post for help setting it up manually (not using the GUI)…
http://forum.pfsense.org/index.php/topic,2353.0.html
Thank you,
-Pete

thedan

Thanks very much Pete. I can confirm that your OLSR gui appears to be working in that it generates proper configuration files

I managed to get OLSRd working manually, though I still have a few problems with dnsmasq.

I personally would find it useful though if it supported more OLSR options such as HELLO/MID/HNA/TC values, MPR coverage and hysteresis… or at the very least, if it could somehow not overwrite custom configuration changes to such settings.

-Dan

pcatiprodotnet

I personally would find it useful though if it supported more OLSR options such as HELLO/MID/HNA/TC values, MPR coverage and hysteresis… or at the very least, if it could somehow not overwrite custom configuration changes to such settings.

Agreed.