On 2/20/15 8:50 AM, Dave Taht wrote:
The homenet working group has been laboring for several years now to
find ways to make ipv6 more deployable to home (and presumably small
business) users.
In addition to multiple specification documents some code has been
produced to try and make things
Is there an hncpd howto somewhere?
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
On Sat, 21 Feb 2015, Juliusz Chroboczek wrote:
The client is running a stub implementation of the routing protocol.
I thought we already had decided we didn't require changes to the host?
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
L3 - route injection (got a routing protocol there already, use it)
This sounds like it needs at least a coordination protocol between the APs?
NO, just between the first-hop (homenet) routers. Should work with unchanged
of the shelf crap-APs as long as they're attached to a homenet router.
retitling this because I really, really, really, would like more
people using hncpd
and providing feedback on that, rather than arguing over specification
documents.
On Fri, Feb 20, 2015 at 2:14 PM, Markus Stenberg markus.stenb...@iki.fi wrote:
On 20.2.2015, at 22.01, Dave Taht
On Sat, Feb 21, 2015 at 09:29:17PM +0100, Juliusz Chroboczek wrote:
(Recall that multicast is 2Mbit/s at the phy. 13ms for a full-size frame,
not counting the cost of collisions.)
Ok. But we also need a way to support fast router redundancy IMHO.
Could you please explain what you mean?
On Sat, Feb 21, 2015 at 08:48:29PM +0100, Juliusz Chroboczek wrote:
(Recall that multicast is 2Mbit/s at the phy. 13ms for a full-size frame,
not counting the cost of collisions.)
Ok. But we also need a way to support fast router redundancy IMHO.
Cheers
Toerless
Something as simple as
(Recall that multicast is 2Mbit/s at the phy. 13ms for a full-size frame,
not counting the cost of collisions.)
Ok. But we also need a way to support fast router redundancy IMHO.
Could you please explain what you mean?
-- Juliusz
___
homenet
