* [B.A.T.M.A.N.] routing tables
@ 2007-11-06 11:54 tetzlav
2007-11-06 11:42 ` Axel Neumann
0 siblings, 1 reply; 2+ messages in thread
From: tetzlav @ 2007-11-06 11:54 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
> 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [B.A.T.M.A.N.] routing tables
2007-11-06 11:54 [B.A.T.M.A.N.] routing tables tetzlav
@ 2007-11-06 11:42 ` Axel Neumann
0 siblings, 0 replies; 2+ messages in thread
From: Axel Neumann @ 2007-11-06 11:42 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
On Dienstag 06 November 2007, tetzlav wrote:
> > 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...
Its a feature!
and its related to:
"Hiding redundant topology information beyond the local neighborhood"
Nodes may reduce the default TTL of their own OGMs to limit the number of hops
that these OGMs are propagated through the mesh. This can be done for all
OGMs or just for OGMs propagating the existence of particular interfaces.
This does not affect the routing between other nodes in the mesh, but may be
used to limit the range of presence (existence) of individual interfaces. For
example, a node with three interfaces may be configured to send OGMs with a
high TTL only for the first (primary) interface and a small TTL for OGMs
representing the second and third (all non-primary) interfaces. This way, the
node is always reachable via the IP of it's first interface. But it does not
burden the nodes beyond its neighbor horizon with the efforts of maintaining
and re-broadcasting OGMs from it's second and third interface.
One side effect of the one-TTL OGMs is that data-packets generated on these
nodes may leave the node with a source address of such a secondary interface.
This has the consequence that non-neighboring nodes could not reply to this
source address, simply because the OGMs for this source address have never
been propagated that fare.
The Solution to counter the above problem is that each multi-homed node
automatically makes an HNA announcement for all non-primary (hidden)
interfaces and propagates this HNAs with the OGM representing its primary
interface. This way the IP addresses of the non-primary interfaces are also
reachable beyond the local neighbor horizon.
All HNA announcements end up in routing table 65.
It tells the network stack to route packets with a destination address of a
non-primary interface towards the IP address of the corresponding primary
interface.
This is now the default behavior in 0.3
ciao,
axel
>
>
> Regards
> tetzlav
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-11-06 11:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-06 11:54 [B.A.T.M.A.N.] routing tables tetzlav
2007-11-06 11:42 ` Axel Neumann
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.