Juliusz Chroboczek <j...@irif.fr> wrote:
> That's exactly the kind of situation that we'd like Homenet to work well
> in. Connection A is a 1.5Mbit/s leased line, it's rock solid, and has
> rock solid infrastructure behind it. Connection B is consumer FTTH at
> 1Gbit/s, it's flaky, and it's backed by infrastructure that works on
> Mondays only.
> Quite frankly, if it's not for combining fast with reliable, I just don't
> see what's the purpose of having multiple connections.
The 1.5Mb/s is for "work" use only (is very low-latency too), but tolerates
some moderate amount of non-work traffic, as long as it's not so much that
anyone notices. That's why you'd have two connections. Work traffic SHOULD
not go out the flaky connection.
That the result is what you describe (which I believe 200%...) is what
happens is not the plan. It's not why the multiple connections are justified.
Now, assume a second spouse working at home, with another "work" connection :-)
(And of course, don't forget the mesh network to the neighbourhood)
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
