Re: AW: [B.A.T.M.A.N.] Experiences with B.A.T.M.A.N. 0.3-beta rv767
Hi On Sonntag 04 November 2007, Marek Lindner wrote: ... > > The batman gateway checks if the tunnelled packet has a known wifi IP > address corresponding to a known virtual IP address. 104.61.13.37 is > obviously a wrong IP address. I would guess that this is an OLSR > address ? May be we have a problem with gatewaying alias interfaces ? > > @Axel: Did you experience that kind of problem ? May be we have to set > the source address explicitely. I look into that. No, not like that. But others. For example you may temporary see messages like that if for, some reason, the GW restarts. /axel
AW: AW: [B.A.T.M.A.N.] Experiences with B.A.T.M.A.N. 0.3-beta rv767
> May be we have to set the source address explicitely. I look into that. I issued a patch. Could you test that for me (rev 779) ? At the moment I can't do it myself. Regards, Marek Machen Sie Yahoo! zu Ihrer Startseite. Los geht's: http://de.yahoo.com/set
AW: [B.A.T.M.A.N.] ideas for 0.3
> How about forwarding the average TQ-Value of the best ranking neighbor instead > of the actual incoming value? This should avoid inconsistency amongst > TQ-Values to a great degree! That is what we do now ! It is the reason for the "10 seconds loops". Therefore I proposed to forward the incoming value instead of the average. I think you mixed it up. ;-) Regards, Marek Machen Sie Yahoo! zu Ihrer Startseite. Los geht's: http://de.yahoo.com/set
[B.A.T.M.A.N.] ideas for 0.3
One more idea: How about forwarding the average TQ-Value of the best ranking neighbor instead of the actual incoming value? This should avoid inconsistency amongst TQ-Values to a great degree! cu elektra > >> We'll post a message to the list as soon as we think it is fixed and > >> worth a try. > > > > i never saw that post (maybe i missed it?), so i only tested exp-0.3 :) > > Right - i think it is ready to be tested now. > > @Elektra: What about activating my latest routing improvement ? > > > > > Heute schon einen Blick in die Zukunft von E-Mails wagen? > www.yahoo.de/mail > > ___ > B.A.T.M.A.N mailing list > b.a.t.m@open-mesh.net > https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
AW: [B.A.T.M.A.N.] batmand-exp test in the developing world
>> We'll post a message to the list as soon as we think it is fixed and >> worth a try. > i never saw that post (maybe i missed it?), so i only tested exp-0.3 :) Right - i think it is ready to be tested now. @Elektra: What about activating my latest routing improvement ? Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail
AW: [B.A.T.M.A.N.] Experiences with B.A.T.M.A.N. 0.3-beta rv767
Hi, > We playing around with B.A.T.M.A.N. 0.3-beta rv767 in our leipziger > Freifunk-testing-Firmware (based on v1.6.10): > the Routing works fine (if i start "batmand eth1:bat vlan1:bat") - > great work! exciting to hear. Keep us informed about all the trouble you experience so that we can work on it. > but the gateway-function (option "-r 2") drives me mad: > > * why the tunnel-interface (gateX) now have IP-Adresses!? Simply said the "get virtual IP on demand" mode had some problems especially with the fact that the interface has no IP address when the first packets arrive. So we went through a whole process of fixing that following problems by setting the new address in these packets, then recalculating the checksums, implementing a lightweight NAT for returning packets. After all that there were still issues which could not be addressed easily. On the other hand we give away the chance to check whether the tunnel port is blocked or not until the user needs the connection. Now batman hands out IP addresses proactively. We are waiting for real world feedback to see if we run into new problems. So far it seems to work. > * what this log-message (on gateway) wants to tell me? (105.61.89.81 is > an Node who wants to build up an gateway-tunnel) >> Nov 3 16:49:38 (none) kern.err batmand[1819]: Error - got packet from >> unknown client: 105.61.89.81 (virtual ip 104.61.13.37) The batman gateway checks if the tunnelled packet has a known wifi IP address corresponding to a known virtual IP address. 104.61.13.37 is obviously a wrong IP address. I would guess that this is an OLSR address ? May be we have a problem with gatewaying alias interfaces ? @Axel: Did you experience that kind of problem ? May be we have to set the source address explicitely. I look into that. > * I noticed, that LAN-clients (on batmannodes) sometimes get 169.x.y.z > Addresses per DHCP if i start batmand with "-r 2"-option? If so that has nothing to do with batman. Even if batman has an internal mini "give IP" server it is an own lightweight protocol which is not compatible with the real DHCP. Actually this IP range is to be used if you can't connect to a DHCP server and have no fixed address set. > B.A.T.M.A.N. 0.2 worked fine, but we want/must use B.A.T.M.A.N. 0.3, > because the available policy-routing cause no problems with parallel > driven olsrd. I understand. Regards, Marek Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail
Re: [B.A.T.M.A.N.] batmand-exp test in the developing world
> > >> I'm sorry to say that 0.3beta is not usable at the moment. > > > > > > and my tests with 0.3-beta_~rv720 showed path-detection pretty > > > broken > > > > Well, rev720 is almost 3 weeks old. During that time the new > > routing algo was quite unstable. Did you also try the newer > > snapshots ? > > On Tue, Oct 16, 2007 at 12:04:37PM +0200, elektra wrote: > > We'll post a message to the list as soon as we think it is fixed and > > worth a try. > > i never saw that post (maybe i missed it?), so i only tested exp-0.3 :) > You didn't miss it. I still don't consider it usable. cu elektra
[B.A.T.M.A.N.] Experiences with B.A.T.M.A.N. 0.3-beta rv767
We playing around with B.A.T.M.A.N. 0.3-beta rv767 in our leipziger Freifunk-testing-Firmware (based on v1.6.10): the Routing works fine (if i start "batmand eth1:bat vlan1:bat") - great work! but the gateway-function (option "-r 2") drives me mad: * why the tunnel-interface (gateX) now have IP-Adresses!? * what this log-message (on gateway) wants to tell me? (105.61.89.81 is an Node who wants to build up an gateway-tunnel) > Nov 3 16:49:38 (none) kern.err batmand[1819]: Error - got packet from > unknown client: 105.61.89.81 (virtual ip 104.61.13.37) > Nov 3 16:49:40 (none) kern.err batmand[1819]: Error - got packet from > unknown client: 105.61.89.81 (virtual ip 104.61.13.37) > Nov 3 16:49:41 (none) kern.err batmand[1819]: Error - got packet from > unknown client: 105.61.89.81 (virtual ip 104.61.13.13) > Nov 3 16:49:42 (none) kern.err batmand[1819]: Error - got packet from > unknown client: 105.61.89.81 (virtual ip 104.61.13.13) > Nov 3 16:49:43 (none) kern.err batmand[1819]: Error - got packet from > unknown client: 105.61.89.81 (virtual ip 104.61.17.28) > Nov 3 16:49:43 (none) kern.err batmand[1819]: Error - got packet from > unknown client: 105.61.89.81 (virtual ip 104.61.13.37) (there is no rule to throw 104/8 to batman tables) > r...@13-18:~# ip rule show > 0: from all lookup local > 6600: from all to 105.0.0.0/8 lookup 66 > 6601: from all to 105.61.89.80/28 lookup 66 > 6699: from all lookup 65 > 6700: from all to 105.0.0.0/8 lookup 67 > 6701: from all to 105.61.89.80/28 lookup 67 > 32766: from all lookup main > 32767: from all lookup default > r...@13-18:~# ip r s t 65 > throw 105.61.89.81 proto static > 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.88.193 via 105.61.89.90 dev vlan1 proto static src 105.61.89.81 > r...@13-18:~# ip r s t 66 > 105.61.17.32 via 105.61.89.90 dev vlan1 proto static src 105.61.89.81 > throw 105.61.89.81 proto static > 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.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 > r...@13-18:~# ip r s t 67 > throw 105.61.89.81 proto static > unreachable default proto static > r...@13-18:~# batmand -bcd 2 > WARNING: You are using the unstable batman branch. If you are > interested in *using* batman get the latest stable release ! > Gateway (#/255) Nexthop [outgoingIF], gw_class ... > [B.A.T.M.A.N. 0.3-beta rv767, MainIF/IP: eth1:bat/105.61.13.18, UT: 0d > 0h 4m] >105.61.89.89(255)105.61.89.89 [ vlan1:bat], gw_class 65 - > 16MBit/4MBit, reliability: 0 >105.61.17.35(255)105.61.89.89 [ vlan1:bat], gw_class 65 - > 16MBit/4MBit, reliability: 0 * I noticed, that LAN-clients (on batmannodes) sometimes get 169.x.y.z Addresses per DHCP if i start batmand with "-r 2"-option? B.A.T.M.A.N. 0.2 worked fine, but we want/must use B.A.T.M.A.N. 0.3, because the available policy-routing cause no problems with parallel driven olsrd. Regards tetzlav
Re: [B.A.T.M.A.N.] batmand-exp test in the developing world
Hello Jan - indeed, your report is the wage for our work. Your application is one of our prime targets. Cheers! cu elektra
Re: [B.A.T.M.A.N.] batmand-exp test in the developing world
On Sun, Nov 04, 2007 at 12:53:13AM +, Marek Lindner wrote: [..snip..] > > >> I'm sorry to say that 0.3beta is not usable at the moment. > > and my tests with 0.3-beta_~rv720 showed path-detection pretty > > broken > > Well, rev720 is almost 3 weeks old. During that time the new > routing algo was quite unstable. Did you also try the newer > snapshots ? On Tue, Oct 16, 2007 at 12:04:37PM +0200, elektra wrote: > We'll post a message to the list as soon as we think it is fixed and > worth a try. i never saw that post (maybe i missed it?), so i only tested exp-0.3 :) cheers --Jan signature.asc Description: Digital signature
Re: AW: [B.A.T.M.A.N.] batmand-exp test in the developing world
On Nov 4, 2007, at 1:53 AM, Marek Lindner wrote: We experienced ~ 200% increase in cpu efficiency and ~ 300% in network efficiency between 0.4.10 and 0.5.4. c.f. http://olsr.funkfeuer.at for graphs. Wow - you are part of the marketing team ? there is no marketing team. however there was a constant anti marketing again and again about the OLSR-NG attempts in vienna. So I wanted simply to make clear that there is *a*lot* of progress happening in "good old" olsrd by now. A lot of progress! I guess B.A.T.M.A.N. has over 1000% increase in efficiency between 0.01 and now. ;-) big deal.
AW: [B.A.T.M.A.N.] batmand-exp test in the developing world
> We experienced ~ 200% increase in cpu efficiency and ~ 300% in > network efficiency between 0.4.10 and 0.5.4. > c.f. http://olsr.funkfeuer.at for graphs. Wow - you are part of the marketing team ? I guess B.A.T.M.A.N. has over 1000% increase in efficiency between 0.01 and now. ;-) >> I'm sorry to say that 0.3beta is not usable at the moment. > and my tests with 0.3-beta_~rv720 showed path-detection pretty > broken Well, rev720 is almost 3 weeks old. During that time the new routing algo was quite unstable. Did you also try the newer snapshots ? > from the "user-feeling" it's the way best mesh-daemon i tried so far. > for fairness i have to say that my olsrds are neither all up to date, > nor pretty well configured, but i beleave olsrd is a > "historically crippled design" and the evolution of batmand will > show the possibilities of wireless mesh networking. > this all needs some further testing and improvements, but > i'm pretty sure all the good bits will find their way into 0.3-final. > Thanks to Elektra, Marek, Axel and everyone else who put so much > energy into this amazing peace of free software. Thank you very much for your testing efforts and all the feedback. That is wait excites us most. :-) Keep up the routing, Marek __ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever
