All of lore.kernel.org
 help / color / mirror / Atom feed
From: tetzlav <tetzlav@leipzig.freifunk.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: [B.A.T.M.A.N.] routing tables
Date: Tue, 06 Nov 2007 12:54:26 +0100	[thread overview]
Message-ID: <473055F2.8020206@leipzig.freifunk.net> (raw)

> root@13-18:~# batmand -v
> B.A.T.M.A.N. 0.3-beta rv780 (compatibility version 4)

> root@13-18:~# ip r s t 65
> throw 105.61.89.81  proto static
> 105.61.89.86 dev vlan1  proto static  scope link  src 105.61.89.81
> 105.61.89.89 dev vlan1  proto static  scope link  src 105.61.89.81
> 105.61.89.90 dev vlan1  proto static  scope link  src 105.61.89.81
> 105.61.89.92 dev vlan1  proto static  scope link  src 105.61.89.81

> root@13-18:~# ip r s t 66
> 105.61.17.1 via 105.61.89.92 dev vlan1  proto static  src 105.61.89.81
> 105.61.17.17 via 105.61.89.92 dev vlan1  proto static  src 105.61.89.81
> 105.61.17.32 via 105.61.89.86 dev vlan1  proto static  src 105.61.89.81
> throw 105.61.89.81  proto static
> 105.61.17.2 via 105.61.89.89 dev vlan1  proto static  src 105.61.89.81
> 105.61.17.18 via 105.61.89.89 dev vlan1  proto static  src 105.61.89.81
> 105.61.17.35 via 105.61.89.89 dev vlan1  proto static  src 105.61.89.81
> 105.61.17.21 via 105.61.89.90 dev vlan1  proto static  src 105.61.89.81
> 105.61.89.86 dev vlan1  proto static  scope link  src 105.61.89.81
> 105.61.89.89 dev vlan1  proto static  scope link  src 105.61.89.81
> 105.61.89.90 dev vlan1  proto static  scope link  src 105.61.89.81
> 105.61.89.92 dev vlan1  proto static  scope link  src 105.61.89.81


The 105.61.89.x-IPs are secandary BATMAN-interfaces (cable-connections).
Why are routes to this IPs in the table 65 (for announced networks)?
Bug or Feature? I think this is new in rv780...


Regards
tetzlav

             reply	other threads:[~2007-11-06 11:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06 11:54 tetzlav [this message]
2007-11-06 11:42 ` [B.A.T.M.A.N.] routing tables 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=473055F2.8020206@leipzig.freifunk.net \
    --to=tetzlav@leipzig.freifunk.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.