Hi,

Sounds good, but noticed some small typos:

thanks! I corrected them on my end. Can any native English speaker check the text and give us her/his blessing ?

And maybe you should increase "Linux 2.6.20" to "Linux 2.6.21" with your newest backporting efforts.

I kept the "Linux 2.6.20" in the hope that the recent patches would also make our code work on this old release. I just did not test it. Do we have reason to believe that it won't work ?

Regards, Marek

Hi Marek,

Alas, I don't know enough about how it works to be of much help.

I *DO* have it running on a pair of Meraki minis with villagetelco software. Seems to work *VERY* well.

I always seem to be looking for a real-time quality monitor so I can adjust antennas, check range, watch radios change by themselves, etc. i.e.- A real-time chart recorder widget. Thus my suggestion.

Congratulations to all :).

warm regards, Wiz

On Mon, 3 May 2010, Marek Lindner wrote:

Hi,

...

I wonder if a brief explanation of how TQ is determined belongs here too?

I find it quite hard write a short paragraph about the TQ stuff, since I either end up simplifying the whole matter or writing too much text. On top of that, I'm not so sure what the casual reader would expect to find in the README regarding the routing algo. Maybe you could draft something and we go from there ?

Cheers, Marek

On mar, mag 04, 2010 at 09:59:43 +0800, Marek Lindner wrote:

Hi,

...

I *DO* have it running on a pair of Meraki minis with villagetelco software. Seems to work *VERY* well.

glad to hear that !

...

I always seem to be looking for a real-time quality monitor so I can adjust antennas, check range, watch radios change by themselves, etc. i.e.- A real-time chart recorder widget. Thus my suggestion.

You are not the first one with such a feature request but let me point out that batman is not the right tool for the job. If you want to finetune antennas batman is way too slow and imprecise, since all it does is measuring packet loss within a certain time frame. Deriving antenna directions from that is more magic than real sience.

I'd rather suggest a tool like "horst" (Highly Optimized Radio Scanning Tool - http://br1.einfach.org/tech/horst/) which hooks into your wifi driver to retrieve real-time data about the link quality to your neighbors. Of course, such a tool is highly dependend on the wifi driver and probably does not support all the drivers in the world but I'm sure it can be extended.

Hi, thank you very much for your suggestion! It is very usefull here! :)

Regards, Marek

Hi,

I reviewed it and made some changes. There are also some suggestion inside [ ] marks.

thanks for all the input so far.

Changelog: * typos found by Sven and Andrew corrected * some output added as suggested by Andrew * increased "Linux 2.6.20" to "Linux 2.6.21" since we don't support 2.6.20 at this moment * piped the README through nroff to get a consistent look & feel

The file is in the repos now.

Cheers, Marek

On Tuesday 04 May 2010 13:14:36 Andrew Lunn wrote:

It looks like this stage made use of UTF-8, or some sort of extended character set:

vpn, etc ... (anything with ethernet<E2><80><90>style layer 2). It compiles against and should work with Linux 2.6.21 <E2><80><90> 2.6.33. Supporting older versions is not planned, but it<E2><80><99>s probably easy to backport

Ok, just committed a utf8 stripped version. You are probably right: nroff added them.

I don't have a locale set, being an English speaker and not needing umlauts, accents, etc. I guess most embedded systems also don't have locale support.

Well, I don't think people would go through the hassle of copying the README onto a router to read it over the serial console. ;-)

Cheers, Marek