Jump in the discussion.

No email address required.

He’s not wrong.

EDIT- I mean in the complexity of it. It’s too much to remember.

Jump in the discussion.

No email address required.

If you're using it in a basic home network there's actually less. You'll just use "SLAAC" for IPs (which is an autoconfig system only possible with the insane amount of addresses) and mDNS for device hostnames (iDevices already use this).

If you're designing a business network it's pretty similiar with DHCPv6.

Jump in the discussion.

No email address required.

I guess my problem here is the concatenation? Like the ::::and I have shitty vision so it fricks w me.

Jump in the discussion.

No email address required.

how can two dots ( : ) be harder to see than one dot ( . )?

Jump in the discussion.

No email address required.

I AM DRUNK YOU QUEEN

Jump in the discussion.

No email address required.

You'll usually see that mentioned but it's orthogonal to good design to use the addresses directly. Like some guy in the comments says "IP addresses are for computers - that's why DNS was made." Again mDNS will autoconfigure hostnames so you should only need to type foobar.local not 2001:db8:2d4f:1::1 in the guy's example.

Jump in the discussion.

No email address required.

I’m just saying

Jump in the discussion.

No email address required.

I mean in my job I’m fqdn and obviously know when there is a routing issue.

Jump in the discussion.

No email address required.

wdym

Jump in the discussion.

No email address required.

I love looking through logs, dealing with IPv6 nonsense. It's just insane babble on the screen.

Jump in the discussion.

No email address required.

I hate it... but as a massive conservatard and Cnile inthusiast he does have a point. Lots of things are claiming IPV4 addresses due to internet of shit.

IPv6 brings good things and concepts, but the growth expectation is insane. Expanding to a nearly infinite amount of people in the world does have its flaws too. Of course these differents are minimal, but the size change in IPv6 does affect performance (although it does fix some things too). Nobody can remember IPv6 addresses due to their sheer complexity.

Tell me this, look in the real world. addresses are addresses, but addresses can be memoized. We often call addresses things like "Moms home" or "The pizza shop", which is where maps come in (DNS), but some people like memorizing the addresses too and its important to do so ourselves. Yes, after a while I can memorize IPv4 addresses from habit if i own the server (i can memorize my old addresses but those change), although obviously i prefer my google maps (dns)

Imagine in the future we have to call addresses "472626E12 Johnson Avenue Complex 5th circle of heck" to account for too many places.

we really need an IPv5 or something. Simplicity should always champ.

NekoBIPOC out :marseyneko:

Jump in the discussion.

No email address required.

You had a chance to not be completely worthless, but it looks like you threw it away. At least you're consistent.

Jump in the discussion.

No email address required.

Reported by:

I don’t understand what your point was.

Jump in the discussion.

No email address required.

I remember places by their WGS-84 coordinates

Jump in the discussion.

No email address required.

Also I love Jew demons and love UN WATCH

Jump in the discussion.

No email address required.

ipv6 in itself is arguably simpler since it's the same thing without most uses of nat and without (necessarily) dhcp, also subnet size is never a worry. The issue is that implementing dual-stack requires doing the same thing twice for each aspect of the setup, or even doing two slightly different things, which is of course much more complicated than using either protocol alone.

Jump in the discussion.

No email address required.

I understand how complex NAT can get, but I just (to be clear, I’m not a network engineer though I know how to analyze a wireshark capture thanks to Laura Chappell) I am just not capable yet. I’m sure I’ll learn, but man it seems Byzantine.

Jump in the discussion.

No email address required.

It's really not too bad. I need to do the HE.net IPv6 course but I've picked up the basics around the 'net.

Jump in the discussion.

No email address required.

The trick I've been looking at is using prefixes. This way I can break down our ranges into what is essentially more /24's or /23's per remote location. It's not the best but it appears to be the only answer to making this stuff easier to remember.

I've been avoiding ipv6 since I worked at ISP's many years ago. I still don't understand why they didn't extend the octets on an ipv4 address and then just pad it with 0's to make everything work together. If my IP is 1.1.1.1 then my new IP in v6 would be 1.1.1.1.0.0.0.0 when I pad it to support more octets. Maybe they were worried about adjusting the cidr? This could of been done easier is all I can think when I look at ipv6 stuff.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.