From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: AW: [B.A.T.M.A.N.] wrong ip rules
Date: Wed, 14 Nov 2007 07:30:15 +0000 (GMT) [thread overview]
Message-ID: <470056.58415.qm@web26904.mail.ukl.yahoo.com> (raw)
Hi,
> 6598: from all to 104.0.0.0/8 lookup olsr
> 6599: from 104.0.0.0/8 lookup olsr
> 6598: from all to 104.0.0.0/8 lookup olsr
> 6599: from 104.0.0.0/8 lookup olsr
> 6802: from 104.0.0.0/8 lookup 68
> batmand delete olsr-rules and set "from 104.0.0.0/8 lookup 68"!?
which olsr-rules are deleted ? I can't see a difference there.
In table 68 is the batman default route. All interfaces not controlled
by batmand are routed towards this routing table. If you don't want
that OLSR traffic is routed into the batman default route you have
2 choices:
- You deleted the OLSR rules after each batmand start (hackish).
- You use the --no-policy-routing option and set all rules by
yourself. This option allows a tight integration into a firmware and
full control of the policy routing.
Why does batmand not recognize OLSR interfaces and
ignores them ? We simply could not find a good solution for
this kind of detection but we are open to suggestions. ;-)
Greetings,
Marek
__________________________________ Ihr erstes Fernweh? Wo gibt es den schönsten Strand? www.yahoo.de/clever
next reply other threads:[~2007-11-14 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 7:30 Marek Lindner [this message]
2007-11-14 12:57 ` AW: [B.A.T.M.A.N.] wrong ip rules Aaron Kaplan
2007-11-14 16:08 ` tetzlav
2007-11-20 16:33 ` Marek Lindner
2007-11-21 15:20 ` [B.A.T.M.A.N.] batman 0.3 and batmand-exp-0.3 Predrag Balorda
2007-11-21 20:00 ` Axel Neumann
2007-11-14 14:49 ` AW: [B.A.T.M.A.N.] wrong ip rules / tunnel crashes tetzlav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=470056.58415.qm@web26904.mail.ukl.yahoo.com \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox