IP Apocalypse - RIPE confirms available IPv4 addresses will run out in November

[Results45]

10 hours ago, rcmaehl said:

 

 

Great. Right in-time for my birthday (hint: it's a week before Christmas).

[williamcll]

Is it really so hard for ISPs to change to IPv6? Almost every device with an internet connection since windows XP has IPv6 support.

[LeSheen]

We managed to get one of the last /22 blocks

[RejZoR]

Here comes the nightmare of working with IPv6 coz the addresses are a god damn nightmare to remember.

[porina]

I can't buy help think of AMD's solution to this: 1.0.0.3ABBA

 

[minibois]

16 hours ago, rcmaehl said:

The UK, Europe

Oh no, not the UK AND Europe!

[jagdtigger]

8 minutes ago, RejZoR said:

the addresses are a god damn nightmare to remember.

10 hours ago, bcredeur97 said:

IPv6 is great, but I find the addresses are so much harder to remember because they aren't just numbers...

Are you living in the dark ages or just never heard of local dns? Since i have a pfsense router i basically never used ip address to reach something on my network...

 

/ON

Im one of the many unlucky ppl who's ISP uses CGN without IPv6. Its a good thing they give you public IP if you ask nicely but still.....

[leadeater]

15 hours ago, VegetableStu said:

wonder who would get 255.255.255.255

 

c:\>ping 255.255.255.255
Ping request could not find host 255.255.255.255. Please check the name and try again.

Nobody yet 

[leadeater]

6 minutes ago, minibois said:

Oh no, not the UK AND Europe!

The UK is in Europe

 

[leadeater]

19 minutes ago, jagdtigger said:

Are you living in the dark ages or just never heard of local dns? Since i have a pfsense router i basically never used ip address to reach something on my network...

I have to work with networking all the time, knowing IP addresses come up just as much and is more important than the DNS name. IPv6 address are just a right pain, we deal with that by prefix of our IPv6 network address then suffix is the IPv4 address so all our IPv6 addresses are identical to our IPv4 addresses just with an IPv6 prefix in front of it, mental life saver honestly.

[minibois]

17 minutes ago, leadeater said:

The UK is in Europe

Not anymore, when we push them towards America!

/s

 

 

[Video Beagle]

17 minutes ago, minibois said:

Not anymore, when we push them towards America!

 

no thanks..we already got one.

[jagdtigger]

58 minutes ago, leadeater said:

I have to work with networking all the time, knowing IP addresses come up just as much and is more important than the DNS name. IPv6 address are just a right pain, we deal with that by prefix of our IPv6 network address then suffix is the IPv4 address so all our IPv6 addresses are identical to our IPv4 addresses just with an IPv6 prefix in front of it, mental life saver honestly.

Bookmarks/spreadsheet...... The only address i know off the top of my head is the router.

[RejZoR]

1 hour ago, jagdtigger said:

Are you living in the dark ages or just never heard of local dns? Since i have a pfsense router i basically never used ip address to reach something on my network...

 

/ON

Im one of the many unlucky ppl who's ISP uses CGN without IPv6. Its a good thing they give you public IP if you ask nicely but still.....

Not when you're configuring local hardware in a fixed way.

[Doobeedoo]

It's over internet is limited muhaha. 

[leadeater]

25 minutes ago, jagdtigger said:

Bookmarks/spreadsheet...... The only address i know off the top of my head is the router.

It's more about reported issues, looking at the address, going to the security team, what was that address again? afe56::2f53s:blah blah? forgot now??? grrrr. There's things I can just do with IPv4 addresses that I cannot with IPv6 and it's all down to memorization.

 

Edit:

Like I legit know off memory probably 50+ servers IPv4 addresses, I know immediately looking at any IPv4 address what subnet and VLAN it belongs to and which building it is coming from or which security zone in the datacenter. IPv6 without the way we address them using the IPv4 address in it.... not a hope in hell of doing the same. 

[jagdtigger]

2 minutes ago, leadeater said:

It's more about reported issues, looking at the address, going to the security team, what was that address again? afe56::2f53s:blah blah? forgot now??? grrrr. There's things I can just do with IPv4 addresses that I cannot with IPv6 and it's all down to memorization.

Label the machine? We have two printers where i work. One main and one reserve. Main one is labeled as COK and reserve is COKR........  Stop looking for excuses why you cant use it. I also have IPv6 on my LAN. Infrastructure (routers, AP's, NAS's, etc) has fixed IP, everything else is dynamic. For the fixed stuff i have bookmarks and DNS entries for everything connected to the router. Thats about it

[leadeater]

8 minutes ago, jagdtigger said:

Label the machine? We have two printers where i work. One main and one reserve. Main one is labeled as COK and reserve is COKR........  Stop looking for excuses why you cant use it. I also have IPv6 on my LAN. Infrastructure (routers, AP's, NAS's, etc) has fixed IP, everything else is dynamic. For the fixed stuff i have bookmarks and DNS entries for everything connected to the router. Thats about it

It's not about labeling it's about being able to remember it while working on it, directly in the moment. What you're saying is equivalent to not being able to remember anyone's name while talking to them and hoping the name tag is on their shirt, yes I can look up the name but that is not work efficient.

 

It's a real issue, human brain limitation just because of the complexity of the address style, I'm not saying it's a reason to not use IPv6 but this actually is an issue and if you'd worked any time in supporting networks you'd likely be able to better understand what I'm pointing to.

 

Edit:

And to be clear we have a central asset database and web interface, every device has an asset tag, every device has a friendly DNS name. It's not a labeling issue, it's not an IP address management issue, it's not a DNS issue, it's a memorization issue.

[jagdtigger]

11 minutes ago, leadeater said:

yes I can look up the name but that is not work efficient.

Just as memorizing every single device's IP address. Its like when at my workplace we had to memorize a whole ton of code number so we would know what goes into the car. Guess what? We found a another way without the codes.......  Why memorize anything that can be looked up in a matter of seconds? Its both dumb and pointless.

[leadeater]

10 minutes ago, jagdtigger said:

Just as memorizing every single device's IP address. Its like when at my workplace we had to memorize a whole ton of code number so we would know what goes into the car. Guess what? We found a another way without the codes.......  Why memorize anything that can be looked up in a matter of seconds? Its both dumb and pointless.

I'm not saying memorize every single device address (legit impossible here as alone we have 10000 PC, thousands of APs, thousands of switches, thousands of servers etc etc), put it this way imagine trying to get your job done if you forget the name of everything and every person after a few seconds. That label on the printer, yea you just forgot that immediately after reading it. Good luck getting your job done efficiently now compared to being able to remember it. But don't worry all the information is in the job ticket, just open the browser go to the site, find the ticket get the details, lookup the address again, ha you can't because you're not at your desk because you're following up the issue with another team so now they have to go through the same process you just did because you couldn't remember the IP address.

 

I'm talking about the specific ability to remember the IP address you got from DNS, if you cannot repeat it even after just reading it that is a problem and is actually rather frustrating and not an issue with IPv4 addresses.

[vanished]

For people worried about this making networking a nightmare, perhaps someone with more network experience can explain if this idea would avoid that or not: just have every public access point get an IPv6 address but within the company/organization, use IPv4.  I know part of the point of IPv6 is to have so many addresses that they can afford to give every device in the world a unique public address, but that actually gets at why I don't like it - half the point of a router is the fact that from outside, you can only target it and nothing behind it, but things behind it can reach out.  If every device had a public address it defeats that security.

[jasonvp]

8 minutes ago, Ryan_Vickers said:

For people worried about this making networking a nightmare, perhaps someone with more network experience can explain if this idea would avoid that or not: just have every public access point get an IPv6 address but within the company/organization, use IPv4.  I know part of the point of IPv6 is to have so many addresses that they can afford to give every device in the world a unique public address, but that actually gets at why I don't like it - half the point of a router is the fact that from outside, you can only target it and nothing behind it, but things behind it can reach out.  If every device had a public address it defeats that security.

"Half the point of a router..." is an incorrect statement.  Half the point of a NAT may be that you can only target it.  That is unless it has a static reverse NAT set up on it.  All L3 NAT devices are routers by nature; all routers are not NAT devices.

 

With that said: yes, you can 4-to-6 NAT if you want.  This is only applicable for people at home though.  Really, any company with a large global presence and lots of public-facing servers will want to avoid doing any sort of NAT for their high bandwidth services.  NATs suck, through and through.  They're a bitch to troubleshoot, and they're potentially a bandwidth bottleneck.

 

Ultimately, folks are going to have to get over the whole, "I can't memorize IPv6 as easy" excuse.  I get it, they're a PITA to work with from a usability perspective.  Specially for those of us working on networking infrastructure.  But the sooner you dive in and immerse yourself, the sooner you'll get over it.

 

And you WILL have to get over it.  Eventually.

[TetraSky]

Meanwhile, my ISP has been handing out static IPs to all their customers for a few years now, so they can stay in IPv4 longer while delaying the rollout of IPv6.

I swear their "beta" for IPv6 has been ongoing since 2011, all while needing their fancy new modem/router, they won't let you sign up to the "beta" without it.

[vanished]

2 minutes ago, jasonvp said:

"Half the point of a router..." is an incorrect statement.  Half the point of a NAT may be that you can only target it.  That is unless it has a static reverse NAT set up on it.  All L3 NAT devices are routers by nature; all routers are not NAT devices.

Well, ok I know it's also a switch, a wireless AP, a firewall, etc. and ours does also do NAT, and strictly speaking NAT isn't a firewall, but I consider it part of it and definitely value that functionality.  "Half" may have just been a figure of speech

2 minutes ago, jasonvp said:

With that said: yes, you can 4-to-6 NAT if you want.  This is only applicable for people at home though.  Really, any company with a large global presence and lots of public-facing servers will want to avoid doing any sort of NAT for their high bandwidth services.  NATs suck, through and through.  They're a bitch to troubleshoot, and they're potentially a bandwidth bottleneck.

Ah ok, good to know

2 minutes ago, jasonvp said:

Ultimately, folks are going to have to get over the whole, "I can't memorize IPv6 as easy" excuse.  I get it, they're a PITA to work with from a usability perspective.  Specially for those of us working on networking infrastructure.  But the sooner you dive in and immerse yourself, the sooner you'll get over it.

 

And you WILL have to get over it.  Eventually.

I'd imagine people will have to just write things down now rather than trying to memorize them.

[leadeater]

22 minutes ago, jasonvp said:

But the sooner you dive in and immerse yourself, the sooner you'll get over it.

Dunno about that, we've been using IPv6 for over 5 years and they still bug me lol. But that has more to do with actual issues with IPv6 like sites not working over IPv6 but work fine over IPv4 that were just working the day before, then having to figure out who's issue it is, us or them. Then there is even dumber issues like the security team forgetting to put firewall rules in for the IPv6 address of the server, I know shouldn't be a thing but yea... happens enough to be annoying.