[olsr-dev] Suggestion: more command-line options

Andreas T√łnnesen (spam-protected)
Thu Jan 5 09:19:52 CET 2006


IMO the configuration file you link to is a bit more trivial than the
olsrd config file. In our config we have multiple grouped "subsections"
(such as all the per interface options, plugins with parameters etc.). The
way I see it implementing all these options as command line options will
make for a rather big and messy CLI :-)
As of now the command line interface should provide most of the common
options, but having a look at it now I see that we have not been updating
it with new features for some time. So I guess we'll have a go at that -
this should bring things such as LQ options to the CLI. We'll have a look
at the rest of the options as well, but I cannot promise that we will add
each and every configureable option to the CLI..

- Andreas

> Hi all,
> First of all, congrats to the OLSR team on releasing v0.4.10.  A giant
> leap
> forward in MANET routing efficiency I'm sure.
> Now my suggestion for olsrd.  I'd like to be able to call olsrd with more
> command-line options.  I use the dhcp/dns program Dnsmasq under OpenWRT
> and
> I love it because it is so well suited to embedded environments.  With
> Dnsmasq every config-file option is also supported as a command-line
> option.
> This means dnsmasq can be executed with options that are shell environment
> variables.  So it can be extensively customised with a web-interface GUI
> with no need to create a temp config file.  The web interface just passes
> it's parameters directly to the shell command as environment variables.
> Check out the man pages for dnsmasq and dnsmasq.conf and see how the
> command-line and config-file options are identical:
> http://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
> http://thekelleys.org.uk/dnsmasq/docs/dnsmasq.conf.example
> Because olsrd has comparatively few command-line options, GUI interfaces
> often have to dynamically create the config file as a temporary file to be
> able to configure certain options.  I think this is a bit of an ugly way
> to
> go about configuring olsrd.
> Would it be very difficult to include most or all of olsrd's config-file
> options as command-line options also?
> Cheers,
> Dan
> -------------
> View my blog:
> http://freenetjazz.blogspot.com
> _______________________________________________
> olsr-dev mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-dev

More information about the Olsr-dev mailing list