291–300 of 496 posts
Noooo, my /22 IPv4 subnet allocation is my personal 401k, I need this money to retire.
You joke, but its exactly how society thinks about housing…
I have it switched off on most networks and servers including my home network. I just don't need it here and I have zero to do with asia. I wish they had just made an IPv5 though. With e.g. 6 bytes instead of 4. 65535 times the current internet should be plenty. I feel like IPv6 is overengineered and I'm glad it didn't take off yet. I like being able to memorise IP addresses, it really helps testing. If I ever do swi…
Earlier quoted context omitted.
> a better web experience than IPv4 That's already the case. IPv6 is often faster because most ISPs these days use cgnat for IPv4.
I have yet to see any ISP use CGNAT here in Sweden. It seems to be a highly regional problem for some reason. Both on mobile and on broadband I get publicly routable IPv4.
Earlier quoted context omitted.
> Of all the things to regulate why bother with this one? It's not like IPv6 is better for the environment or useful to the consumer. If I'm with a small-time ISP that has to use CG-NAT because they don't have the cash to buy/lease enough IPv4 addresses to give one to each CPE WAN interface, then using things like Xbox/PS multiplayer/P2P gaming is no longer possible. Want to host a Minecraft server? Too bad. Are thos…
I did port forwarding in 2010 for a Minecraft server. Basically every router supports it. It wasn't meaningfully more difficult than setting up the server.
Earlier quoted context omitted.
The prefix is too long and it's not the same at every site. When I'm at a different location, the biggest problem is usually figuring out if they use 192.168.0 or 192.168.1 :)
lucky you, IPV6 indeed uses the same prefix everywhere: fe80::
192.168/16 is a private IPv4 subnet (https://en.wikipedia.org/wiki/Private_network#IPv4) and the equivalent for IPv6 is the fd00/8 subnet (RFC 4193).
Earlier quoted context omitted.
> Of all the things to regulate why bother with this one? It's not like IPv6 is better for the environment or useful to the consumer. If I'm with a small-time ISP that has to use CG-NAT because they don't have the cash to buy/lease enough IPv4 addresses to give one to each CPE WAN interface, then using things like Xbox/PS multiplayer/P2P gaming is no longer possible. Want to host a Minecraft server? Too bad. Are thos…
I did port forwarding in 2010 for a Minecraft server. Basically every router supports it. It wasn't meaningfully more difficult than setting up the server.
It’s gotten much worse.
Great example of how fixing things "the correct way" does not seem to work sometimes. They added those new addresses that can store more information.. but this requires a rewrite of old software to make it work. If they used the old >bolting on top< method by extending ip4 from 4 octets to 8 (or more) octets, then old software could be extended much easier too / probably addresses could be simply mechanically transla…
> If they used the old >bolting on top In every fucking IPv6 thread this "just add more addresses" idea comes up. There is no "just" in expanding the address space: """ Whether you expand the address size to 33, 64 or 128 bits, all IPv4 implementations will discard the packets. So it's a matter of mathematical and physical fact that to expand the address size, you must change the protocol, and that means two things i…
Had the original plan been simply "extend address space" instead of "extend address space and while we are at it revamp and rewrite every part of the whole scheme including assignment, discovery, and everything else we see wrong with ipv4"; we would be in a much better place.
Adding extra address bytes would of course require new changes across the internet, but that change would be easier to swallow compared to having to rip and replace large swaths of processes to make ipv6 work because of all of the other changes that came with ipv6.
Also, the stupid idea of turning addresses to hex as the default, and more specifically the dumb :: shortening methods really made it confusing for everyone and didnt help at all in the efforts.
I have it switched off on most networks and servers including my home network. I just don't need it here and I have zero to do with asia. I wish they had just made an IPv5 though. With e.g. 6 bytes instead of 4. 65535 times the current internet should be plenty. I feel like IPv6 is overengineered and I'm glad it didn't take off yet. I like being able to memorise IP addresses, it really helps testing. If I ever do swi…
A changeover to your IPv5 would be just as agonizing as the changeover to IPv6. A system with a larger address space is fundamentally uninteroperable with one with a smaller address space as there is nowhere to put the extra bits in the old protocol. The lack of motivation to move to the new protocol would also be just the same. And as for memorization: do you actually memorize MAC addresses for your interfaces? The…
DNS and mDNS don't "just work". You don't need but probably really want HA for DNS which is overkill for a homelab user, and you really want a fixed address for that DNS, because who wants to fix issues when you can't even address your services, and you really want your routers to have fixed addresses for the same reasons; you need VLAN and/or Avahi reflecting for mDNS, and if you need firewalling on your LAN, have fun dealing with the fact that mDNS clients prefer GUAs, then IPv4s, then ULAs in that order, by RFC rule, and managing GUAs sensibly when your ISP keeps changing your prefix -- well, IPv6 is almost 30 years old and home/SMB equipment still can't handle that reliably or flexibly, if it even lets you do anything besides assign /64s, and there's nothing stopping your ISP from saying "here just have a single /64, sorry if you wanted to actually use IPv6 for anything clever like having multiple subnets, who would ever want that?" So you say "I'll just use DHCPv6" and it turns out that DHCPv6 kind of sucks and it also turns out many devices don't support that by default or at all, including every single Android and Chrome device, for starters.
IPv6 is full of these design issues where you have a lot of things that are supposed to Just Work, Look It's So Much Simpler Than IPv4, and look at all these address bytes (excuse us while we take 64 of them away for no reason), except you discover that nothing Just Works with anything else in mildly nontrivial cases. You end up on a yak shave only to discover no yak underneath, and you end up just having a broken network while standing in a pile of yak hair. The whole story above is just one example. IPv6 is a migraine in RFC form, and if it weren't that I accidentally bought some expensive IOT devices that are IPv6-only, I'd be happy to never touch it. At this point, it would have been a better time-money tradeoff to have thrown those in the trash as soon as I had seen the problem.
Earlier quoted context omitted.
Well yeah, because they can't. Maybe if they could, they would do it more. You probably wouldn't want to host a permanent website from home, although some people do, but you could share a file. It would be popular with game servers, too.
>You probably wouldn't want to host a permanent website from home, although some people do, but you could share a file. bittorent has been around for decades and nobody used it. They emailed files to themselves instead, or used dropbox. This all happened before the ipv4 shortage and people getting moved to CGNAT.
I have it switched off on most networks and servers including my home network. I just don't need it here and I have zero to do with asia. I wish they had just made an IPv5 though. With e.g. 6 bytes instead of 4. 65535 times the current internet should be plenty. I feel like IPv6 is overengineered and I'm glad it didn't take off yet. I like being able to memorise IP addresses, it really helps testing. If I ever do swi…