7 ms·
But how do you know you should use a /64 mask? One of my hosting providers assigns much smaller subnets. Some others assign /56. You are at risk of blocking man
by cm2187 9y ago
But how do you know you should use a /64 mask? One of my hosting providers assigns much smaller subnets. Some others assign /56. You are at risk of blocking many legitimate IPs and missing many others.
- profmonocle 9y ago> But how do you know you should use a /64 mask? One of my hosting providers assigns much smaller subnets. It's baked into the standard that IPv6 networks shouldn't be smaller than /64. If a provider is disregarding the standard so blatantly I would probably avoid them. Really, why on earth would a cloud provider be so stingy with IPv6 that they'd give less than a /64 per customer? ARIN gives out /32s like candy and a single /32 can be split into ~4.3 billion /64s.
- dingo_bat 9y ago/32 is like you can build your own entire internet!
- daurnimator 9y agoSadly the ISP for internet to our office building only gave out a /65... that we are meant to share with ~20 companies. Suffice to say I've got IPv6 to the internet gateway, but no further. => They fulfilled their contractual obligation to "provide ipv6 connectivity", while being entirely useless. They'll probably use us as a stat to prove that no one wants ipv6 anyway... There is no choice in provider.
- cm2187 9y agoBut why /65 is such a big deal? You can divide it in 32 different /70 subnets, one per company. That still leave you with 2^58 IPs by company. You can still even use MAC addresses in your IPs.
- zAy0LfpBZLC8mAC 9y agoSLAAC on ethernet requires a /64. A provider assigning you anything but at least a /48 is pure incompetence, if it's explicitly for 20 companies, they really should be giving out a /43.
- cm2187 9y agoYeah but stateful vs stateless DHCP is really a minor problem.
- deleted 9y ago[deleted]
- zAy0LfpBZLC8mAC 9y ago> is really a minor problem. So, it's a problem. For no reason at all. Also, no, it's not really just a minor problem. Reconfiguring your one client device might be trivial, but that's really not the question. The question is what you do with a setup with a few dozen devices/machines/routers/whatever. First of all, even if you do a new setup, it's idiotic that you'd have to consider the idiosyncrasies of your ISP when designing your network, instead of choosing whatever setup fits your internal requirements best. That you possibly cannot buy a certain printer because it doesn't support DHCPv6, or whatever. But it's a lot worse when you think about switching ISPs with an existing setup: Having to completely rebuild your network because of your ISP's idiocy is ... well, idiotic. Suppose you have a bunch of routers that do SLAAC for end devices and obtain prefixes via DHCP-PD from the uplink router. Really, all that should be technically required in such a setup to switch from one provider to another would be to unplug the old line, plug in the new line, everything should renumber automatically, while keeping the exact same network structure. Good luck reconfiguring all of that to work with a /65 ... and when you have done that, tell me again that it's a minor problem.
- cm2187 9y agoYou don't need to set up your clients with IPv6 more than you need with IPv4. Your router will do DHCP in just the same way. To me this is only a minor inconvenience.