[B.A.T.M.A.N.] strange default routes

[B.A.T.M.A.N.] strange default routes

[Dennis Bartsch]

[-- Attachment #1: Type: text/plain, Size: 8736 bytes --]

hello batmen, ;)

here in berlin NE we are about to update the batmands on our backbone to 0.3.0 . atm our net is mainly running on olsr and batman in parallel for testing purpose.
after some changes in the net we got heavy HNA-hopping with olsr which is related to the improper metric in our case. therefore we are somewhat forcing the
migration to batman and got some strange default routes with the most recent 0.3.0 builds on some routers:

root@OpenWrt:/etc/init.d# route -n
Destination  Gateway  Genmask  Flags Metric Ref    Use Iface
[...]
0.0.0.0         0.0.0.0     0.0.0.0      !        0         0       0     *
[...]

batmand has been started with the following parameters:  /usr/sbin/batmand -g 0 -r 0 eth2

after appearance of this default-route olsr-"clients" cannot use the uplink anymore, so further testing  is difficult.
we have another problem with this build, but cannot investigate further because of this behaviour. so any help is appreciated.

thanks

dennis bartsch
freifunk-bno.de

attached is some console-output:
###########################
root@OpenWrt:/etc/init.d# ifconfig
eth2 Link encap:Ethernet HWaddr 00:01:36:0D:D2:63
inet addr:104.13.0.54 Bcast:104.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:512 Metric:1
RX packets:105511 errors:0 dropped:0 overruns:0 frame:0
TX packets:122436 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:61107954 (58.2 MiB) TX bytes:45973166 (43.8 MiB)
Interrupt:27

eth2:0 Link encap:Ethernet HWaddr 00:01:36:0D:D2:63
inet addr:105.13.0.54 Bcast:105.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:512 Metric:1
Interrupt:27

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2800 errors:0 dropped:0 overruns:0 frame:0
TX packets:2800 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:288724 (281.9 KiB) TX bytes:288724 (281.9 KiB)

wifi0 Link encap:UNSPEC HWaddr 00-0B-6B-4D-63-8B-00-0A-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:997788 errors:0 dropped:1221 overruns:0 frame:443273
TX packets:688240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:305805070 (291.6 MiB) TX bytes:126339425 (120.4 MiB)
Interrupt:28

root@OpenWrt:/etc/init.d# /usr/sbin/batmand -g 0 -r 0 eth2:0 -d 4
WARNING: You are using the unstable batman branch. If you are interested in *using* batman get the latest stable release !
[ 0] Error - can't add rule to 105.0.0.0/8: Invalid argument
[ 0] Error - can't add rule to 105.0.0.0/8: Invalid argument
Using interface eth2:0 with address 105.13.0.54 and broadcast address 105.255.255.255
B.A.T.M.A.N. 0.3-beta (compatibility version 4)
[ 0] Error - can't add rule to 0.0.0.0/0: Invalid argument
[ 10] Error - can't add rule to 0.0.0.0/0: Invalid argument
debug level: 4
[ 20]

[ 940] Forwarding packet (originator 105.13.0.54, seqno 1, TTL 50) on interface eth2:0
[ 940]

