News for hackers. Stuff that matters.
Re:AWS to Begin Charging for Public IPv4 Addresses by Aeolun on Thursday August 03, 2023 @06:28PM (#36992931)
Hmm, I use IPv4 mostly because nobody in their right mind can remember a IPv6 address…
Re:AWS to Begin Charging for Public IPv4 Addresses by post-it on Thursday August 03, 2023 @06:41PM (#36993065)
Who's out there remembering IPv4 addresses?
Re:AWS to Begin Charging for Public IPv4 Addresses by brickteacup on Thursday August 03, 2023 @06:55PM (#36993212)
If only there were some sort of a system for translating human readable names to network addresses...
Re:AWS to Begin Charging for Public IPv4 Addresses by waithuh on Thursday August 03, 2023 @07:31PM (#36993478)
damn, imagine if the buddies of the company that owns all of these IPs operated that system. The entire internet would be in their control. Wild dream.
Re:AWS to Begin Charging for Public IPv4 Addresses by gaudystead on Thursday August 03, 2023 @07:01PM (#36993267)
/me slowly raises hand
Re:AWS to Begin Charging for Public IPv4 Addresses by capableweb on Thursday August 03, 2023 @07:08PM (#36993323)
Plenty of people own ipv4 addresses (I mean, all of them are owned, but most by companies) and have been using the same addresses for a very long time, you start to remember some of them by heart after that :)
Re:AWS to Begin Charging for Public IPv4 Addresses by ricardo81 on Friday August 04, 2023 @02:28AM (#36996160)
Not I. Any commonly accessed IP tends to be named in my SSH config.
Re:AWS to Begin Charging for Public IPv4 Addresses by lucb1e on Thursday August 03, 2023 @08:01PM (#36993731)
Have you tried? I knew my v6 block (and static addresses within that, which is like two: router and server) back when I used v6 ten years ago, same as I know my v4 address, without really actively learning either

For sure this is a self-hoster thing, where you have pets not cattle, but so is memorizing your v4 address(es)

Re:AWS to Begin Charging for Public IPv4 Addresses by chungy on Thursday August 03, 2023 @08:48PM (#36994056)
I must be in my wrong mind then. :)

Just because it's a 128-bit number doesn't mean it should be difficult to remember, the standard notation goes a long way toward that. 2001:db8::cafe:f00d and fc00:bad:beef::1 aren't what I'd call the epitome of "can't remember"

Mind that real-world global addresses often have four groups of almost-random at the beginning, but it's usually not terrible to commit to memory.

Re:AWS to Begin Charging for Public IPv4 Addresses by tenebrisalietum on Thursday August 03, 2023 @10:46PM (#36994881)
Use DNS?
Re:AWS to Begin Charging for Public IPv4 Addresses by skrause on Friday August 04, 2023 @02:34AM (#36996204)
Is is really so hard to remember the addresses fd::1, fd::2 etc. for your local network?
Re:AWS to Begin Charging for Public IPv4 Addresses by ghosty141 on Friday August 04, 2023 @04:58AM (#36997316)
There is nothing wrong with ipv4 in the LAN, for public things in the internet DNS is and should be used anyways making ipv6 there a non issue.
Re:AWS to Begin Charging for Public IPv4 Addresses by sgjohnson on Friday August 04, 2023 @05:24AM (#36997488)
> There is nothing wrong with ipv4 in the LAN

Asides from potential address conflicts, should your work VPN space overlap with your LAN subnet, for example.

Re:AWS to Begin Charging for Public IPv4 Addresses by pantalaimon on Friday August 04, 2023 @07:05AM (#36998260)
2600:: is pretty handy