[Olsr-dev] Idea for small OLSR improvement

Markus Kittenberger (spam-protected)
Sun Apr 25 08:39:19 CEST 2010

definetely sounds like a bug,..

my own (monitored) olsrds definitely dont do it,... *G


On Sun, Apr 25, 2010 at 5:22 AM, Mitar <(spam-protected)> wrote:

> Hi!
> On Sat, Apr 24, 2010 at 7:25 PM, Markus Kittenberger
> <(spam-protected)> wrote:
> > if so, there would be non influence on olsr/routing from any layer <=2
> > (which means you problem is probably inside olsr and/or its config)
> Yes. I also believe so. For example, we added some new reporting about
> connectivity loss from the mesh (which we measure with number of time
> route to the gateway drops) and one node with VPN uplink + direct ~1.0
> ETX WiFi peering with another node with VPN uplink is reporting
> connectivity loss from time to time. There was no stuck beacons errors
> on any of those nodes, they use different ISPs for VPN tunnels and
> just the first one reported connectivity loss even with having (at
> least two - its own VPN tunnel and direct peer without connectivity
> loss reported) very good connections to the mesh. Why OLSR dropped the
> connection to the mesh and not just changed its peering node? (It is a
> rhetorical question. But I do believe there is some bug somewhere.)
> Mitar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100425/6635264e/attachment.html>

More information about the Olsr-dev mailing list