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: Re: [B.A.T.M.A.N.] single IP for multiple interfaces
Date: Tue, 20 Nov 2007 15:08:05 +0100 [thread overview]
Message-ID: <200711201508.06076.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4742E4E6.1010802@absorb.it>
> sure? (I'm in no way an expert, its an honest question.)
> root@OpenWrt:~# ip route
> 192.168.1.48 via 192.168.1.188 dev ath1 metric 7
> 192.168.2.40 via 192.168.1.188 dev ath1 metric 6
> 192.168.1.49 via 192.168.1.188 dev ath1 metric 4
> 192.168.2.42 via 192.168.1.188 dev ath1 metric 7
> 192.168.1.51 via 192.168.2.172 dev eth0 metric 2
> so there are interfaces shown in the routes, the kernel should recognize
> them, what else they are for?
As Axel already mentionned: These are the outgoing interfaces which you can
specify but the problem arises if your neighbor node has 2 interfaces as
well. How are you going to seperate these ? Normally you do so by using 2
different IP addresses to send traffic to one or the other interface. But if
you only have one address ...
> PS: Invited Sebastian Hagen who programmed the patch to join the
> discussion, hope he will help me/us with more details
Good idea. :-)
Greetings,
Marek
next prev parent reply other threads:[~2007-11-20 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 5:22 [B.A.T.M.A.N.] problem starting batmand (v799) rene
2007-11-20 9:08 ` Axel Neumann
2007-11-20 10:31 ` rene
2007-11-20 10:59 ` [B.A.T.M.A.N.] single IP for multiple interfaces (was: Re: [B.A.T.M.A.N.] problem starting batmand (v799)) Marek Lindner
2007-11-20 11:29 ` [B.A.T.M.A.N.] single IP for multiple interfaces rene
2007-11-20 12:24 ` Marek Lindner
2007-11-20 13:45 ` rene
2007-11-20 14:08 ` Marek Lindner [this message]
2007-11-20 11:32 ` [B.A.T.M.A.N.] problem starting batmand (v799) Axel Neumann
2007-11-20 11:39 ` [B.A.T.M.A.N.] single IP for multiple interfaces rene
2007-11-20 12:31 ` Axel Neumann
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=200711201508.06076.lindner_marek@yahoo.de \
--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