Bug: cannot disable DHCPv6 Server
-
Hi
I have a management interface /123.
Under the installation DHCPv6 was enabeled. It is now not possible to disable it, as you only can make DPCP pools with the size between /48 to /64. This is not a possiblity with /123. So now I get the error message: The following input errors were detected:
The specified range lies outside of the current subnet.So in other words it is not possible to disable DHCPv6.
-
First off, you shouldn't be making a /123 network. LANs are supposed to be /64.
What happens if you make it a /64 and then try disabling DHCPv6?
-
Hi
And why should I not make a it /123?
Cannot see why it should be manditory to waist 2^64-62 ip numbersAnd yes the problem is the same /64 all the way to /48 and again I want to delete a service not create it. So what the settings are is not relevant.
Regards
Henning -
@hsv said in Bug: cannot disable DHCPv6 Server:
And why should I not make a it /123?
It will break some IPv6 function, such as SLAAC.
As for wasting numbers, the IPv6 address range is so huge that's not an issue. For example, with a /48, you have 65536 /64s, each with 18.4 billion, billion addresses. Are you really that worried about wasting some? About the only place you'd use smaller than a /64 is with point to point links where you could use a /127. The reason for that is using a /64 for a p2p link presents security issues.
-
@jknott said in Bug: cannot disable DHCPv6 Server:
SLAAC
Ok I look into SLAAC. And can see the problem, but I am from a time where you only allocate what you need.
For my setup I need about 80 IP number these are in 15 VLANs.
So I will allocate 15* /64 for 80 static IP numbers. Yes it is possible. But it is a waist. I do not use DHCP in this part of my setup as it is servers.But stil it is a bug you cannot delete a DHCPv6 what ever the settings are.
Thanks for point out the problem with SLAAC
Regards
Henning -
@hsv said in Bug: cannot disable DHCPv6 Server:
So I will allocate 15* /64 for 80 static IP numbers. Yes it is possible. But it is a waist.
You need to rethink your understanding of waste ;) When it comes to IPv6..
As mentioned your typical /48 that should be given to any site allows for 65k /64's - be it you put 1 IP on this vlan or 2000 doesn't really matter when it comes to the assignment of netblock to a specific vlan.
If I recall the math, even with the very tiny, minuscule fraction of ipv6 space that has been allocated for use currently there is enough space to assign ever person on the planet like 4k /48s.
The IPv6 space is so huge it is hard to actually comprehend how big it actually is ;) So you need to forget about old ways of thinking where... Its not like your using a /16 for your vlan in Ipv4 speak..
While yes its odd that such a prefix is used for tiny little vlans with a handful of devices on them - but the powers that be, and all the smart people working on the rfc figured that /64 makes the most sense to use..
-
@johnpoz said in Bug: cannot disable DHCPv6 Server:
You need to rethink your understanding of waste ;) When it comes to IPv6..
And spelling.
If I recall the math, even with the very tiny, minuscule fraction of ipv6 space that has been allocated for use currently there is enough space to assign ever person on the planet like 4k /48s.
GUA takes 1/8 the entire IPv6 address space, with everything else considerably less. Most of the IPv6 address space hasn't been allocated to anything. I've often said here and elsewhere that there are enough /48s to give every person on earth over 4000 of them.
BTW, the GUA addresses start with a 2 or 3, but I've never seen one with a 3.
but the powers that be, and all the smart people working on the rfc figured that /64 makes the most sense to use..
Novell did the same thing with Netware. IIRC, it had a 16 bit network address and 48 bit host address (usually the MAC). The only reason we worry about it with IPv4 is the very limited address space. Initially, everything was what became a Class A address, but that didn't allow enough networks, so classes were created, with the smaller B & C classes allowing more networks.
-
..... and then they invented NAT ....
-
Yep and it's been a curse ever since. Vint Cerf, the guy who invented IP said 32 bits was only meant to be an experiment to prove the concept and would have a larger address space in the final product. Unfortunately, IPv4 "escaped" and we've been suffering with it ever since.
I first started learning about IPv4 in the mid '90s. Even then I knew 32 bits wasn't enough. Then I read about IPv6 in the April 1995 issue of Byte magazine and realized that was what was needed. I've now been running IPv6 on my home network for 11 years (next month).
-
@jknott said in Bug: cannot disable DHCPv6 Server:
Byte magazine
You remember the columnist Jerry Pournelle "Chaos Manor" ?
-
Yep. He was one of my favourite things in that magazine. Incidentally, I have every paper issue of the magazine on my shelves here, going back to Vol 1, #1, Sept 1975. I bought the first three issues in person from the original publisher, Wayne Greene, at an amateur radio convention in Ottawa in 1975. He put the magazine in his wife's name for tax reasons. He then lost it when they divorced.