[ 940] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0 105.13.0.54 (from OG: 105.13.0.54, seqno 1, tq 255, TTL 50, V 4, UDF 0, IDF 0)
[ 940] Drop packet: received my own broadcast (sender: 105.13.0.54)
[ 940]
[ 1090] Received BATMAN packet via NB: 105.12.0.20 , IF: eth2:0 105.13.0.54 (from OG: 105.12.0.20, seqno 55800, tq 255, TTL 50, V 4, UDF 0, IDF 0)
[ 1090] HNA information received (1 HNA network):
[ 1090] hna: 105.0.200.6/32
[ 1090] Creating new originator: 105.12.0.20
[ 1090] Creating new last-hop neighbour of originator
[ 1090] bidirectional: orig = 105.12.0.20 neigh = 105.12.0.20 => own_bcast = 0, real recv = 0, local tq: 0, asym_penality: 0, total tq: 0
[ 1090] schedule_forward_packet():
[ 1090] forwarding: tq_orig: 0, tq_forw: 0
[ 1090] Forward packet: rebroadcast neighbour packet with direct link and unidirectional flag
[ 1090] Forwarding packet (originator 105.12.0.20, seqno 55800, TTL 49) on interface eth2:0
[ 1090] ------------------ DEBUG ------------------
[ 1090] Forward list
[ 1090] 105.13.0.54 at 1946
[ 1090] Originator list
[ 1090] Originator Router (#/255 #/64): Potential routers
[ 1090] No batman nodes in range ...
[ 1090] ---------------------------------------------- END DEBUG
[ 1090]

[ 1090] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0 105.13.0.54 (from OG: 105.12.0.20, seqno 55800, tq 0, TTL 49, V 4, UDF 1, IDF 1)
[ 1090] HNA information received (1 HNA network):
[ 1090] hna: 105.0.200.6/32
[ 1090] Drop packet: received my own broadcast (sender: 105.13.0.54)
[ 1090]

[ 1950] Forwarding packet (originator 105.13.0.54, seqno 2, TTL 50) on interface eth2:0
[ 1950] count own bcast (schedule_own_packet): old = 0, [ 1950] new = 0
[ 1950]

[ 1950] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0 105.13.0.54 (from OG: 105.13.0.54, seqno 2, tq 255, TTL 50, V 4, UDF 0, IDF 0)
[ 1950] Drop packet: received my own broadcast (sender: 105.13.0.54)
[ 1950]

[ 2710] Received BATMAN packet via NB: 105.12.0.20 , IF: eth2:0 105.13.0.54 (from OG: 105.12.0.20, seqno 55801, tq 255, TTL 50, V 4, UDF 0, IDF 0)
[ 2710] HNA information received (1 HNA network):
[ 2710] hna: 105.0.200.6/32
[ 2710] Other host probably restarted !
[ 2720] updating last_seqno: old 0, new 55801
[ 2720] bidirectional: orig = 105.12.0.20 neigh = 105.12.0.20 => own_bcast = 0, real recv = 1, local tq: 0, asym_penality: 8, total tq: 0
[ 2720] schedule_forward_packet():
[ 2720] forwarding: tq_orig: 0, tq_forw: 0
[ 2720] Forward packet: rebroadcast neighbour packet with direct link and unidirectional flag
[ 2720] Forwarding packet (originator 105.12.0.20, seqno 55801, TTL 49) on interface eth2:0
[ 2720] ------------------ DEBUG ------------------
[ 2720] Forward list
[ 2720] 105.13.0.54 at 2903
[ 2720] Originator list
[ 2720] Originator Router (#/255 #/64): Potential routers
[ 2720] No batman nodes in range ...
[ 2720] ---------------------------------------------- END DEBUG
[ 2720]

[ 2720] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0 105.13.0.54 (from OG: 105.12.0.20, seqno 55801, tq 0, TTL 49, V 4, UDF 1, IDF 1)
[ 2720] HNA information received (1 HNA network):
[ 2720] hna: 105.0.200.6/32
[ 2720] Drop packet: received my own broadcast (sender: 105.13.0.54)
[ 2720]

[ 2910] Forwarding packet (originator 105.13.0.54, seqno 3, TTL 50) on interface eth2:0
[ 2910] count own bcast (schedule_own_packet): old = 0, [ 2910] new = 0
[ 2910]

[ 2910] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0 105.13.0.54 (from OG: 105.13.0.54, seqno 3, tq 255, TTL 50, V 4, UDF 0, IDF 0)
[ 2910] Drop packet: received my own broadcast (sender: 105.13.0.54)
[ 2910]

[ 3980] Forwarding packet (originator 105.13.0.54, seqno 4, TTL 50) on interface eth2:0
[ 3980] count own bcast (schedule_own_packet): old = 0, [ 3980] new = 0
[ 3980]

[ 3980] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0 105.13.0.54 (from OG: 105.13.0.54, seqno 4, tq 255, TTL 50, V 4, UDF 0, IDF 0)
[ 3980] Drop packet: received my own broadcast (sender: 105.13.0.54)
[ 3980] ------------------ DEBUG ------------------
[ 3980] Forward list
[ 3980] 105.13.0.54 at 4917
[ 3980] Originator list
[ 3980] Originator Router (#/255 #/64): Potential routers
[ 3980] No batman nodes in range ...
[ 3980] ---------------------------------------------- END DEBUG
[ 3980]

[ 4920] Forwarding packet (originator 105.13.0.54, seqno 5, TTL 50) on interface eth2:0
[ 4920] count own bcast (schedule_own_packet): old = 0, [ 4920] new = 0
[ 4920]

[ 4920] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0 105.13.0.54 (from OG: 105.13.0.54, seqno 5, tq 255, TTL 50, V 4, UDF 0, IDF 0)
[ 4920] Drop packet: received my own broadcast (sender: 105.13.0.54)
[ 4920]

[ 6870] Forwarding packet (originator 105.13.0.54, seqno 6, TTL 50) on interface eth2:0
[ 6870] count own bcast (schedule_own_packet): old = 0, [ 6870] new = 0
Deleting all BATMAN routes
[ 6870] Originator timeout: originator 105.12.0.20, last_valid 2710
[ 6870] update_routes()
[ 6870] Error - can't delete rule to 105.0.0.0/8: Invalid argument
[ 6870] Error - can't delete rule to 105.0.0.0/8: Invalid argument
[ 6870] Error - can't delete rule to 105.0.0.0/8: Invalid argument
[ 6870] Error - can't delete rule to 105.0.0.0/8: Invalid argument
[ 6870] Error - can't delete rule to 0.0.0.0/0: Invalid argument
[ 6870] Error - can't delete rule to 0.0.0.0/0: Invalid argument
root@OpenWrt:/etc/init.d# 

_________________________________________________________________
Windows Live Writer Beta - Veröffentlichen Sie Multimediainhalte in Ihrem Blog!
http://get.live.com/betas/writer_betas

[-- Attachment #2: Type: text/html, Size: 9592 bytes --]

Re: [B.A.T.M.A.N.] strange default routes

[a.anselmi]

Hi Freifunk

I don't know if you have a typo in your mail but starting batmand as

/usr/sbin/batmand -g 0 -r 0 eth2

means you do not want set any default route (-r equal 0). Moreover, using
-g equal 0 means disabling gateway functionality for the node (normally -g
0 is used on a recpeater/client node only).

What revision are you running and what 0.3 branch (beta or experimental)?
We use beta branch rv674, now migrating to latest rv719 for test purposes).

-- Antonio ...one of robin men :)


> hello batmen, ;)
>
> here in berlin NE we are about to update the batmands on our backbone to
> 0.3.0 . atm our net is mainly running on olsr and batman in parallel for
> testing purpose.
> after some changes in the net we got heavy HNA-hopping with olsr which is
> related to the improper metric in our case. therefore we are somewhat
> forcing the
> migration to batman and got some strange default routes with the most
> recent 0.3.0 builds on some routers:
>
> root@OpenWrt:/etc/init.d# route -n
> Destination  Gateway  Genmask  Flags Metric Ref    Use Iface
> [...]
> 0.0.0.0         0.0.0.0     0.0.0.0      !        0         0       0
> *
> [...]
>
> batmand has been started with the following parameters:  /usr/sbin/batmand
> -g 0 -r 0 eth2
>
> after appearance of this default-route olsr-"clients" cannot use the
> uplink anymore, so further testing  is difficult.
> we have another problem with this build, but cannot investigate further
> because of this behaviour. so any help is appreciated.
>
> thanks
>
> dennis bartsch
> freifunk-bno.de
>
> attached is some console-output:
> ###########################
> root@OpenWrt:/etc/init.d# ifconfig
> eth2 Link encap:Ethernet HWaddr 00:01:36:0D:D2:63
> inet addr:104.13.0.54 Bcast:104.255.255.255 Mask:255.0.0.0
> UP BROADCAST RUNNING MULTICAST MTU:512 Metric:1
> RX packets:105511 errors:0 dropped:0 overruns:0 frame:0
> TX packets:122436 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:61107954 (58.2 MiB) TX bytes:45973166 (43.8 MiB)
> Interrupt:27
>
> eth2:0 Link encap:Ethernet HWaddr 00:01:36:0D:D2:63
> inet addr:105.13.0.54 Bcast:105.255.255.255 Mask:255.0.0.0
> UP BROADCAST RUNNING MULTICAST MTU:512 Metric:1
> Interrupt:27
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:2800 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2800 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:288724 (281.9 KiB) TX bytes:288724 (281.9 KiB)
>
> wifi0 Link encap:UNSPEC HWaddr
> 00-0B-6B-4D-63-8B-00-0A-00-00-00-00-00-00-00-00
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:997788 errors:0 dropped:1221 overruns:0 frame:443273
> TX packets:688240 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:199
> RX bytes:305805070 (291.6 MiB) TX bytes:126339425 (120.4 MiB)
> Interrupt:28
>
> root@OpenWrt:/etc/init.d# /usr/sbin/batmand -g 0 -r 0 eth2:0 -d 4
> WARNING: You are using the unstable batman branch. If you are interested
> in *using* batman get the latest stable release !
> [ 0] Error - can't add rule to 105.0.0.0/8: Invalid argument
> [ 0] Error - can't add rule to 105.0.0.0/8: Invalid argument
> Using interface eth2:0 with address 105.13.0.54 and broadcast address
> 105.255.255.255
> B.A.T.M.A.N. 0.3-beta (compatibility version 4)
> [ 0] Error - can't add rule to 0.0.0.0/0: Invalid argument
> [ 10] Error - can't add rule to 0.0.0.0/0: Invalid argument
> debug level: 4
> [ 20]
>
> [ 940] Forwarding packet (originator 105.13.0.54, seqno 1, TTL 50) on
> interface eth2:0
> [ 940]
>
> [ 940] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0 105.13.0.54
> (from OG: 105.13.0.54, seqno 1, tq 255, TTL 50, V 4, UDF 0, IDF 0)
> [ 940] Drop packet: received my own broadcast (sender: 105.13.0.54)
> [ 940]
> [ 1090] Received BATMAN packet via NB: 105.12.0.20 , IF: eth2:0
> 105.13.0.54 (from OG: 105.12.0.20, seqno 55800, tq 255, TTL 50, V 4, UDF
> 0, IDF 0)
> [ 1090] HNA information received (1 HNA network):
> [ 1090] hna: 105.0.200.6/32
> [ 1090] Creating new originator: 105.12.0.20
> [ 1090] Creating new last-hop neighbour of originator
> [ 1090] bidirectional: orig = 105.12.0.20 neigh = 105.12.0.20 => own_bcast
> = 0, real recv = 0, local tq: 0, asym_penality: 0, total tq: 0
> [ 1090] schedule_forward_packet():
> [ 1090] forwarding: tq_orig: 0, tq_forw: 0
> [ 1090] Forward packet: rebroadcast neighbour packet with direct link and
> unidirectional flag
> [ 1090] Forwarding packet (originator 105.12.0.20, seqno 55800, TTL 49) on
> interface eth2:0
> [ 1090] ------------------ DEBUG ------------------
> [ 1090] Forward list
> [ 1090] 105.13.0.54 at 1946
> [ 1090] Originator list
> [ 1090] Originator Router (#/255 #/64): Potential routers
> [ 1090] No batman nodes in range ...
> [ 1090] ---------------------------------------------- END DEBUG
> [ 1090]
>
> [ 1090] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0
> 105.13.0.54 (from OG: 105.12.0.20, seqno 55800, tq 0, TTL 49, V 4, UDF 1,
> IDF 1)
> [ 1090] HNA information received (1 HNA network):
> [ 1090] hna: 105.0.200.6/32
> [ 1090] Drop packet: received my own broadcast (sender: 105.13.0.54)
> [ 1090]
>
> [ 1950] Forwarding packet (originator 105.13.0.54, seqno 2, TTL 50) on
> interface eth2:0
> [ 1950] count own bcast (schedule_own_packet): old = 0, [ 1950] new = 0
> [ 1950]
>
> [ 1950] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0
> 105.13.0.54 (from OG: 105.13.0.54, seqno 2, tq 255, TTL 50, V 4, UDF 0,
> IDF 0)
> [ 1950] Drop packet: received my own broadcast (sender: 105.13.0.54)
> [ 1950]
>
> [ 2710] Received BATMAN packet via NB: 105.12.0.20 , IF: eth2:0
> 105.13.0.54 (from OG: 105.12.0.20, seqno 55801, tq 255, TTL 50, V 4, UDF
> 0, IDF 0)
> [ 2710] HNA information received (1 HNA network):
> [ 2710] hna: 105.0.200.6/32
> [ 2710] Other host probably restarted !
> [ 2720] updating last_seqno: old 0, new 55801
> [ 2720] bidirectional: orig = 105.12.0.20 neigh = 105.12.0.20 => own_bcast
> = 0, real recv = 1, local tq: 0, asym_penality: 8, total tq: 0
> [ 2720] schedule_forward_packet():
> [ 2720] forwarding: tq_orig: 0, tq_forw: 0
> [ 2720] Forward packet: rebroadcast neighbour packet with direct link and
> unidirectional flag
> [ 2720] Forwarding packet (originator 105.12.0.20, seqno 55801, TTL 49) on
> interface eth2:0
> [ 2720] ------------------ DEBUG ------------------
> [ 2720] Forward list
> [ 2720] 105.13.0.54 at 2903
> [ 2720] Originator list
> [ 2720] Originator Router (#/255 #/64): Potential routers
> [ 2720] No batman nodes in range ...
> [ 2720] ---------------------------------------------- END DEBUG
> [ 2720]
>
> [ 2720] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0
> 105.13.0.54 (from OG: 105.12.0.20, seqno 55801, tq 0, TTL 49, V 4, UDF 1,
> IDF 1)
> [ 2720] HNA information received (1 HNA network):
> [ 2720] hna: 105.0.200.6/32
> [ 2720] Drop packet: received my own broadcast (sender: 105.13.0.54)
> [ 2720]
>
> [ 2910] Forwarding packet (originator 105.13.0.54, seqno 3, TTL 50) on
> interface eth2:0
> [ 2910] count own bcast (schedule_own_packet): old = 0, [ 2910] new = 0
> [ 2910]
>
> [ 2910] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0
> 105.13.0.54 (from OG: 105.13.0.54, seqno 3, tq 255, TTL 50, V 4, UDF 0,
> IDF 0)
> [ 2910] Drop packet: received my own broadcast (sender: 105.13.0.54)
> [ 2910]
>
> [ 3980] Forwarding packet (originator 105.13.0.54, seqno 4, TTL 50) on
> interface eth2:0
> [ 3980] count own bcast (schedule_own_packet): old = 0, [ 3980] new = 0
> [ 3980]
>
> [ 3980] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0
> 105.13.0.54 (from OG: 105.13.0.54, seqno 4, tq 255, TTL 50, V 4, UDF 0,
> IDF 0)
> [ 3980] Drop packet: received my own broadcast (sender: 105.13.0.54)
> [ 3980] ------------------ DEBUG ------------------
> [ 3980] Forward list
> [ 3980] 105.13.0.54 at 4917
> [ 3980] Originator list
> [ 3980] Originator Router (#/255 #/64): Potential routers
> [ 3980] No batman nodes in range ...
> [ 3980] ---------------------------------------------- END DEBUG
> [ 3980]
>
> [ 4920] Forwarding packet (originator 105.13.0.54, seqno 5, TTL 50) on
> interface eth2:0
> [ 4920] count own bcast (schedule_own_packet): old = 0, [ 4920] new = 0
> [ 4920]
>
> [ 4920] Received BATMAN packet via NB: 105.13.0.54 , IF: eth2:0
> 105.13.0.54 (from OG: 105.13.0.54, seqno 5, tq 255, TTL 50, V 4, UDF 0,
> IDF 0)
> [ 4920] Drop packet: received my own broadcast (sender: 105.13.0.54)
> [ 4920]
>
> [ 6870] Forwarding packet (originator 105.13.0.54, seqno 6, TTL 50) on
> interface eth2:0
> [ 6870] count own bcast (schedule_own_packet): old = 0, [ 6870] new = 0
> Deleting all BATMAN routes
> [ 6870] Originator timeout: originator 105.12.0.20, last_valid 2710
> [ 6870] update_routes()
> [ 6870] Error - can't delete rule to 105.0.0.0/8: Invalid argument
> [ 6870] Error - can't delete rule to 105.0.0.0/8: Invalid argument
> [ 6870] Error - can't delete rule to 105.0.0.0/8: Invalid argument
> [ 6870] Error - can't delete rule to 105.0.0.0/8: Invalid argument
> [ 6870] Error - can't delete rule to 0.0.0.0/0: Invalid argument
> [ 6870] Error - can't delete rule to 0.0.0.0/0: Invalid argument
> root@OpenWrt:/etc/init.d#
>
> _________________________________________________________________
> Windows Live Writer Beta - Veröffentlichen Sie Multimediainhalte in Ihrem
> Blog!
> http://get.live.com/betas/writer_betas_______________________________________________
> 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
>

Re: [B.A.T.M.A.N.] strange default routes

[Marek Lindner]

Hi,

> root@OpenWrt:/etc/init.d# route -n
> Destination  Gateway  Genmask  Flags Metric Ref    Use Iface
> [...]
> 0.0.0.0         0.0.0.0     0.0.0.0      !        0         0       0     *
> [...]
>
> batmand has been started with the following parameters:  /usr/sbin/batmand
> -g 0 -r 0 eth2

as Antonio said you disabled all internet traffic via batman.
Furthermore, default routes created by batman are found in table 68 (use "ip 
route ls table 68" to see its content) but "route -n" shows you table 254.


> root@OpenWrt:/etc/init.d# /usr/sbin/batmand -g 0 -r 0 eth2:0 -d 4
> WARNING: You are using the unstable batman branch. If you are interested in
> [ 0] Error - can't add rule to 105.0.0.0/8: Invalid argument
> [ 0] Error - can't add rule to 105.0.0.0/8: Invalid argument
> Using interface eth2:0 with address 105.13.0.54 and broadcast address
> 105.255.255.255 B.A.T.M.A.N. 0.3-beta (compatibility version 4)
> [ 0] Error - can't add rule to 0.0.0.0/0: Invalid argument
> [ 10] Error - can't add rule to 0.0.0.0/0: Invalid argument

Here batman tries to set the policy routing rules and not routing table 
entries. It would be interesting to know the revision you use and could you 
please add the output of (while batmand is running) "ip rule".

Regards,
Marek

Re: [B.A.T.M.A.N.] strange default routes

[elektra]

I'm sorry to say that 0.3beta is not usable at the moment. We are in the 
status of bug-hunting. 

cu elektra 

Re: [B.A.T.M.A.N.] strange default routes

[a.anselmi]

ciao Elektra

need some hunters ? :)

we are strongly testing batmand 0.3-beta since its alpha revisions:
actually rv674 seems the best working one. Today rv719 is now in
testing...
We appreciate very much your work

-- Antonio

> I'm sorry to say that 0.3beta is not usable at the moment. We are in the
> status of bug-hunting.
>
> cu elektra
>
> _______________________________________________
> 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
>

RE: [B.A.T.M.A.N.] strange default routes

[Dennis Bartsch]

[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]

Hello Marek,

we used rev718 ... from yesterday evening ... and all facts you mentioned are right ... we disabled anything that enables batman to set or announce default routes ... thats why we completely don't understand whats happening there. and because the same things happens on a slackware/i386 node AND on an openWRT_post7.09/ixp4xx but not on an openWRT_pre7.06/i386 the failure is not likely to be in the operating system. 

in the evening i'll post what you asked for ... atm i am not in reach of the equipment ...

greets
dennis bartsch

> From: lindner_marek@yahoo.de
> To: b.a.t.m.a.n@open-mesh.net
> Subject: Re: [B.A.T.M.A.N.] strange default routes
> Date: Mon, 15 Oct 2007 16:08:47 +0200
> 
> 
> Hi,
> 
> > root@OpenWrt:/etc/init.d# route -n
> > Destination  Gateway  Genmask  Flags Metric Ref    Use Iface
> > [...]
> > 0.0.0.0         0.0.0.0     0.0.0.0      !        0         0       0     *
> > [...]
> >
> > batmand has been started with the following parameters:  /usr/sbin/batmand
> > -g 0 -r 0 eth2
> 
> as Antonio said you disabled all internet traffic via batman.
> Furthermore, default routes created by batman are found in table 68 (use "ip 
> route ls table 68" to see its content) but "route -n" shows you table 254.
> 
> 
> > root@OpenWrt:/etc/init.d# /usr/sbin/batmand -g 0 -r 0 eth2:0 -d 4
> > WARNING: You are using the unstable batman branch. If you are interested in
> > [ 0] Error - can't add rule to 105.0.0.0/8: Invalid argument
> > [ 0] Error - can't add rule to 105.0.0.0/8: Invalid argument
> > Using interface eth2:0 with address 105.13.0.54 and broadcast address
> > 105.255.255.255 B.A.T.M.A.N. 0.3-beta (compatibility version 4)
> > [ 0] Error - can't add rule to 0.0.0.0/0: Invalid argument
> > [ 10] Error - can't add rule to 0.0.0.0/0: Invalid argument
> 
> Here batman tries to set the policy routing rules and not routing table 
> entries. It would be interesting to know the revision you use and could you 
> please add the output of (while batmand is running) "ip rule".
> 
> Regards,
> Marek
> _______________________________________________
> 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

_________________________________________________________________
Windows Live Writer Beta - Veröffentlichen Sie Multimediainhalte in Ihrem Blog!
http://get.live.com/betas/writer_betas

[-- Attachment #2: Type: text/html, Size: 2992 bytes --]

RE: [B.A.T.M.A.N.] strange default routes

[Dennis Bartsch]

[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]

hey,

the problem semms to be found and very much trivial. the recent openWRT-release (or especially the ixp4xx-port ?!) as well as the rather old slackware10.2 comes _without_ policy-routing compiled into the kernel. figure this out ... an OS for embedded routers comes without advanced routing capabilities ... nothing i've expected. nevertheless batman should detect this and give a hint rather than trying to write to non-existent routing-tables. 

i report back later and tell whether the problems are gone ...

greets,
dennis bartsch (... who should study linux-policy-routing before trying to soft-migrate olsr-to-batman)


> Date: Mon, 15 Oct 2007 16:54:58 +0200
> Subject: Re: [B.A.T.M.A.N.] strange default routes
> From: a.anselmi@oltrelinux.com
> To: b.a.t.m.a.n@open-mesh.net
> 
> ciao Elektra
> 
> need some hunters ? :)
> 
> we are strongly testing batmand 0.3-beta since its alpha revisions:
> actually rv674 seems the best working one. Today rv719 is now in
> testing...
> We appreciate very much your work
> 
> -- Antonio
> 
> > I'm sorry to say that 0.3beta is not usable at the moment. We are in the
> > status of bug-hunting.
> >
> > cu elektra
> >
> > _______________________________________________
> > 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
> >
> 
> 
> _______________________________________________
> 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

_________________________________________________________________
Freunde treffen. Jetzt den Windows Live™ Messenger downloaden!
http://get.live.com/messenger/overview

[-- Attachment #2: Type: text/html, Size: 2228 bytes --]

Re: [B.A.T.M.A.N.] strange default routes

[elektra]

> need some hunters ? :)

Soon! If you have a mesh with a couple of boxes with more than one 
batman-interface (linked by ethernet or multiple radios) we'll be more than 
happy to learn about your results. 

We just have found one important bug, I think. But it is not fixed yet. 

We'll post a message to the list as soon as we think it is fixed and worth a 
try.

Looking forward to the results!

Cheers!

cu elektra

[B.A.T.M.A.N.] development-ipkgs broken

[Dennis Bartsch]

[-- Attachment #1: Type: text/plain, Size: 809 bytes --]

hey,

installation of the latest development-ipkgs (at least the i386 ones) of 0.3-beta fails, because control.tar.gz is missing:

root@NicoAP5G:~# ipkg install http://downloads.open-mesh.net/batman/development/i386/batmand_0.3-beta-rv722_i386-gc-elf-32-lsb-dynamic.tgz
Downloading http://downloads.open-mesh.net/batman/development/i386/batmand_0.3-beta-rv722_i386-gc-elf-32-lsb-dynamic.tgz
ipkg: /tmp/ipkg-p6lIJa/control.tar.gz: No such file or directory
root@NicoAP5G:~# cd ipkg-p6lIJa/
root@NicoAP5G:~/ipkg-p6lIJa# ls
batmand_0.3-beta-rv722_i386-gc-elf-32-lsb-dynamic.tgz

system is kamikaze 7.06

greets
dennis bartsch

_________________________________________________________________
Freunde treffen. Jetzt den Windows Live™ Messenger downloaden!
http://get.live.com/messenger/overview

[-- Attachment #2: Type: text/html, Size: 1118 bytes --]

Re: [B.A.T.M.A.N.] strange default routes

[Marek Lindner]

Hi,

> the problem semms to be found and very much trivial. the recent
> openWRT-release (or especially the ixp4xx-port ?!) as well as the rather
> old slackware10.2 comes _without_ policy-routing compiled into the kernel.
> figure this out ... an OS for embedded routers comes without advanced
> routing capabilities ... nothing i've expected. nevertheless batman should
> detect this and give a hint rather than trying to write to non-existent
> routing-tables.

this sounds odd. A check for policy routing seems to be a good idea but does 
anyone know how to check that ?

Regards,
Marek

Re: [B.A.T.M.A.N.] strange default routes

[Axel Neumann]

Hello,

Just want to add something to what was said in the latest release mail...
> Another big step forward is our new experimental routing code - we call it
> B.A.T.M.A.N. IV. It takes asymmetric routing into account. Currently we
> have several ideas competing for the final inclusion into the release. Feel
> free to join our testing team.
This other idea is implemented in the batman-experimental branch. The 
implementation has shown to run quite stable and performant during the 
Wireless Community Weekend in Graz. Since then it also runs on our local 
mesh-cloud in Berlin/Friedrichshain. 

No need to be a risky explorer to run it. Just download batmand-exp-0.3  from 
http://downloads.open-mesh.net/batman/development/
and start it (as usual) with:
batmand [options] <(w)lan interface> [additional lan interfaces]

Recently, there is also a documentation included in the sources which can be 
accessed as pdf: http://open-mesh.net/batman/doc/BMX/bmx.pdf
or directly from the latest subversion build: 
http://downloads.open-mesh.net/batman/development/sources/batmand-exp_0.3-alpha-current_sources/doc/bmx/

You are very very welcome to test this :-)

ciao,
/axel

On Dienstag 16 Oktober 2007, elektra wrote:
> > need some hunters ? :)
>
> Soon! If you have a mesh with a couple of boxes with more than one
> batman-interface (linked by ethernet or multiple radios) we'll be more than
> happy to learn about your results.
>
> We just have found one important bug, I think. But it is not fixed yet.
>
> We'll post a message to the list as soon as we think it is fixed and worth
> a try.
>
> Looking forward to the results!
>
> Cheers!
>
> cu elektra
>
>
>
> _______________________________________________
> 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

Re: [B.A.T.M.A.N.] 0.3-beta testing

[Jan Hetges]

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

On Tue, Oct 16, 2007 at 12:04:37PM +0200, elektra wrote:
> 
> > need some hunters ? :)
> 
> Soon! If you have a mesh with a couple of boxes with more than one 
> batman-interface (linked by ethernet or multiple radios) we'll be more than 
> happy to learn about your results. 
> 
> We just have found one important bug, I think. But it is not fixed yet. 

i did a test on 12 nodes (two with 2 radios) with rv726 last night
(which was not that successful).
after i put everything back to "productive setup" with 0.2-rv502,
i still had a problem on one of the two-radio-boxes with the 
2nd radio that might be related (seems all ogm's entering that iface
were ignored from time to time). rebooting fixed it and rv502 works 
like before.

cheers

  --Jan


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [B.A.T.M.A.N.] development-ipkgs broken

[Axel Neumann]

Hey Dennis,

On Dienstag 16 Oktober 2007, Dennis Bartsch wrote:
> hey,
>
> installation of the latest development-ipkgs (at least the i386 ones) of
> 0.3-beta fails, because control.tar.gz is missing:
>
> root@NicoAP5G:~# ipkg install
> http://downloads.open-mesh.net/batman/development/i386/batmand_0.3-beta-rv7
>22_i386-gc-elf-32-lsb-dynamic.tgz Downloading

Hmm, the tgz in that folder is a tgz :-) 
I think there has never been a ipk in the development/i386 folder - maybe 
there should. 
Anyway, there are ipk packages for i386 here:
http://downloads.open-mesh.net/batman/development/misc/batmand_0.3-beta-current_i386-gc-elf-32-lsb-static.ipk
or here:
http://downloads.open-mesh.net/batman/development/misc/batmand_0.3-beta-current_i386-gc-elf-32-lsb-dynamic.ipk

If you can confirm that its working for i386-kamikaze I'll open a 
deveopment/i386-kamikaze folder.

Yesterday you also mentioned some problems with the binary packages for ARM 
CPUs. Ipkg and tgz can be found here: 
http://downloads.open-mesh.net/batman/development/armv5te/
Unfortunately, I do not remember the exact problem description ;-)

ciao
/axel

Re: [B.A.T.M.A.N.] development-ipkgs broken

[Alexander Morlang]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Axel Neumann schrieb:
> Hey Dennis,
> 
> On Dienstag 16 Oktober 2007, Dennis Bartsch wrote:
>> hey,
>>
>> installation of the latest development-ipkgs (at least the i386 ones) of
>> 0.3-beta fails, because control.tar.gz is missing:
>>
>> root@NicoAP5G:~# ipkg install
>> http://downloads.open-mesh.net/batman/development/i386/batmand_0.3-beta-rv7
>> 22_i386-gc-elf-32-lsb-dynamic.tgz Downloading
> 
> Hmm, the tgz in that folder is a tgz :-) 
> I think there has never been a ipk in the development/i386 folder - maybe 
> there should. 
> Anyway, there are ipk packages for i386 here:
> http://downloads.open-mesh.net/batman/development/misc/batmand_0.3-beta-current_i386-gc-elf-32-lsb-static.ipk
> or here:
> http://downloads.open-mesh.net/batman/development/misc/batmand_0.3-beta-current_i386-gc-elf-32-lsb-dynamic.ipk
> 
> If you can confirm that its working for i386-kamikaze I'll open a 
> deveopment/i386-kamikaze folder.

how about just maintaing the batman package in kamikaze?
> 
> Yesterday you also mentioned some problems with the binary packages for ARM 
> CPUs. Ipkg and tgz can be found here: 
> http://downloads.open-mesh.net/batman/development/armv5te/
> Unfortunately, I do not remember the exact problem description ;-)
> 
> ciao
> /axel

alex

> _______________________________________________
> 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHF2+uhx2RbV7T5aERAsnzAKCQRILx+ZH+mOBib33/DkeqgoHrXACeNBum
vRmaZRP/Pwo8AzpiXkNNYuA=
=iPnZ
-----END PGP SIGNATURE-----