On 16/09/13 11:49, Roy Marples wrote:
On 16/09/2013 11:44, Simon Kelley wrote:
That links seems to refer entirely to DHCPv6. Dnsmasq will allow
non-64 prefix lengths for DHCPv6. What we're talking about here is
rfc4861 router advertisements and I'm not sure how the discussion you
reference appli
On 16/09/2013 11:44, Simon Kelley wrote:
That links seems to refer entirely to DHCPv6. Dnsmasq will allow
non-64 prefix lengths for DHCPv6. What we're talking about here is
rfc4861 router advertisements and I'm not sure how the discussion you
reference applies there.
It shows a case where a RA
On 16/09/13 11:16, Roy Marples wrote:
On 16/09/2013 10:44, Simon Kelley wrote:
SLAAC works by generating addresses by composing the prefix and the
so-called Interface Identifier.
RFC-4291 says: "For all unicast addresses, except those that start
with the binary value 000, Interface IDs are requ
On 16/09/2013 10:44, Simon Kelley wrote:
SLAAC works by generating addresses by composing the prefix and the
so-called Interface Identifier.
RFC-4291 says: "For all unicast addresses, except those that start
with the binary value 000, Interface IDs are required to be 64 bits
long and to be const
Am Mon, 16 Sep 2013 10:44:01 +0100
schrieb Simon Kelley :
> SLAAC works by generating addresses by composing the prefix and the
> so-called Interface Identifier.
>
> RFC-4291 says: "For all unicast addresses, except those that start
> with the binary value 000, Interface IDs are required to be 6
On 16/09/13 10:18, Quintus wrote:
Hi there,
I’m trying to divide my home network into useful IPv6 subnets. I’ve got
a /64 network from SiXxs and wanted to use a /80 for cable clients and
another /80 for wifi clients (with the other /80s staying unused for
now). Here’s what I’ve tried for cable:
Hi there,
I’m trying to divide my home network into useful IPv6 subnets. I’ve got
a /64 network from SiXxs and wanted to use a /80 for cable clients and
another /80 for wifi clients (with the other /80s staying unused for
now). Here’s what I’ve tried for cable:
---
