---------- Forwarded message ----------
From: <mesh-dev-owner@lists.sudoroom.org>
Date: Sat, Feb 21, 2015 at 4:21 AM
Subject: mesh-dev post from jernej@kos.mx requires approval
To: mesh-dev-owner@lists.sudoroom.org


As list administrator, your authorization is requested for the
following mailing list posting:

    List:    mesh-dev@lists.sudoroom.org
    From:    jernej@kos.mx
    Subject: Re: [mesh-dev] Web admin of roof to roof nodes [another ramble]
    Reason:  Post by non-member to a members-only list

At your convenience, visit:

    https://lists.sudoroom.org/admindb/mesh-dev

to approve or deny the request.


---------- Forwarded message ----------
From: Jernej Kos <jernej@kos.mx>
To: Mitar <mitar@tnode.com>, Marc Juul <juul@labitat.dk>, mesh-dev@lists.sudoroom.org
Cc: 
Date: Sat, 21 Feb 2015 13:21:05 +0100
Subject: Re: [mesh-dev] Web admin of roof to roof nodes [another ramble]
Hello!

On 21. 02. 2015 09:36, Mitar wrote:
> the most reliably in that way. I do not know details, though, what all
> issues we had that we had to move to this setup. CCing Kostko who might
> be able to provide more information here.

Indeed, this was a problem with olsrd implementation of OLSR which used
neighbour IPs as part of link identification and we had some strange
routing issues because of using same IPs on multiple interfaces.

We now use one IP for each interface which participates in routing and
we use the first such IP as the Router ID.

Note that babel uses IPv6 link-local addresses for neighbours, so it
uses different IPs anyway and this will probably not be such a problem
in this case. But I would still refrain from using the same IP on
multiple interfaces.


Jernej



---------- Forwarded message ----------
From: mesh-dev-request@lists.sudoroom.org
To: 
Cc: 
Date: Sat, 21 Feb 2015 04:21:20 -0800
Subject: confirm 4bacb63cb6f3b747fd43348ca7faa4410c84a424
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message.  Do this if the message is
spam.  If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list.  The Approved: header can also appear in the first line
of the body of the reply.