[Olsr-dev] olsrd-0.6.1 deletes default route on MacOS X

Markus Kittenberger (spam-protected)
Sat Dec 11 15:02:26 CET 2010

On Sat, Dec 11, 2010 at 2:32 AM, Mitar <(spam-protected)> wrote:

> Hi!
> On Sat, Dec 11, 2010 at 1:49 AM, Markus Kittenberger
> <(spam-protected)> wrote:
> > furthermore usually policy routing is absolutely sufficient to route your
> > own traffic different than mesh traffic,..
> But not to prevent for example leaking into the mesh.

it can not stop knowing olsrd about this announcements,.
but you could stop you from using them

the point is with policyrouting you can limit which routes YOU will use that
are available in the mesh,.. (without breaking anything in the mesh)
and anyone can use different rules, without problems, ((as long as he only
limits his own usage, but not the forwarding))
(and ofcourse you can have the same config on all nodes aswell, but youdon`t
need to,..)

with filtering you can reasonable only filter the SAME on ALL nodes,.. else
you will break at least "something" in an linkstate network

BUT if you can configure the same filter rules on ALL nodes, than you could
easily stop announcing bullsh*t (e.g. there anyways,.

btw i see useful scenarious for filtering, but i see (more)
unwanted/unexpected results aswell,..
that`s why i propose letting olsrd route everything, and just deciding
locally what routes u want to use,.. #0

e.g. we have added a second dedicated iprange to our networks years ago, if
we would have used olsrd filtering before, we would have to change the
filter on all nodes before being able to add the second range,.. (which
would have been a very big problem!!)

and again, if you have easy access/control to all nodes, you don`t really
need filtering,..
and if NOT i'm not sure if you benefit more from this as u might suffer,..

as e.g. the pepole that currently announce bullsh*t, might also filter
bullsh*t in the future,..

We for example allow only dedicated IPs from our IP range in the mesh.
> Otherwise there would be chaos: multiple users announcing their
> different networks but same IP ranges into the mesh and then depending
> on where you are in the mesh you would get different network.

and you want to solve this by NOT reaching this networks anymore (from

what is the benefit (except no chaos)


#0 combined with smartgateway (local policyrouting) is imho 100% sufficient
to let you being unaffected from any olsr announcement bullsh*t, ..
(except someone using the same dedicated ip as you do,..)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20101211/91c68075/attachment.html>

More information about the Olsr-dev mailing list