[Olsr-users] Basic problem? router_id from loopback

[Velt, R. (Ronald) in 't]

Hi Andreas,

(See below)

From: Olsr-users <(spam-protected)> On Behalf Of Andreas Martens1
Sent: vrijdag 26 februari 2021 15:43
To: (spam-protected)
Subject: [Olsr-users] Basic problem? router_id from loopback

Hello all,

I've been trying to get this working for some time and I feat I'm just not understanding something... This might be a n00b problem!

I have a group of nodes in a few different wireless networks. Because they have an IP address for each NIC I wanted to give them a unique IP address that could be routed across all the networks.
So I added an IP address to the lo device:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet 172.20.0.1/32 scope global lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
I then added [interface=lo] to the olsrd2.conf:
[global]
        fork 1
[olsrv2]
        originator default_accept
        nhdp_routable true
        tc_interval 8.0
        tc_validity 40.0
[nhdp]
  mpr *
[interface=lo]
[interface=emane14]
        hello_interval 2.0
        hello_validity 10.0
        l2default rx_bitrate 600k
        multicast_v4 224.0.0.109
        bindto 192.168.15.1
        bindto default_reject

[interface=emane13]
        hello_interval 2.0
        hello_validity 10.0
        l2default rx_bitrate 600k
        multicast_v4 224.0.0.109
        bindto 192.168.14.1
        bindto default_reject

[interface=emane11]
        hello_interval 2.0
        hello_validity 10.0
        l2default rx_bitrate 600k
        multicast_v4 224.0.0.109
        bindto 192.168.12.1
        bindto default_reject

but this seems to have stopped it working, as far as I can tell it's using 127.0.0.1 as its router_id now instead of the id of a NIC.

What does the config need to look like so it distributes routes to the 172.20.0.0/32 addresses configured on loopback?



cheers,
Andreas

Deferring to Henning for an authoritative answer, of course, but judging from the output of

# olsrd2_static --schema=olsrv2.originator ,

you should get rid of the ‘originator default_accept’ in the [olsrv2] stanza:

21:39:22.109 WARN(olsrv2_old_lan) src/olsrv2/olsrv2_old_lan/old_lan.c 147: Old LAN plugin does add support for the deprecated olsrv2/lan config option

    originator (list)

    Default value:

        '-127.0.0.0/8'

        '-224.0.0.0/12'

        '-::1'

        '-ff00::/8'

        'default_accept'

    Parameter is an apache2 style access control list made from a list of network addresses of the following types:

IPv4, IPv6

        (the address can have an optional prefix)

        Each of the addresses/prefixes can start with a '+' to add them to the whitelist and '-' to add it to the blacklist (default is the whitelist).

        In addition to this there are four keywords to configure the ACL:

        - 'first_accept' to parse the whitelist first

        - 'first_reject' to parse the blacklist first

        - 'default_accept' to accept input if it doesn't match either list

        - 'default_reject' to not accept it if it doesn't match either list

        (default mode is 'first_accept' and 'default_reject')

    Description:

        Filter for router originator addresses (ipv4 and ipv6) from the interface addresses. Olsrv2 will prefer routable addresses over linklocal addresses and addresses from loopback over other interfaces.

If I interpret this correctly, the default setting for ‘originator’ will ensure that 127.0.0.1 is filtered out and the address you added to the loopback interface gets selected.

Cheers,

Ronald





























Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20210228/a910234b/attachment.htm>