* [B.A.T.M.A.N.] two radio nodes and alternative next hop
@ 2008-04-21 12:39 Jan Hetges
2008-04-21 12:57 ` Benjamin Henrion
0 siblings, 1 reply; 11+ messages in thread
From: Jan Hetges @ 2008-04-21 12:39 UTC (permalink / raw)
To: b.a.t.m.a.n
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
Hi
i'm running bmxd_rv972 for almost three months now, without
any mayor problems :-)... thanks.
what i recognized lately, on two nodes (the ones with more than
one bmx interface), show alternativeNextHops, which are *NO*
alternative. It seems there gets some 'information' lost between
the two IFs. I suppose that's a known issue ;-), any ideas how to
fix/workaround ? iirc, i saw once or twice a node "on the other
interface" even listed as the bestNextHop.
cheers
--Jan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two radio nodes and alternative next hop
2008-04-21 12:39 [B.A.T.M.A.N.] two radio nodes and alternative next hop Jan Hetges
@ 2008-04-21 12:57 ` Benjamin Henrion
2008-04-21 20:30 ` [B.A.T.M.A.N.] two-radio " Jan Hetges
2008-04-21 20:33 ` [B.A.T.M.A.N.] two radio " Jan Hetges
0 siblings, 2 replies; 11+ messages in thread
From: Benjamin Henrion @ 2008-04-21 12:57 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
Can you describe a little more extensively your network configuration?
On Mon, Apr 21, 2008 at 2:39 PM, Jan Hetges <tran@ms20.net> wrote:
> Hi
> i'm running bmxd_rv972 for almost three months now, without
> any mayor problems :-)... thanks.
> what i recognized lately, on two nodes (the ones with more than
> one bmx interface), show alternativeNextHops, which are *NO*
> alternative. It seems there gets some 'information' lost between
> the two IFs. I suppose that's a known issue ;-), any ideas how to
> fix/workaround ? iirc, i saw once or twice a node "on the other
> interface" even listed as the bestNextHop.
>
> cheers
>
> --Jan
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFIDIsAlTtvZdk47D4RAuzTAJ4kaM8igcwMFyGm0VME14nnBR2rIgCeL7WL
> vgm3/cHM8tR7/g8q0NkGPiU=
> =40m+
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> 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
>
>
--
Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-4148403
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop
2008-04-21 12:57 ` Benjamin Henrion
@ 2008-04-21 20:30 ` Jan Hetges
2008-04-22 14:01 ` Axel Neumann
2008-04-21 20:33 ` [B.A.T.M.A.N.] two radio " Jan Hetges
1 sibling, 1 reply; 11+ messages in thread
From: Jan Hetges @ 2008-04-21 20:30 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
On Mon, Apr 21, 2008 at 02:57:44PM +0200, Benjamin Henrion wrote:
> On Mon, Apr 21, 2008 at 2:39 PM, Jan Hetges <tran@ms20.net> wrote:
> > i'm running bmxd_rv972 for almost three months now, without
> > any mayor problems :-)... thanks.
> > what i recognized lately, on two nodes (the ones with more than
> > one bmx interface), show alternativeNextHops, which are *NO*
> > alternative. It seems there gets some 'information' lost between
> > the two IFs. I suppose that's a known issue ;-), any ideas how to
> > fix/workaround ? iirc, i saw once or twice a node "on the other
> > interface" even listed as the bestNextHop.
> >
> Can you describe a little more extensively your network configuration?
sorry ;-):
x.x.0.0/24---x.x.0.1/x.x.3.1---x.x.3.0/24---x.x.3.160/x.x.4.1---x.x.4.0/24
|
internet
batman network x.x.0.0/20.
.0.1/.3.1 is one node with two radios, and .3.160/.4.1 the other one.
and, .3.160/.4.1 lists .4.162 as alternativeNextHop to .3.128.
where .3.1 and .3.137 can see .3.128, but .4.162 can not. So, there is a real
alternativeNextHop to .3.128 ... .3.137, which is listed after .4.162
on .3.160/.4.1. I attach the output of bmxd -cbd8.
But after i really think through it, it shouldn't really matter,
because, if the connection between .3.160 and .3.1 gets interrupted,
.4.162 should probably fall back behind .3.137 in .3.160's statistic.
--Jan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two radio nodes and alternative next hop
2008-04-21 12:57 ` Benjamin Henrion
2008-04-21 20:30 ` [B.A.T.M.A.N.] two-radio " Jan Hetges
@ 2008-04-21 20:33 ` Jan Hetges
1 sibling, 0 replies; 11+ messages in thread
From: Jan Hetges @ 2008-04-21 20:33 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
[-- Attachment #1.1: Type: text/plain, Size: 26 bytes --]
uups, here the attachment
[-- Attachment #1.2: bmxd.log --]
[-- Type: text/plain, Size: 3830 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF wlan0:bmx 172.19.3.160, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 25023, UT 17:18:01:04, CPU 25/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.3.1 wlan0:bmx 172.19.3.1 91 ( 99 11:03:11:00 3342 0 6 5 ) [ wlan0:bmx 86 98 86]
172.19.3.137 wlan0:bmx 172.19.3.137 91 ( 99 0:00:42:40 2712 0 1 7 ) [ wlan0:bmx 90 86 100]
172.19.4.162 wlan1:bmx 172.19.4.160 98 ( 100 0:00:28:16 30333 0 1 1 ) [ wlan1:bmx 82 84 96]
172.19.4.161 wlan1:bmx 172.19.4.161 100 ( 100 0:00:28:10 44312 0 1 2 ) [ wlan1:bmx 98 100 98]
172.19.4.160 wlan1:bmx 172.19.4.160 100 ( 100 0:00:28:05 13209 0 1 3 ) [ wlan1:bmx 100 100 100]
172.19.4.165 wlan0:bmx 172.19.4.165 55 ( 84 0:00:28:03 9777 1 1 4 ) [ wlan0:bmx 46 76 60]
172.19.3.140 wlan0:bmx 172.19.3.1 78 ( 97 0:00:26:57 16823 4 2 6 ) [ wlan0:bmx 4 54 6]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.140 wlan0:bmx 172.19.3.1 78 ( 97 0:00:26:57 16823 4 100 1020 1 3 1 ) 172.19.3.140 2 172.19.4.162 60
172.19.3.130 wlan0:bmx 172.19.3.1 88 ( 98 1:01:20:31 64430 0 100 987 8 2 1 ) 172.19.4.162 65 172.19.3.140 1
172.19.3.133 wlan0:bmx 172.19.3.1 86 ( 92 0:00:28:29 22127 0 100 989 5 2 1 ) 172.19.3.140 2 172.19.4.162 67
172.19.4.161 wlan1:bmx 172.19.4.161 100 ( 100 0:00:28:10 44312 0 100 979 0 1 1 ) 172.19.4.162 78 172.19.3.140 2
172.19.4.167 wlan1:bmx 172.19.4.160 68 ( 69 0:00:28:16 61695 0 100 985 5 3 34 ) 172.19.4.162 55 172.19.3.140 0
172.19.4.160 wlan1:bmx 172.19.4.160 100 ( 100 0:00:28:05 13209 0 100 1016 27 1 2 ) 172.19.4.162 84 172.19.3.140 0
172.19.3.141 wlan0:bmx 172.19.3.1 78 ( 92 0:00:26:43 30813 0 100 997 12 3 1 ) 172.19.4.162 54 172.19.3.140 2
172.19.3.137 wlan0:bmx 172.19.3.137 91 ( 99 0:00:42:40 2712 0 100 1004 7 1 1 ) 172.19.4.162 72 172.19.3.140 1
172.19.4.162 wlan1:bmx 172.19.4.160 98 ( 100 0:00:28:16 30333 0 100 1015 16 2 30 ) 172.19.4.162 87 172.19.3.140 1
172.19.3.128 wlan0:bmx 172.19.3.1 80 ( 97 1:01:20:33 15813 0 100 1012 18 2 1 ) 172.19.4.162 67 172.19.3.140 2
172.19.3.1 wlan0:bmx 172.19.3.1 91 ( 99 11:03:11:00 3342 0 100 1021 64 1 37 ) 172.19.4.162 65 172.19.3.140 2
172.19.0.4 wlan0:bmx 172.19.3.1 81 ( 96 0:05:53:27 52999 3 100 1007 9 3 1 ) 172.19.3.140 0 172.19.4.162 62
172.19.0.2 wlan0:bmx 172.19.3.1 89 ( 99 0:08:18:36 41115 1 100 1002 5 2 1 ) 172.19.4.162 67 172.19.3.140 2
172.19.4.165 wlan0:bmx 172.19.4.165 55 ( 84 0:00:28:03 9777 1 100 1004 7 1 1 ) 172.19.4.162 41 172.19.3.140 2
172.19.3.136 wlan0:bmx 172.19.3.1 63 ( 75 0:00:26:38 6097 0 100 979 26 2 1 ) 172.19.4.162 47 172.19.3.140 2
172.19.3.135 wlan0:bmx 172.19.3.1 67 ( 75 0:00:26:33 55121 0 100 1017 5 3 1 ) 172.19.4.162 50 172.19.3.140 0
16 known Originator(s), averages: 82 ( 92 0 100 1002 13 2 7 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop
2008-04-21 20:30 ` [B.A.T.M.A.N.] two-radio " Jan Hetges
@ 2008-04-22 14:01 ` Axel Neumann
2008-04-23 0:04 ` Jan Hetges
0 siblings, 1 reply; 11+ messages in thread
From: Axel Neumann @ 2008-04-22 14:01 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
Hi Jan,
On Montag 21 April 2008, Jan Hetges wrote:
> On Mon, Apr 21, 2008 at 02:57:44PM +0200, Benjamin Henrion wrote:
> > On Mon, Apr 21, 2008 at 2:39 PM, Jan Hetges <tran@ms20.net> wrote:
> > > i'm running bmxd_rv972 for almost three months now, without
> > > any mayor problems :-)... thanks.
> > > what i recognized lately, on two nodes (the ones with more than
> > > one bmx interface), show alternativeNextHops, which are *NO*
> > > alternative. It seems there gets some 'information' lost between
> > > the two IFs. I suppose that's a known issue ;-),
It is NOT a known issue (at least not to me) and if its a bug it should be fixed.
> > > fix/workaround ? iirc, i saw once or twice a node "on the other
> > > interface" even listed as the bestNextHop.
> >
> > Can you describe a little more extensively your network configuration?
>
> sorry ;-):
>
>
> x.x.0.0/24---x.x.0.1/x.x.3.1---x.x.3.0/24---x.x.3.160/x.x.4.1---x.x.4.0/24
One general questions: do all your interfaces operate on the same frequency?
Then, I am unsure about the netmasks you are using. The above line I
understand that you are using x.x.3.0/24 and x.x.4.0/24 netmasks.
Generally, It is strongly recommended to always use the same netmask
on ALL batman interfaces !
In your case there is: x.x.3.160/24 for one interface on the 3.160 node
which should result in a broadcast address of x.x.3.255.
But according to the debug output there is a direct link to x.x.4.165/24
(which I guess has broadcast address of x.x.4.255) and therefore the two
interfaces should not see each other!!?? Can you verify that (note that the
"ifconfig dev ip/netmask" command is buggy and does not always produce
corresponding netmask and broadcast addresses and that the interfaces MUST be
configured appropriately before the daemon is started. !!!)
> .0.1/.3.1 is one node with two radios, and .3.160/.4.1 the other one.
> and, .3.160/.4.1 lists .4.162 as alternativeNextHop to .3.128.
> where .3.1 and .3.137 can see .3.128, but .4.162 can not.
An alternativeNextHop to a specific node must not necessarily be a direct neighbor of
that node. For example in the following scenario:
A---B---D
| |
+---E---+
From As' point of view B and E may both be potential next hops towards D. But only E
can directly see D.
Is it possible to generate (almost simultaneously) -cbd8 logs from the involved
nodes, especially 3.1, 3.160, 4.162, 3.128.
> So, there is a
> real alternativeNextHop to .3.128 ... .3.137, which is listed after .4.162
> on .3.160/.4.1. I attach the output of bmxd -cbd8.
The attached debug log shows:
172.19.3.128 wlan0:bmx 172.19.3.1 80 ( 97 1:01:20:33 15813 0 100 1012
18 2 1 ) 172.19.4.162 67 172.19.3.140 2
At least this line does not show 3.137 listed after .4.162 on .3.160/.4.1
Has it been truncated ??
Looking forward to solve this...
best regards,
axel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop
2008-04-22 14:01 ` Axel Neumann
@ 2008-04-23 0:04 ` Jan Hetges
2008-04-23 7:54 ` Axel Neumann
0 siblings, 1 reply; 11+ messages in thread
From: Jan Hetges @ 2008-04-23 0:04 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
[-- Attachment #1: Type: text/plain, Size: 3738 bytes --]
On Tue, Apr 22, 2008 at 04:01:57PM +0200, Axel Neumann wrote:
> Hi Jan,
>
> On Montag 21 April 2008, Jan Hetges wrote:
> > On Mon, Apr 21, 2008 at 02:57:44PM +0200, Benjamin Henrion wrote:
> > > On Mon, Apr 21, 2008 at 2:39 PM, Jan Hetges <tran@ms20.net> wrote:
> > > > what i recognized lately, on two nodes (the ones with more than
> > > > one bmx interface), show alternativeNextHops, which are *NO*
> > > > alternative. It seems there gets some 'information' lost between
> > > > the two IFs. I suppose that's a known issue ;-),
> It is NOT a known issue (at least not to me) and if its a bug it should be fixed.
so, let's fix it then ;-)
> > > Can you describe a little more extensively your network configuration?
> > x.x.0.0/24---x.x.0.1/x.x.3.1---x.x.3.0/24---x.x.3.160/x.x.4.1---x.x.4.0/24
> One general questions: do all your interfaces operate on the same frequency?
no
> Then, I am unsure about the netmasks you are using. The above line I
> understand that you are using x.x.3.0/24 and x.x.4.0/24 netmasks.
sorry, the /24 only specifys the netrange for the ssid it belongs to
> Generally, It is strongly recommended to always use the same netmask
> on ALL batman interfaces !
i know, you helped me fixing that :-)
and if you look again into my previous mail, i also wrote:
batman network x.x.0.0/20.
so, ALL batman broadcasting to x.x.15.255,
> But according to the debug output there is a direct link to x.x.4.165/24
> (which I guess has broadcast address of x.x.4.255) and therefore the two
> interfaces should not see each other!!??
there are direct links always only in the according /24 netrange,
because they are on different channels/ssids, so .3.160 and .4.1 cannot
"see" each other.
Note, NO .4.x node cannot see ANY .3.x node, even if they
would be on the same channel/ssid!
>Can you verify that (note that the
> "ifconfig dev ip/netmask" command is buggy and does not always produce
> corresponding netmask and broadcast addresses and that the interfaces MUST be
> configured appropriately before the daemon is started. !!!)
i recognized the buggy ifconfig and ALWAYS set netmask and broadcast
addresses.
>
> > .0.1/.3.1 is one node with two radios, and .3.160/.4.1 the other one.
> > and, .3.160/.4.1 lists .4.162 as alternativeNextHop to .3.128.
> > where .3.1 and .3.137 can see .3.128, but .4.162 can not.
>
> An alternativeNextHop to a specific node must not necessarily be a direct neighbor of
> that node. For example in the following scenario:
claro
>
> A---B---D
> | |
> +---E---+
>
> >From As' point of view B and E may both be potential next hops towards D. But only E
> can directly see D.
>
> Is it possible to generate (almost simultaneously) -cbd8 logs from the involved
> nodes, especially 3.1, 3.160, 4.162, 3.128.
attached, note that .3.137 is down due to power issues, and the link
between .3.140 and .3.160 is not usable, but you should see the issue.
>
> > So, there is a
> > real alternativeNextHop to .3.128 ... .3.137, which is listed after .4.162
> > on .3.160/.4.1. I attach the output of bmxd -cbd8.
>
> The attached debug log shows:
> 172.19.3.128 wlan0:bmx 172.19.3.1 80 ( 97 1:01:20:33 15813 0 100 1012
> 18 2 1 ) 172.19.4.162 67 172.19.3.140 2
right, but it SHOULD show .3.137, and NOT .4.162 at all. The ONLY link
between .4.x and .3.x IS .4.1/.3.160 (that's the reason for having a
repeater there :)
>
> At least this line does not show 3.137 listed after .4.162 on .3.160/.4.1
> Has it been truncated ??
i don't think so, i'll make some more logs when .3.137 is back up
>
> Looking forward to solve this...
cheers
--Jan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop
2008-04-23 0:04 ` Jan Hetges
@ 2008-04-23 7:54 ` Axel Neumann
2008-04-23 23:02 ` Jan Hetges
2008-04-24 3:55 ` Jan Hetges
0 siblings, 2 replies; 11+ messages in thread
From: Axel Neumann @ 2008-04-23 7:54 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
Hey,
> > But according to the debug output there is a direct link to x.x.4.165/24
> > (which I guess has broadcast address of x.x.4.255) and therefore the two
> > interfaces should not see each other!!??
>
> there are direct links always only in the according /24 netrange,
> because they are on different channels/ssids, so .3.160 and .4.1 cannot
> "see" each other.
> Note, NO .4.x node cannot see ANY .3.x node, even if they
> would be on the same channel/ssid!
Are you also specifying the bssid? Because in order to define different
cells in an ad-hoc network the ssid is almost useless in most adhoc
implementations. THe BSSID is much more important!
(E.g. use kamikaze-etc/config/wireless style: option bssid 44:ca:ff:ee:ba:be
or the command-line-style: iwconfig wlan0 ap 44:ca:ff:ee:ba:be )
Anyway, you mean a debug output on 3.16 like the following can not be correct?
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.4.165 wlan0:bmx 172.19.4.165 55 ( 84 0:00:28:03 9777 1 1 4 ) [ wlan0:bmx 46 76 60]
Sorry for being stubborn: what makes you so sure that they cannot see each
other or that the driver does not mix things up?
At least from the madwifi driver (in ad-hoc mode) I know that it tends to
ignore its assigned *bssid* and channel and switches back and forth between the
assigned one and others.
Sometimes the driver hangs on a wrong bssid and
channel, forwards the wrong IP packets, and cannot receive any packets from
its originally assigned bssid/channel.
One way to verify this would be to run a tcpdump on interface 3.160/wlan0 and
see if it ever tracks a batman packet with a src address of e.g. 172.19.4.165
> i'll make some more logs when .3.137 is back up
ok.
ciao,
axel
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop
2008-04-23 7:54 ` Axel Neumann
@ 2008-04-23 23:02 ` Jan Hetges
2008-04-24 7:33 ` Axel Neumann
2008-04-24 3:55 ` Jan Hetges
1 sibling, 1 reply; 11+ messages in thread
From: Jan Hetges @ 2008-04-23 23:02 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
[-- Attachment #1.1: Type: text/plain, Size: 2726 bytes --]
Hi Axel
thanks for being stubborn :-)
On Wed, Apr 23, 2008 at 09:54:37AM +0200, Axel Neumann wrote:
> > > But according to the debug output there is a direct link to x.x.4.165/24
> > > (which I guess has broadcast address of x.x.4.255) and therefore the two
> > > interfaces should not see each other!!??
> >
> > there are direct links always only in the according /24 netrange,
> > because they are on different channels/ssids, so .3.160 and .4.1 cannot
> > "see" each other.
> > Note, NO .4.x node cannot see ANY .3.x node, even if they
> > would be on the same channel/ssid!
ok, .4.165 can see .3.160
> Are you also specifying the bssid? Because in order to define different
> cells in an ad-hoc network the ssid is almost useless in most adhoc
> implementations. THe BSSID is much more important!
> (E.g. use kamikaze-etc/config/wireless style: option bssid 44:ca:ff:ee:ba:be
> or the command-line-style: iwconfig wlan0 ap 44:ca:ff:ee:ba:be )
thanks, did'nt know that ^^
>
> Anyway, you mean a debug output on 3.16 like the following can not be correct?
> Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
> 172.19.4.165 wlan0:bmx 172.19.4.165 55 ( 84 0:00:28:03 9777 1 1 4 ) [ wlan0:bmx 46 76 60]
did'nt see that ^^^^^
>
> Sorry for being stubborn: what makes you so sure that they cannot see each
> other or that the driver does not mix things up?
>
> At least from the madwifi driver (in ad-hoc mode) I know that it tends to
> ignore its assigned *bssid* and channel and switches back and forth between the
> assigned one and others.
>
> Sometimes the driver hangs on a wrong bssid and
> channel, forwards the wrong IP packets, and cannot receive any packets from
> its originally assigned bssid/channel.
>
> One way to verify this would be to run a tcpdump on interface 3.160/wlan0 and
> see if it ever tracks a batman packet with a src address of e.g. 172.19.4.165
ok, what happend: .4.165 (i386/prism2.5/hostap(-pci)) switched for some
unknown reason to .3.x/channel/essid (which explains the poor link from
.4.165 to ".4.1"(actually .3.160), and i thought it was a fast growing Guahumo tree :).
So i fixed the bssids on both, .4.1 and .4.165. And it seems to not
switch anymore... thanks for being so stubborn :-)
But that doesn't change the fact, that .4.1 still shows .4.162 as
alternativeNextHop to .3.x, where, in fact, all alternative paths inside
.4.x to .3.x lead back to .4.1 !
> > i'll make some more logs when .3.137 is back up
still down, anyways, i attach -cbd8 from .4.1, .4.160, .4.162 and .4.165
cheers
--Jan
[-- Attachment #1.2: 4.1.log --]
[-- Type: text/plain, Size: 3158 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF wlan0:bmx 172.19.3.160, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 10045, UT 19:20:37:09, CPU 34/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.3.1 wlan0:bmx 172.19.3.1 79 ( 100 13:05:47:05 53771 0 6 5 ) [ wlan0:bmx 90 100 90]
172.19.4.165 wlan1:bmx 172.19.4.165 100 ( 100 0:10:25:17 45516 0 1 1 ) [ wlan1:bmx 98 98 100]
172.19.4.162 wlan1:bmx 172.19.4.162 97 ( 100 0:10:25:01 471 0 1 2 ) [ wlan1:bmx 92 92 100]
172.19.4.161 wlan1:bmx 172.19.4.161 96 ( 100 0:10:24:51 14469 1 1 3 ) [ wlan1:bmx 92 98 92]
172.19.4.160 wlan1:bmx 172.19.4.160 98 ( 100 0:10:24:50 48895 0 2 4 ) [ wlan1:bmx 92 96 94]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.131 wlan0:bmx 172.19.3.1 78 ( 97 0:16:56:07 16669 0 100 1003 10 2 1 ) 172.19.4.162 28
172.19.3.134 wlan0:bmx 172.19.3.1 78 ( 92 0:02:06:04 30506 0 100 1001 7 3 1 ) 172.19.4.162 66
172.19.3.130 wlan0:bmx 172.19.3.1 68 ( 88 1:07:12:16 49397 0 100 972 6 2 17 ) 172.19.4.162 59
172.19.3.133 wlan0:bmx 172.19.3.1 72 ( 90 0:07:51:30 48541 0 100 1004 1 2 1 ) 172.19.4.162 63
172.19.4.161 wlan1:bmx 172.19.4.161 96 ( 100 0:10:24:51 14469 1 100 1004 5 1 1 ) 172.19.4.162 43
172.19.4.160 wlan1:bmx 172.19.4.160 98 ( 100 0:10:24:50 48895 0 100 1011 7 1 94 ) 172.19.4.162 92
172.19.3.141 wlan0:bmx 172.19.3.1 72 ( 91 0:10:24:04 1018 0 100 952 34 3 1 ) 172.19.4.162 59
172.19.4.162 wlan1:bmx 172.19.4.162 97 ( 100 0:10:25:01 471 0 100 996 21 1 855 ) 172.19.4.160 90
172.19.3.128 wlan0:bmx 172.19.3.1 77 ( 90 1:07:12:17 748 1 100 974 13 2 13 ) 172.19.4.162 56
172.19.3.1 wlan0:bmx 172.19.3.1 79 ( 100 13:05:47:05 53771 0 100 1023 42 1 37 ) 172.19.4.162 65
172.19.0.4 wlan0:bmx 172.19.3.1 78 ( 96 0:08:27:17 51735 0 100 1005 28 3 1 ) 172.19.4.162 69
172.19.0.2 wlan0:bmx 172.19.3.1 79 ( 95 0:07:57:04 14754 0 100 996 6 2 1 ) 172.19.4.162 65
172.19.4.165 wlan1:bmx 172.19.4.165 100 ( 100 0:10:25:17 45516 0 100 995 29 1 3 ) 172.19.4.162 85
172.19.3.136 wlan0:bmx 172.19.3.1 76 ( 87 0:10:24:02 41807 0 100 992 26 3 1 ) 172.19.4.162 30
172.19.3.135 wlan0:bmx 172.19.3.1 68 ( 85 0:02:36:56 62915 0 100 986 36 4 1 ) 172.19.4.162 56
15 known Originator(s), averages: 81 ( 94 0 100 994 18 2 68 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #1.3: 4.160.log --]
[-- Type: text/plain, Size: 2633 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF eth1:bmx 172.19.4.160, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 48894, UT 0:10:24:51, CPU 7/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.4.162 eth1:bmx 172.19.4.162 99 ( 100 0:10:24:49 468 0 2 1 ) [ eth1:bmx 100 100 100]
172.19.4.1 eth1:bmx 172.19.4.1 99 ( 100 0:10:24:49 10040 0 4 2 ) [ eth1:bmx 96 100 96]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.131 eth1:bmx 172.19.4.1 73 ( 76 0:10:24:49 16666 0 100 994 10 3 8 ) 172.19.4.162 42
172.19.3.134 eth1:bmx 172.19.4.1 78 ( 80 0:02:06:01 30502 1 100 992 0 4 1 )
172.19.3.130 eth1:bmx 172.19.4.1 68 ( 69 0:10:24:49 49391 4 100 985 20 3 2 ) 172.19.4.162 0
172.19.3.133 eth1:bmx 172.19.4.1 71 ( 73 0:07:51:28 48538 0 100 1019 3 3 11 )
172.19.4.161 eth1:bmx 172.19.4.1 89 ( 96 0:10:24:49 14467 0 100 1010 15 2 13 ) 172.19.4.162 33
172.19.3.160 eth1:bmx 172.19.4.1 96 ( 100 0:10:24:49 10040 0 100 1003 29 1 3 )
172.19.3.141 eth1:bmx 172.19.4.1 70 ( 71 0:10:24:03 1016 0 100 952 37 4 9 )
172.19.4.162 eth1:bmx 172.19.4.162 99 ( 100 0:10:24:49 468 0 100 1002 14 1 53 ) 172.19.4.1 87
172.19.3.128 eth1:bmx 172.19.4.1 75 ( 77 0:10:24:49 746 0 100 983 13 3 8 ) 172.19.4.162 12
172.19.3.1 eth1:bmx 172.19.4.1 75 ( 79 0:10:24:49 53769 0 100 1007 42 2 9 )
172.19.0.4 eth1:bmx 172.19.4.1 76 ( 77 0:08:27:15 51732 0 100 1008 32 4 11 )
172.19.0.2 eth1:bmx 172.19.4.1 74 ( 79 0:07:57:02 14751 0 100 1002 11 3 1 )
172.19.4.165 eth1:bmx 172.19.4.1 99 ( 100 0:10:24:48 45513 0 100 1001 21 2 15 )
172.19.3.136 eth1:bmx 172.19.4.1 73 ( 74 0:10:24:01 41804 0 100 968 26 4 15 ) 172.19.4.162 36
172.19.3.135 eth1:bmx 172.19.4.1 64 ( 66 0:02:36:53 62912 1 100 1003 35 5 3 )
15 known Originator(s), averages: 78 ( 81 0 100 995 20 2 10 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #1.4: 4.162.log --]
[-- Type: text/plain, Size: 3226 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF eth1:bmx 172.19.4.162, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 470, UT 0:10:25:00, CPU 14/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.4.1 eth1:bmx 172.19.4.1 90 ( 100 0:10:24:56 10040 0 2 1 ) [ eth1:bmx 92 98 92]
172.19.4.160 eth1:bmx 172.19.4.160 100 ( 100 0:10:24:47 48892 0 1 2 ) [ eth1:bmx 100 100 100]
172.19.4.165 eth1:bmx 172.19.4.160 98 ( 100 0:10:24:51 45513 0 2 3 ) [ eth1:bmx 36 74 48]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.131 eth1:bmx 172.19.4.1 74 ( 76 0:10:24:54 16666 0 100 994 10 3 401 ) 172.19.4.160 71 172.19.4.165 29
172.19.3.134 eth1:bmx 172.19.4.160 76 ( 80 0:02:06:00 30502 1 100 992 0 5 58 ) 172.19.4.1 69 172.19.4.165 41
172.19.3.130 eth1:bmx 172.19.4.160 68 ( 69 0:10:24:55 49391 3 100 984 20 4 428 ) 172.19.4.1 58 172.19.4.165 25
172.19.3.133 eth1:bmx 172.19.4.160 70 ( 73 0:07:51:26 48538 0 100 1018 3 4 316 ) 172.19.4.1 65 172.19.4.165 27
172.19.4.161 eth1:bmx 172.19.4.1 88 ( 96 0:10:24:48 14467 0 100 1017 15 2 447 ) 172.19.4.160 87 172.19.4.165 43
172.19.3.160 eth1:bmx 172.19.4.160 95 ( 100 0:10:24:54 10040 0 100 1003 29 2 360 ) 172.19.4.1 88 172.19.4.165 42
172.19.4.160 eth1:bmx 172.19.4.160 100 ( 100 0:10:24:47 48892 0 100 1028 10 1 29 ) 172.19.4.165 25 172.19.4.1 88
172.19.3.141 eth1:bmx 172.19.4.160 70 ( 71 0:10:24:00 1016 0 100 951 37 5 380 ) 172.19.4.1 59 172.19.4.165 28
172.19.3.128 eth1:bmx 172.19.4.1 74 ( 77 0:10:24:55 746 0 100 982 13 3 397 ) 172.19.4.160 72 172.19.4.165 29
172.19.3.1 eth1:bmx 172.19.4.160 74 ( 79 0:10:24:54 53769 0 100 1016 42 3 364 ) 172.19.4.1 71 172.19.4.165 28
172.19.0.4 eth1:bmx 172.19.4.160 74 ( 77 0:08:27:12 51732 0 100 1008 32 5 254 ) 172.19.4.1 71 172.19.4.165 31
172.19.0.2 eth1:bmx 172.19.4.160 73 ( 79 0:07:57:00 14751 0 100 999 11 4 327 ) 172.19.4.1 71 172.19.4.165 29
172.19.4.165 eth1:bmx 172.19.4.160 98 ( 100 0:10:24:51 45513 0 100 991 21 3 384 ) 172.19.4.1 96 172.19.4.165 36
172.19.3.136 eth1:bmx 172.19.4.1 73 ( 74 0:10:23:59 41804 0 100 968 26 4 355 ) 172.19.4.160 71 172.19.4.165 29
172.19.3.135 eth1:bmx 172.19.4.160 61 ( 66 0:02:36:51 62912 0 100 996 35 6 72 ) 172.19.4.1 58 172.19.4.165 33
15 known Originator(s), averages: 77 ( 81 0 100 996 20 3 304 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #1.5: 4.165.log --]
[-- Type: text/plain, Size: 2815 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF wlan0:bmx 172.19.4.165, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 45513, UT 0:10:25:14, CPU 21/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.4.1 wlan0:bmx 172.19.4.1 100 ( 100 0:10:20:14 10038 0 1 1 ) [ wlan0:bmx 98 100 98]
172.19.4.162 wlan0:bmx 172.19.4.1 94 ( 98 0:10:24:53 466 0 3 2 ) [ wlan0:bmx 36 46 78]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.131 wlan0:bmx 172.19.4.1 76 ( 76 0:10:25:11 16664 0 100 997 16 3 2 ) 172.19.4.162 36
172.19.3.134 wlan0:bmx 172.19.4.1 79 ( 80 0:02:05:58 30501 0 100 983 0 4 1 ) 172.19.4.162 31
172.19.3.130 wlan0:bmx 172.19.4.1 68 ( 69 0:10:25:11 49391 2 100 983 20 3 2 ) 172.19.4.162 27
172.19.3.133 wlan0:bmx 172.19.4.1 74 ( 74 0:07:51:24 48535 1 100 1021 3 3 1 ) 172.19.4.162 33
172.19.4.161 wlan0:bmx 172.19.4.1 96 ( 96 0:10:24:42 14465 0 100 993 15 2 2 ) 172.19.4.162 39
172.19.3.160 wlan0:bmx 172.19.4.1 100 ( 100 0:10:25:12 10038 0 100 985 29 1 2 ) 172.19.4.162 35
172.19.4.160 wlan0:bmx 172.19.4.1 97 ( 99 0:10:24:43 48890 0 100 1019 10 2 2 ) 172.19.4.162 36
172.19.3.141 wlan0:bmx 172.19.4.1 71 ( 72 0:10:23:45 1014 0 100 960 37 4 2 ) 172.19.4.162 27
172.19.4.162 wlan0:bmx 172.19.4.1 94 ( 98 0:10:24:53 466 0 100 985 14 2 2 ) 172.19.4.162 43
172.19.3.128 wlan0:bmx 172.19.4.1 77 ( 78 0:10:25:09 743 1 100 979 13 3 2 ) 172.19.4.162 25
172.19.3.1 wlan0:bmx 172.19.4.1 80 ( 80 0:10:25:11 53766 1 100 1018 65 2 2 ) 172.19.4.162 29
172.19.0.4 wlan0:bmx 172.19.4.1 78 ( 78 0:08:27:10 51730 0 100 988 32 4 1 ) 172.19.4.162 32
172.19.0.2 wlan0:bmx 172.19.4.1 78 ( 79 0:07:56:57 14749 0 100 1029 11 3 1 ) 172.19.4.162 33
172.19.3.136 wlan0:bmx 172.19.4.1 73 ( 74 0:10:23:54 41802 0 100 994 40 4 2 ) 172.19.4.162 24
172.19.3.135 wlan0:bmx 172.19.4.1 68 ( 68 0:02:36:49 62909 1 100 995 35 5 1 ) 172.19.4.162 17
15 known Originator(s), averages: 80 ( 81 0 100 995 22 3 1 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop
2008-04-23 7:54 ` Axel Neumann
2008-04-23 23:02 ` Jan Hetges
@ 2008-04-24 3:55 ` Jan Hetges
2008-04-24 8:09 ` Axel Neumann
1 sibling, 1 reply; 11+ messages in thread
From: Jan Hetges @ 2008-04-24 3:55 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
[-- Attachment #1.1: Type: text/plain, Size: 378 bytes --]
On Wed, Apr 23, 2008 at 09:54:37AM +0200, Axel Neumann wrote:
[..snip..]
> > i'll make some more logs when .3.137 is back up
> ok.
there you go (to make the confusion complete, i named them
like before ;-) .
and something completely different: i think, .4.1 should choose the
direkt link to .4.162 instead of going through .4.160 (and vice versa)
cheers
--Jan
[-- Attachment #1.2: 3.1.log --]
[-- Type: text/plain, Size: 4073 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF wlan0:bmx 172.19.3.1, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 4887, UT 13:10:24:11, CPU 43/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.3.160 wlan0:bmx 172.19.3.160 94 ( 98 13:10:24:10 26708 0 5 6 ) [ wlan0:bmx 74 94 78]
172.19.3.130 wlan0:bmx 172.19.3.130 88 ( 100 1:11:50:46 525 0 3 5 ) [ wlan0:bmx 78 80 96]
172.19.3.128 wlan0:bmx 172.19.3.128 92 ( 98 1:11:50:48 17407 0 4 8 ) [ wlan0:bmx 72 80 90]
172.19.3.131 wlan0:bmx 172.19.3.131 91 ( 100 0:21:34:38 33336 0 1 3 ) [ wlan0:bmx 80 94 84]
172.19.3.136 wlan0:bmx 172.19.3.131 87 ( 100 0:15:02:33 58460 0 3 2 ) [ wlan0:bmx 50 50 100]
172.19.3.133 wlan0:bmx 172.19.3.133 96 ( 96 0:12:30:01 65198 0 1 9 ) [ wlan0:bmx 76 78 96]
172.19.3.135 wlan0:bmx 172.19.3.131 86 ( 100 0:07:15:27 14037 0 2 4 ) [ wlan0:bmx 40 36 100]
172.19.3.137 wlan0:bmx 172.19.3.160 83 ( 91 0:01:03:44 3969 0 1 1 ) [ wlan0:bmx 0 4 0]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.131 wlan0:bmx 172.19.3.131 91 ( 100 0:21:34:38 33336 0 100 1004 8 1 7 ) 172.19.3.136 60 172.19.3.135 46 172.19.3.137 1
172.19.3.134 wlan0:bmx 172.19.3.131 74 ( 88 0:06:44:35 47266 0 100 1013 0 2 1 ) 172.19.3.135 46 172.19.3.136 51 172.19.3.137 0
172.19.3.130 wlan0:bmx 172.19.3.130 88 ( 100 1:11:50:46 525 0 100 1021 14 1 3107 ) 172.19.3.136 50 172.19.3.135 43 172.19.3.128 77 172.19.3.137 1
172.19.3.133 wlan0:bmx 172.19.3.133 96 ( 96 0:12:30:01 65198 0 100 995 5 1 1 ) 172.19.3.135 38 172.19.3.136 52 172.19.3.137 0
172.19.4.161 wlan0:bmx 172.19.3.160 86 ( 93 0:15:03:22 31126 0 100 1003 0 2 1 ) 172.19.3.135 40 172.19.3.137 2 172.19.3.136 45 172.19.3.130 5
172.19.3.160 wlan0:bmx 172.19.3.160 94 ( 98 13:10:24:10 26708 0 100 992 19 1 15 ) 172.19.3.136 52 172.19.3.135 47 172.19.3.137 0
172.19.4.160 wlan0:bmx 172.19.3.160 91 ( 94 0:15:03:21 23 0 100 1000 25 2 1 ) 172.19.3.136 50 172.19.3.135 38 172.19.3.137 2
172.19.3.141 wlan0:bmx 172.19.3.128 87 ( 92 0:15:02:35 17669 0 100 1043 14 2 99 ) 172.19.3.136 47 172.19.3.130 73 172.19.3.135 42 172.19.3.137 0
172.19.3.137 wlan0:bmx 172.19.3.160 83 ( 91 0:01:03:44 3969 0 100 998 1 2 5 ) 172.19.3.136 42 172.19.3.135 34 172.19.3.137 1 172.19.3.128 12
172.19.4.162 wlan0:bmx 172.19.3.160 86 ( 90 0:15:03:32 17134 0 100 978 10 3 1 ) 172.19.3.136 46 172.19.3.135 34 172.19.3.137 0
172.19.3.128 wlan0:bmx 172.19.3.128 92 ( 98 1:11:50:48 17407 0 100 991 26 1 185 ) 172.19.3.136 38 172.19.3.130 65 172.19.3.135 29 172.19.3.137 2
172.19.4.165 wlan0:bmx 172.19.3.160 90 ( 96 0:15:03:48 62168 0 100 982 19 2 1 ) 172.19.3.136 50 172.19.3.135 42 172.19.3.137 1
172.19.3.136 wlan0:bmx 172.19.3.131 87 ( 100 0:15:02:33 58460 0 100 1003 24 2 422 ) 172.19.3.136 63 172.19.3.135 55 172.19.3.137 0
172.19.3.135 wlan0:bmx 172.19.3.131 86 ( 100 0:07:15:27 14037 0 100 1014 33 3 252 ) 172.19.3.135 68 172.19.3.136 64 172.19.3.137 0 172.19.3.130 2 172.19.3.128 1
14 known Originator(s), averages: 87 ( 95 0 100 1003 14 1 292 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #1.3: 3.128.log --]
[-- Type: text/plain, Size: 3198 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF eth1:bmx 172.19.3.128, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 17406, UT 6:08:28:30, CPU 26/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.3.130 eth1:bmx 172.19.3.130 88 ( 100 1:11:50:49 522 0 1 1 ) [ eth1:bmx 82 84 96]
172.19.3.1 eth1:bmx 172.19.3.130 71 ( 100 1:11:50:50 4882 0 8 4 ) [ eth1:bmx 78 94 82]
172.19.3.141 eth1:bmx 172.19.3.141 92 ( 99 0:15:02:35 17666 0 1 2 ) [ eth1:bmx 88 92 94]
172.19.3.137 eth1:bmx 172.19.3.1 60 ( 95 0:01:03:42 3966 0 2 3 ) [ eth1:bmx 24 44 54]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.131 eth1:bmx 172.19.3.1 72 ( 91 0:21:34:38 33333 0 100 994 10 2 117 ) 172.19.3.130 64 172.19.3.137 35
172.19.3.134 eth1:bmx 172.19.3.1 60 ( 75 0:06:44:34 47263 0 100 971 0 3 60 ) 172.19.3.137 30 172.19.3.130 51
172.19.3.130 eth1:bmx 172.19.3.130 88 ( 100 1:11:50:49 522 0 100 1031 14 1 1443 ) 172.19.3.1 66 172.19.3.137 34
172.19.3.133 eth1:bmx 172.19.3.1 76 ( 96 0:12:30:00 65195 1 100 1011 5 2 51 ) 172.19.3.130 64 172.19.3.137 29
172.19.4.161 eth1:bmx 172.19.3.1 69 ( 95 0:15:03:22 31123 0 100 1036 1 3 43 ) 172.19.3.130 49 172.19.3.137 41
172.19.3.160 eth1:bmx 172.19.3.1 80 ( 99 1:11:50:50 26705 0 100 979 19 2 79 ) 172.19.3.130 68 172.19.3.137 34
172.19.4.160 eth1:bmx 172.19.3.1 71 ( 95 0:15:03:21 20 0 100 1005 25 3 75 ) 172.19.3.130 66 172.19.3.137 41
172.19.3.141 eth1:bmx 172.19.3.141 92 ( 99 0:15:02:35 17666 0 100 1002 14 1 1 ) 172.19.3.137 29 172.19.3.130 0
172.19.3.137 eth1:bmx 172.19.3.1 60 ( 95 0:01:03:42 3966 0 100 999 0 3 63 ) 172.19.3.137 55 172.19.3.130 46
172.19.4.162 eth1:bmx 172.19.3.1 65 ( 92 0:15:03:32 17131 0 100 1009 10 4 43 ) 172.19.3.130 64 172.19.3.137 41
172.19.3.1 eth1:bmx 172.19.3.130 71 ( 100 1:11:50:50 4882 0 100 1022 43 2 98 ) 172.19.3.1 69 172.19.3.137 31
172.19.4.165 eth1:bmx 172.19.3.1 60 ( 99 0:15:03:48 62164 0 100 980 19 3 84 ) 172.19.3.130 56 172.19.3.137 44
172.19.3.136 eth1:bmx 172.19.3.1 66 ( 88 0:15:02:33 58457 0 100 1002 17 3 77 ) 172.19.3.130 63 172.19.3.137 30
172.19.3.135 eth1:bmx 172.19.3.130 65 ( 87 0:07:15:25 14034 0 100 1010 35 5 50 ) 172.19.3.1 64 172.19.3.137 32
14 known Originator(s), averages: 71 ( 93 0 100 1003 15 2 163 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #1.4: 3.137.log --]
[-- Type: text/plain, Size: 3322 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF ath0:bmx 172.19.3.137, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 3970, UT 0:01:03:45, CPU 1/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.3.1 ath0:bmx 172.19.3.160 66 ( 94 0:01:03:43 4884 0 1 1 ) [ ath0:bmx 0 22 0]
172.19.3.128 ath0:bmx 172.19.3.160 68 ( 93 0:01:03:44 17405 1 3 2 ) [ ath0:bmx 28 54 50]
172.19.3.160 ath0:bmx 172.19.3.160 81 ( 100 0:01:03:43 26707 0 6 3 ) [ ath0:bmx 82 100 82]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.131 ath0:bmx 172.19.3.160 76 ( 90 0:01:03:42 33335 0 100 1024 8 3 1 ) 172.19.3.128 24 172.19.3.1 0 172.19.3.131 0
172.19.3.134 ath0:bmx 172.19.3.160 55 ( 71 0:01:03:43 47263 2 100 991 0 4 2 ) 172.19.3.128 18 172.19.3.1 0 172.19.3.131 0
172.19.3.130 ath0:bmx 172.19.3.160 68 ( 94 0:01:03:43 522 1 100 1022 14 3 1 ) 172.19.3.128 36 172.19.3.1 0 172.19.3.131 0
172.19.3.133 ath0:bmx 172.19.3.160 70 ( 95 0:01:03:43 65198 0 100 1006 5 3 2 ) 172.19.3.128 29 172.19.3.1 0 172.19.3.131 0
172.19.4.161 ath0:bmx 172.19.3.160 84 ( 97 0:01:03:42 31124 1 100 1033 0 2 2 ) 172.19.3.128 20 172.19.3.1 0
172.19.4.160 ath0:bmx 172.19.3.160 78 ( 96 0:01:03:43 22 0 100 1007 25 2 1 ) 172.19.3.128 15 172.19.3.1 0 172.19.3.131 0
172.19.3.160 ath0:bmx 172.19.3.160 81 ( 100 0:01:03:43 26707 0 100 988 19 1 1 ) 172.19.3.128 22 172.19.3.1 0
172.19.3.141 ath0:bmx 172.19.3.160 66 ( 89 0:01:03:42 17668 0 100 980 14 4 3 ) 172.19.3.128 33 172.19.3.1 0 172.19.3.131 0
172.19.4.162 ath0:bmx 172.19.3.160 84 ( 94 0:01:03:43 17132 1 100 1017 10 3 2 ) 172.19.3.128 26 172.19.3.1 0 172.19.3.131 0
172.19.3.128 ath0:bmx 172.19.3.160 68 ( 93 0:01:03:44 17405 1 100 998 26 3 4 ) 172.19.3.128 35 172.19.3.1 0 172.19.3.131 0
172.19.3.1 ath0:bmx 172.19.3.160 66 ( 94 0:01:03:43 4884 0 100 1013 43 2 2 ) 172.19.3.1 0 172.19.3.128 27 172.19.3.131 0
172.19.4.165 ath0:bmx 172.19.3.160 85 ( 100 0:01:03:43 62166 0 100 1024 19 2 1 ) 172.19.3.128 29 172.19.3.1 0 172.19.3.131 0
172.19.3.136 ath0:bmx 172.19.3.160 70 ( 86 0:01:03:43 58458 1 100 1014 17 4 2 ) 172.19.3.128 31 172.19.3.1 0 172.19.3.131 0
172.19.3.135 ath0:bmx 172.19.3.160 64 ( 82 0:01:03:42 14034 1 100 1012 35 5 1 ) 172.19.3.128 20 172.19.3.1 0 172.19.3.131 0
14 known Originator(s), averages: 72 ( 91 0 100 1009 16 2 1 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #1.5: 4.1.log --]
[-- Type: text/plain, Size: 3148 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF wlan0:bmx 172.19.3.160, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 26711, UT 20:01:15:43, CPU 24/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.3.1 wlan0:bmx 172.19.3.1 85 ( 100 13:10:25:39 4886 0 6 5 ) [ wlan0:bmx 96 98 96]
172.19.4.165 wlan1:bmx 172.19.4.165 100 ( 100 0:15:03:51 62169 0 1 1 ) [ wlan1:bmx 96 98 96]
172.19.4.162 wlan1:bmx 172.19.4.160 98 ( 100 0:15:03:35 17136 0 1 2 ) [ wlan1:bmx 80 76 100]
172.19.4.161 wlan1:bmx 172.19.4.161 97 ( 100 0:15:03:25 31128 0 1 3 ) [ wlan1:bmx 92 96 94]
172.19.4.160 wlan1:bmx 172.19.4.160 97 ( 100 0:15:03:24 25 0 2 4 ) [ wlan1:bmx 96 96 100]
172.19.3.137 wlan0:bmx 172.19.3.137 91 ( 97 0:01:03:46 3971 0 3 6 ) [ wlan0:bmx 86 86 100]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.131 wlan0:bmx 172.19.3.1 85 ( 91 0:21:34:41 33338 0 100 1005 8 2 1 ) 172.19.4.162 74
172.19.3.134 wlan0:bmx 172.19.3.1 61 ( 74 0:06:44:38 47267 0 100 1019 0 3 1 ) 172.19.4.162 27
172.19.3.130 wlan0:bmx 172.19.3.1 78 ( 88 1:11:50:50 525 0 100 1023 14 2 17 ) 172.19.4.162 71
172.19.3.133 wlan0:bmx 172.19.3.1 85 ( 95 0:12:30:04 65200 0 100 995 9 2 1 ) 172.19.4.162 79
172.19.4.161 wlan1:bmx 172.19.4.161 97 ( 100 0:15:03:25 31128 0 100 1023 0 1 1 ) 172.19.4.162 83
172.19.4.160 wlan1:bmx 172.19.4.160 97 ( 100 0:15:03:24 25 0 100 998 14 1 166 ) 172.19.4.162 91
172.19.3.141 wlan0:bmx 172.19.3.1 83 ( 89 0:15:02:38 17667 3 100 1007 14 3 1 ) 172.19.4.162 69
172.19.3.137 wlan0:bmx 172.19.3.137 91 ( 97 0:01:03:46 3971 0 100 1010 1 1 1 ) 172.19.4.162 41
172.19.4.162 wlan1:bmx 172.19.4.160 98 ( 100 0:15:03:35 17136 0 100 1002 30 2 1254 ) 172.19.4.162 90
172.19.3.128 wlan0:bmx 172.19.3.1 79 ( 92 1:11:50:51 17408 0 100 999 18 2 13 ) 172.19.4.162 64
172.19.3.1 wlan0:bmx 172.19.3.1 85 ( 100 13:10:25:39 4886 0 100 1028 43 1 37 ) 172.19.4.162 70
172.19.4.165 wlan1:bmx 172.19.4.165 100 ( 100 0:15:03:51 62169 0 100 1007 19 1 3 ) 172.19.4.162 86
172.19.3.136 wlan0:bmx 172.19.3.1 76 ( 87 0:15:02:36 58461 0 100 1013 24 3 1 ) 172.19.4.162 65
172.19.3.135 wlan0:bmx 172.19.3.1 75 ( 86 0:07:15:30 14037 1 100 1032 33 4 1 ) 172.19.4.162 61
14 known Originator(s), averages: 85 ( 92 0 100 1012 16 2 107 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #1.6: 4.162.log --]
[-- Type: text/plain, Size: 3084 bytes --]
WARNING: You are using BatMan-eXp 0.3-alpha rv972 (compatibility version 10) !
BatMan-eXp 0.3-alpha rv972, IF eth1:bmx 172.19.4.162, LinkWindowSize 50, PathWindSize 100, OGI 1000ms, currSeqno 17132, UT 0:15:03:31, CPU 10/1000
Neighbor outgoingIF bestNextHop brc (rcvd knownSince lseq lvld rid sid ) [ viaIF RTQ RQ TQ]..
172.19.4.1 eth1:bmx 172.19.4.1 88 ( 100 0:15:03:27 26702 1 2 1 ) [ eth1:bmx 76 98 76]
172.19.4.160 eth1:bmx 172.19.4.160 100 ( 100 0:15:03:18 19 0 1 2 ) [ eth1:bmx 96 100 96]
172.19.4.165 eth1:bmx 172.19.4.160 97 ( 100 0:15:03:22 62163 0 2 3 ) [ eth1:bmx 10 76 12]
Originator outgoingIF bestNextHop brc (rcvd knownSince lseq lvld pws ogi cpu hop change ) alternativeNextHops brc ...
172.19.3.131 eth1:bmx 172.19.4.160 81 ( 85 0:15:03:25 33332 0 100 995 10 4 588 ) 172.19.4.1 75 172.19.4.165 4
172.19.3.134 eth1:bmx 172.19.4.160 58 ( 63 0:06:44:31 47261 0 100 1014 3 5 282 ) 172.19.4.1 57 172.19.4.165 4
172.19.3.130 eth1:bmx 172.19.4.160 76 ( 78 0:15:03:26 519 1 100 1008 8 4 634 ) 172.19.4.1 70 172.19.4.165 5
172.19.3.133 eth1:bmx 172.19.4.160 84 ( 86 0:12:29:57 65194 0 100 1029 1 4 536 ) 172.19.4.1 73 172.19.4.165 9
172.19.4.161 eth1:bmx 172.19.4.160 93 ( 97 0:15:03:19 31122 0 100 993 1 3 662 ) 172.19.4.1 88 172.19.4.165 8
172.19.3.160 eth1:bmx 172.19.4.160 96 ( 100 0:15:03:25 26703 0 100 991 14 2 580 ) 172.19.4.1 81 172.19.4.165 6
172.19.4.160 eth1:bmx 172.19.4.160 100 ( 100 0:15:03:18 19 0 100 1009 25 1 47 ) 172.19.4.165 7 172.19.4.1 61
172.19.3.141 eth1:bmx 172.19.4.160 81 ( 83 0:15:02:31 17664 1 100 1003 14 5 618 ) 172.19.4.1 74 172.19.4.165 9
172.19.3.137 eth1:bmx 172.19.4.160 85 ( 91 0:01:03:40 3965 0 100 1036 0 3 48 ) 172.19.4.1 76 172.19.4.165 7
172.19.3.128 eth1:bmx 172.19.4.160 77 ( 80 0:15:03:26 17402 0 100 994 17 4 568 ) 172.19.4.1 67 172.19.4.165 3
172.19.3.1 eth1:bmx 172.19.4.160 79 ( 85 0:15:03:25 4881 0 100 997 44 3 542 ) 172.19.4.1 74 172.19.4.165 5
172.19.4.165 eth1:bmx 172.19.4.160 97 ( 100 0:15:03:22 62163 0 100 977 19 3 584 ) 172.19.4.1 81 172.19.4.165 9
172.19.3.136 eth1:bmx 172.19.4.160 74 ( 77 0:15:02:30 58455 0 100 1057 17 5 530 ) 172.19.4.1 66 172.19.4.165 3
172.19.3.135 eth1:bmx 172.19.4.160 73 ( 75 0:07:15:22 14032 0 100 1025 35 6 264 ) 172.19.4.1 64 172.19.4.165 5
14 known Originator(s), averages: 82 ( 85 0 100 1009 14 3 463 )
Originator Announced networks HNAs: moved to debug level 9...
Originator Announced services ip:port:seqno ... see debug level 7
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop
2008-04-23 23:02 ` Jan Hetges
@ 2008-04-24 7:33 ` Axel Neumann
0 siblings, 0 replies; 11+ messages in thread
From: Axel Neumann @ 2008-04-24 7:33 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
Hi,
> ok, what happend: .4.165 (i386/prism2.5/hostap(-pci)) switched for some
> unknown reason to .3.x/channel/essid (which explains the poor link from
> .4.165 to ".4.1"(actually .3.160), and i thought it was a fast growing
> Guahumo tree :). So i fixed the bssids on both, .4.1 and .4.165. And it
> seems to not switch anymore...
So lets hope that the prism2.5 behavior is more predictable than madwifi
> thanks for being so stubborn :-)
> But that doesn't change the fact, that .4.1 still shows .4.162 as
> alternativeNextHop to .3.x, where, in fact, all alternative paths inside
> .4.x to .3.x lead back to .4.1 !
Yea, thats correct. Its not a bug, its a design thing of the batman protocol.
3.1 generates OGMs which are rebroadcasted via 4.1. Then, they are received
by 4.162 and 4.160 which rebroadcast them again. Consequently, 4.162 and
4.160 will both receive 3.1-OGMs from each other.
3.x----4.1--+- - -4.162-+
| |
+---4.160---+
Now assuming, for some reasons the link between 4.1 and 4.162 is weak, then
4.162 might receive more OGMs via 4.160 then via 4.1. Consequently, 4.1 will
receive the 3.x-OGMs broadcasted by 4.162 and consider 4.162 as an
alternativeNextHop towards 3.x.
The good thing is that the number of OGMs received via such a "wrong path" can
NEVER become more (and faster) than those received via the "correct path" and
therefore such path should never be chosen.
Theoretically, the same applies for a setup like this:
3.x----4.1---4.162
where 4.1 receives the 3.x-OGMs rebroadcasted by 4.162. But for paranoid
reasons we included a mechanism which allows 4.1 to identify OGMs that
travelled via itself just one hop ago.
happy ruminating,
axel
>
> > > i'll make some more logs when .3.137 is back up
>
> still down, anyways, i attach -cbd8 from .4.1, .4.160, .4.162 and .4.165
>
>
> cheers
>
> --Jan
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [B.A.T.M.A.N.] two-radio nodes and alternative next hop
2008-04-24 3:55 ` Jan Hetges
@ 2008-04-24 8:09 ` Axel Neumann
0 siblings, 0 replies; 11+ messages in thread
From: Axel Neumann @ 2008-04-24 8:09 UTC (permalink / raw)
To: The list for a Better Approach To Mobile Ad-hoc Networking
Hi,
On Donnerstag 24 April 2008, Jan Hetges wrote:
> and something completely different: i think, .4.1 should choose the
> direkt link to .4.162 instead of going through .4.160 (and vice versa)
I experienced the same. Sometimes, from the end2end throughput point of view,
it would be better to choose the direct route and sometimes not. I played a
lot with the metric in charge of the final route. But in the end I am unsure
which parameters are responsible for that or whether the better path can be
identified over several hops at all (perhaps if we take hop-by-hop bandwidth,
interference, load, and other stuff into account). You could twist the metric
so that it always prefers end2end routes with less hops but I think in the
end it is most important to have a general and unique metric applied to every
routing instance in your mesh.
Don't know if you want to hear it? You can play with --dups-ttl-degradation X
(current default is X=2). This degrades the preference for a path by 2
percent with every additional hop (relative to the shortes path). So if you
use 50 instead, a node with two alternative paths (one single-hop and one
two-hop path) to a given destination will ignore 50% of the OGMs received via
a two hop path. Then it will probably choose the single-hop path.
And of course, if you find a value which works general better for all your
nodes then let us know.
ciao,
axel
>
> cheers
>
> --Jan
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2008-04-24 8:09 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-21 12:39 [B.A.T.M.A.N.] two radio nodes and alternative next hop Jan Hetges
2008-04-21 12:57 ` Benjamin Henrion
2008-04-21 20:30 ` [B.A.T.M.A.N.] two-radio " Jan Hetges
2008-04-22 14:01 ` Axel Neumann
2008-04-23 0:04 ` Jan Hetges
2008-04-23 7:54 ` Axel Neumann
2008-04-23 23:02 ` Jan Hetges
2008-04-24 7:33 ` Axel Neumann
2008-04-24 3:55 ` Jan Hetges
2008-04-24 8:09 ` Axel Neumann
2008-04-21 20:33 ` [B.A.T.M.A.N.] two radio " Jan Hetges
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox