In message <cagnrvupwf3n9jqmi_txwbxketo_59zdqqapcfcsyfduvqp8...@mail.gmail.com>
Henning Rogge writes:
 
> On Wed, Feb 25, 2015 at 9:36 PM, Curtis Villamizar
> <[email protected]> wrote:
> > In message <[email protected]>
> > Juliusz Chroboczek writes:
> >> As to wireless links -- as far as I'm aware, making efficient use of
> >> wireless L2 information in a routing protocol is an open research problem.
> >
> > Other than signal strength and collision rate, what L2 information is
> > available?  Per MAC information would be nice for the AP side or any
> > node in mesh or adhoc mode but that isn't collected anywhere AFAIK.
>  
> Raw linkspeed and (on Linux) even Throughput to each neighbor... and a lot 
> more.
>  
> Just run "iw wlan0 station dump" on a Linux system with wifi and you
> will be surprised how much information you will get.
>  
> Henning Rogge


Henning,

How can a router make use of throughput to a mostly idle neighbor?
How do you get packets sent to a neighbor that dropped or packets that
a neighbor sent to you that didn't arrive here?  Raw link speed or
packet and byte counts don't by themselves tell you much.  The
equivalent of PPP LQM or MPLS-TP LM OAM would be the sort of thing
needed is you didn't want to use BFD with a high probe rate.

As I said above (or tried to say), the most useful hints that the link
isn't as good as nominal link speed might indicate might be signal
strength and collision rate.  [What I meant above by "available" was
available and useful for "making efficient use of wireless L2
information in a routing protocol" in the quoted text.  So maybe I was
too terse in saying that.]

Thanks for the response though.  I use FreeBSD and other than rate and
S/N there isn't much, so could you send me sample output from a Linux
host or better yet a Linux AP with a few "neighbors".  We can take
this off list and discuss the sample output but so far "lots of stuff"
(sic) doesn't help.

Curtis


ps - maybe I should stop procrastinating and compile and flash openwrt
and see for myself, but for now ...

_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to