hi lui,

the batstat looks quite nice! the animation is also a little eye candy

but the output of "ip route" is still hardcoded to an 105.* address range

can you fix this in the next version? we use 103.* ... you should already know ... but in general it is better to make the fiilter dynamic, referred to the used network

good job, thx!

have a nice weekend felix

_________________________________________________________________ Haben Spinnen Ohren? Finden Sie es heraus – mit dem MSN Suche Superquiz via http://www.msn-superquiz.de Jetzt mitmachen und gewinnen!

Hi,

freifunk-batman_0.83.ipk is out now.

hope it's usefull Lui

CHANGES: # ----------------------------------------------------------------------------

ToDo: * Info: better representation of status and link-relations... * Translations: it-fr-nl-<place your language here> * Config: 'choosing' a prefered gateway * ... * keep close to the hight development-cycles of batmand ;-) * watching out for B.A.T.M.A.N.-IV ;-)

Changes (0.82 -> 0.83) + "Raider is Twix" and S55batman is S66batman now - lowers a timestamp problem with S60rdate + removed S54(/S65)robin

Changes (0.81 -> 0.82) + replaced option d|debug with log... (S55batman log <mode> <time>) + fixed cron entry + added tun-ex + added: S55... v like batmand -v

Changes (0.80 -> 0.81) + use /etc/ff_bat.config and remove extensive use of nvram (/-commit) + language *switch* via config... + layout issues

Changes (0.7x -> 0.80) + (merged) support for non-WRT like hardware (i.e SE505) and tagged-vlans... + community network support: choose olsr->batman network (/8 /16 /24) transition. + multi language support: de, en (please help with your addional translations) + status-page with links to known nodes + B.A.T.M.A.N.-III v0.2++ client-mode info on router-frontpage + S55batman initscript opens by default traceroute ports + re-designed bad handling of NVRAM-vars # ----------------------------------------------------------------------------

...this last informations are still valid:

Sent: Freitag, 12. Januar 2007 07:40 To: B.A.T.M.A.N.-ML Subject: [B.A.T.M.A.N.] freifunk-batman-de (0.73 "vampimated")

Hi all,

cleanups - and more... ;-)

!!!Important!!! For those of you, who have installed any previous versions - 1st: #>ipkg remove freifunk-batman-de

For others: freifunk-batman-de is a WebUI-Plugin for the freifunk-firmware (->[1]) It allows to easily configure and manage all aspects of the batman-daemon in a side-by-side environment with olsr (even for unskilled users). [...] The main goal is to raise the amount of batman-nodes in 'a mesh' of heterogeneous skilled node owners over 'the critical-mass' in the phase of development and testing... and of course, to make it easy for myself to manage testing with 10++ batman-nodes.

[...]

Find it at: http://freifunk.schmudde.com/ipkg

Regards Lui

[1] - http://ff-firmware.sourceforge.net/

Hello, Lui and everyone.

Thank you for your kind work. I've tried.

machine: buffalo whr-hp-g54 x 2 http://www.buffalo-technology.com/products/product-detail.php?productid=124&... one as gateway node (gw) and another as only node (nd)

It seems to work well. gw: <nvram> ff_bat_cron=on ff_bat_gw_uplink=11 ff_bat_netmig=192.168.1/192.168.2 ff_bat_ran_if=eth1:bat ff_bat_ran_ip=192.168.2.1 ff_bat_ran_on=1 ff_bat_ran_pf=24 ff_bat_start=1

root@freifunk-batman1:~# ps |grep batman 1157 root 400 S batmand -g 11 eth1:bat 1162 root 400 S batmand -g 11 eth1:bat 1164 root 400 S batmand -g 11 eth1:bat 1168 root 400 S batmand -g 11 eth1:bat 2241 root 420 R grep batman root@freifunk-batman1:~# ping 192.168.2.2 PING 192.168.2.2 (192.168.2.2): 56 data bytes 64 bytes from 192.168.2.2: icmp_seq=0 ttl=64 time=1.9 ms 64 bytes from 192.168.2.2: icmp_seq=1 ttl=64 time=1.4 ms 64 bytes from 192.168.2.2: icmp_seq=2 ttl=64 time=1.4 ms 64 bytes from 192.168.2.2: icmp_seq=3 ttl=64 time=1.4 ms

nd: <nvram> ff_bat_cron=on ff_bat_gw_choose=2 ff_bat_gw_uplink=0 ff_bat_netmig=192.168.1/192.168.2 ff_bat_ran_if=eth1:bat ff_bat_ran_ip=192.168.2.2 ff_bat_ran_on=1 ff_bat_ran_pf=24 ff_bat_start=1

root@freifunk-batman2:~# ps |grep batman 7236 root 472 S batmand -r 2 eth1:bat 7239 root 472 S batmand -r 2 eth1:bat 7240 root 472 S batmand -r 2 eth1:bat 20048 root 268 S grep batman root@freifunk-batman2:~# ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1): 56 data bytes 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=3.4 ms 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1.4 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.4 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.4 ms

I have some question. (1) gw shows tun interface,

root@freifunk-batman1:~# ifconfig |grep tun tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 root@freifunk-batman1:~#

but nd shows no tun interface.

root@freifunk-batman2:~# ifconfig |grep tun root@freifunk-batman2:~#

Is this right? Is any setting missed?

(2) From webIF of nd, batman info shows ------------------------------------------------------------------ | Please wait... | S66batman: Connecting B.A.T.M.A.N. (routings) Statistics: | S66batman: # batmand -c -b -d 1 | 192.168.2.1, GW: 192.168.2.1(59) via: 192.168.2.1(59) ------------------------------------------------------------------- | S66batman: Connecting B.A.T.M.A.N. (gateways) | S66batman: # batmand -c -b -d 2 Gateways: | 192.168.2.1 via: 192.168.2.1(59), gw_class 11 - >6 MBit, reliability: 9 | No gateways in range ... -------------------------------------------------------------------- Does the last line "No gateways in range ..." mean failure to find gateway? If so, why does it happen?

regards,

zukky

Lui wrote:

Hi,

freifunk-batman_0.83.ipk is out now.

hope it's usefull Lui