Juliusz Chroboczek <[email protected]> wrote: >> If you have hardware with a built-in switch that can report the link-speed,
> The WNDR3700v2 under OpenWRT appears to do so:
> # swconfig dev switch0 show | grep 'link:'
> link: port:0 link:down
> link: port:1 link:down
> link: port:2 link:up speed:100baseT full-duplex
> link: port:3 link:down
> link: port:4 link:down
> link: port:5 link:up speed:1000baseT full-duplex txflow rxflow auto
> but to use this information, you need to know:
> 1. that vlan1 on eth0 is connected to ports 0 through 3 of switch0;
> 2. that neighbour fe80::dead:beef is connected over port 2.
> You could do (1) with a small amount of model-specific code (yuck), but
> I have no idea how to do (2). Consult the ND cache to find out the
> neighbour's MAC, then find a way to snoop on the switch's forwarding
table?
And assuming that you could do this, you still don't know that
fe80::dead:beef isn't connected via some *other* layer-2 switch external to
the WRT.
So, if anyone is basing their convergence time summaries upon loss of link,
vs keep-alive timeouts, then they need to recalculate, because we are only
rarely gonna see link-down.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
