public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: rene <batman@absorb.it>
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 19:15:10 +0530	[thread overview]
Message-ID: <4742E4E6.1010802@absorb.it> (raw)
In-Reply-To: <200711201324.34421.lindner_marek@yahoo.de>

Hi,

Marek Lindner wrote:
> - More important: The routing table operates on IP addresses and not on 
> interface names. Even if olsrd can distinguish your interfaces by name the 
> kernel can't.
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
192.168.1.53 via 192.168.1.188 dev ath1  metric 6
192.168.1.56 via 192.168.1.188 dev ath1  metric 6
192.168.2.32 via 192.168.1.188 dev ath1  metric 7
192.168.1.57 via 192.168.1.188 dev ath1  metric 6
192.168.2.33 via 192.168.1.188 dev ath1  metric 8
192.168.1.58 via 192.168.1.188 dev ath1  metric 3
192.168.1.60 via 192.168.1.188 dev ath1  metric 7
....

so there are interfaces shown in the routes, the kernel should recognize
them, what else they are for?

> Imagine: You have a node A with 2 Interfaces and node B can hear both 
> interfaces but one better than the other. The routing table entry would look 
> like that "<destination> via IP_of_node_A" whereas the kernel can't send the 
> packet to a distinct interface of A.
see above...

regards,
Rene

PS: Invited Sebastian Hagen who programmed the patch to join the
discussion, hope he will help me/us with more details


  reply	other threads:[~2007-11-20 13:45 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 [this message]
2007-11-20 14:08             ` Marek Lindner
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=4742E4E6.1010802@absorb.it \
    --to=batman@absorb.it \
    --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