[Olsr-users] Looking for simple OLSRd2 config
Henning Rogge
(spam-protected)
Wed Apr 29 19:51:30 CEST 2015
On Wed, Apr 29, 2015 at 7:43 PM, Bernd Naumann <(spam-protected)> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 04/29/2015 07:17 PM, Henning Rogge wrote:
>> On Wed, Apr 29, 2015 at 6:55 PM, Bernd Naumann <(spam-protected)>
>> wrote:
>
>>> ############################################### # cat
>>> /etc/config/dlep_radio
>> ... I don't think you need the dlep_radio at all.
>
> Ok, I just followed the wiki. So I will disable dlep.
Okay, I have to clear up the wiki about this...
dlep_radio and olsrd2 are two applications, both based on OONF... but
you don't need both, they are just two programs using the same API.
>>> ############################################### # cat
>>> /etc/config/olsrd2 config global option 'failfast' 'no'
>>> option 'pidfile' '/var/run/olsrd2.pid' option 'lockfile'
>>> '/var/lock/olsrd2'
>>>
>>> config log option 'syslog' 'true' option 'stderr'
>>> 'true' option 'file' '/var/log/olsrd2.log' option
>>> 'info' 'all' option 'debug' 'all'
>>
>> This will spam your logfile pretty quickly... don't complain when
>> you have a few megabytes of log after a while.
>
> OK :)
comment out "option info all" and "option debug all" to get the
warnings... only activate info/debug either for a specific subsystem
or for when you debug a node.
see "olsrd2 --schema=log.info" or "olsrd2 --schema=log.debug" for the
possible options.
>>
>>> config telnet option 'port' '2009'
>>>
>>> config olsrv2 list 'lan' '::/0' # list 'lan'
>>> '0.0.0.0/0'
>>>
>>> config interface option 'ifname' 'loopback' #
>>> option 'lan' '10.0.2.1/24'
>>
>> the "lan" option is not valid for the section "interface".
>
> Thats the default config from the package. I have no f***ing clue what
> I'm doing ;)
Okay, I thought I had cleaned this up, but it seems a few things
slipped when I worked on the UCI scripts.
>>
>> Maybe you are thinking about setting an IP address on the loopback
>> in the network config?
>>
>>> config interface list 'ifname' 'wlan0'
>>>
>>> config interface list 'ifname' 'wan' option 'ignore'
>>> '1' # option 'rx_bitrate' '100M' # option
>>> 'tx_bitrate' '100M' # option 'signal' '-20'
>>>
>>> config interface list 'ifname' 'lan' option 'ignore'
>>> '1' # option 'rx_bitrate' '1G' # option 'tx_bitrate'
>>> '1G' # option 'signal' '-10'
>>
>> So you want both "lan" and "wan" a mesh interface?
>
> That is also in the default config, and it's ignored...
> But I can delete that interface config...
Ahh okay, I forgot about the "ignore" option... thats something done
by the "init" script, not by olsrd2 ;)
>>> ###############################################
>>>
>>>
>>> dlep and olsrd2 start up via openwrt init.d scripts.
>>
>> Why do you want to run dlep_radio?
>
> Like I said, I don't know... For what I have understood from the wiki,
> I had to compile it... but I can remove that, too.
There are also makefile targets just to compile a single thing. e.g.:
make olsrd2_static
>>
>>> So my actual questions are:
>>>
>>> * Where do I configure an ip-address? Via config/network (or
>>> with `ip`), OR via config/olsrd2 ?
>>
>> the idea is that you set the IP addresses via the network config.
>> Olsrd2 will monitor all its interfaces and automatically grab
>> addresses that are allowed (you can set patterns in the
>> olsrd2-config what is allowed).
>
> k, thx!
>
>>
>> run "olsrd2 --schema=interface.ifaddr_filter" for the rules which
>> addresses will be included in Hellos and "olsrd2
>> --schema=olsrv2.routable" for the rules which addresses will be
>> "routable" and distributed "end-to-end".
Both "ifaddr_filter" and "routable" are Apache2-style ACLs... with a
black/whitelist of IPs/prefixes. This should make it possible to use
the same configuration for most nodes.
>>> * How do I check for mesh-neighbours? From olsr I know `wget -qO
>>> - http://127.0.0.1:2006/neighbours`...
>>
>> Try the telnet port of olsrd2 (see config above ^^). e.g.:
>>
>> echo /nhdpinfo neighbor | nc 127.0.0.1 2009
>>
>> or connect to the telnet port and use the "help" command... e.g.
>>
>> "help" (for generic help and a list of available commands) "help
>> <command>" for help text for an available command.
>
> Thanks a lot!
You are welcome.
Henning
More information about the Olsr-users
mailing list