3

I'm trying to set up radvd on a 6RD configuration (on Linux), where I have a /64 subnet, and I'm trying to use it on two distinct physical networks, so I'm trying to give each of them a /80 subnet. However, when I start radvd on these interfaces, it says this:

radvd[3987]: prefix length should be 64 for int

(int being the name of one of the interfaces.)

I know that stateless autoconfiguration doesn't work on subnets that are larger than /64, like a /48 subnet, but AFAIK it's supposed to work on anything that is smaller than /64, so /80 shouldn't be a problem. The final effect, now, is that radvd simply advertises the wrong subnet prefix, effectively "removing" the first 16 bits of it.

What is this? Am I all wrong on that, is radvd buggy, or is there some configuration option that I'm missing?

Dolda2000
  • 1,253

2 Answers2

5

radvd is not buggy, IPv6 subnets must really be a /64 for stateless autoconfiguration to work. If you use anything else you will have to manually configure each device on the network. Devices that don't offer the option of manual configuration will not work at all.

Unless you really know what you are doing (like using a /127 on point-to-point links between routers) you should always use a /64 for LANs.

Sander Steffann
  • 4,802
0

Please note, that autogenerated IPv6 address is like 2001:db8:1234:1234:xxxx:xxff:feyy:yyyy where xxxxxx and yyyyyy is MAC (with one bit reversed). That's why radvd 9or any other stateless configuration tool) cannot use any other prefix length instead.

For other lengths you can still use stateful tool - DHCPv6.

mateusza
  • 365