Mordecai Walfish wrote on Apr 21, 2018, 13:47:Today meet "someday".Mr. Tact wrote on Apr 21, 2018, 13:37:RedEye9 wrote on Apr 21, 2018, 11:48:Someday, sure -- but not any time soon. Basically it is NOP. (not our problem)
As more people go online and more iots devices get into consumer hands the "lack of IPv4 addresses" will definitely be a thing. If is inevitable.
It became *my* problem when I randomly discovered a bunch of shit was acting haywire/not working, and spent hours troubleshooting until I found out I was quietly switched over to that Carrier Grade NAT bs, which only exists because of the "lack of IPv4 addresses" issue, whether imaginary or not.
Mr. Tact wrote on Apr 21, 2018, 13:37:RedEye9 wrote on Apr 21, 2018, 11:48:Someday, sure -- but not any time soon. Basically it is NOP. (not our problem)
As more people go online and more iots devices get into consumer hands the "lack of IPv4 addresses" will definitely be a thing. If is inevitable.
RedEye9 wrote on Apr 21, 2018, 11:48:Someday, sure -- but not any time soon. Basically it is NOP. (not our problem)
As more people go online and more iots devices get into consumer hands the "lack of IPv4 addresses" will definitely be a thing. If is inevitable.
Mordecai Walfish wrote on Apr 21, 2018, 11:24:As more people go online and more iots devices get into consumer hands the "lack of IPv4 addresses" will definitely be a thing. If is inevitable.Mr. Tact wrote on Apr 20, 2018, 21:40:
Oh, additionally FWIW (possibly not much) -- I have an acquaintance who owns/runs a medium to large privately owned ISP in the Chicago area. And his personal spin on this topic is the "lack of IPv4 addresses" is unlikely to ever be an issue. There are so many chunks that people are squatting on, and so many devices being assigned real IPv4 that don't need them.
There are a number of hacks in the works at isps to alleviate this issue somewhat, like "Carrier Grade NAT", which my ISP recently started using.
This is a direct negative consequence of not switching to ipv6 sooner, as carrier grade NAT is prohibitive in a number of different ways. The way carrier grade NAT works, it could switch your IP address multiple times a day, and break simple things like port forwarding. This conflicts with running a home/remote server as well.
I had to call and discuss issues I was having with my internet with my ISP to find out they had switched to this recently, and it was the source of the issues I was having. They switched me back to standard upon request, but they ask for a reason when you do this. I simply told them I stream media from my home computer to my portable tablets/devices and needed proper NAT for this to work properly. No problems since.
I looked in to it, and many carriers across the country are switching over to patchwork solutions like this, and this is indeed a cause for concern with the limited abilities of solutions like "Carrier Grade NAT".
Mr. Tact wrote on Apr 20, 2018, 21:40:
Oh, additionally FWIW (possibly not much) -- I have an acquaintance who owns/runs a medium to large privately owned ISP in the Chicago area. And his personal spin on this topic is the "lack of IPv4 addresses" is unlikely to ever be an issue. There are so many chunks that people are squatting on, and so many devices being assigned real IPv4 that don't need them.
Creston wrote on Apr 20, 2018, 18:32:
The thing about the IPv4 address block problem is that people don't see what the problem is. Oh, there are no more new addresses? Okay. So there won't be any more NEW websites? Huh.
*goes to Facebook*
I mean, it'd be one thing if we said "IPv4 is going to crash in three months and nothing will work on the Internet." That'd get people moving.
But no new websites, and other assorted shit? But we do get to keep our current allotment of devices and websites? Okay, whatever.
In the end, the ISPs are to blame for this. They need to just fucking FORCE this shit.
ViRGE wrote on Apr 20, 2018, 15:06:eRe4s3r wrote on Apr 20, 2018, 11:18:You can switch now or you can switch later. But if you switch later it's going to hurt all the more.
"Now for the last time, will you all please shift to IPv6?!"
The answer is no, and sod off
ViRGE wrote on Apr 20, 2018, 15:06:Okay, I'll bite. Why will it hurt more if I wait? I actually don't really care at this point. My router is IPv6 capable but I have no pressing reason to switch. And frankly, I'd be shocked if Comcast supported it.
You can switch now or you can switch later. But if you switch later it's going to hurt all the more.
eRe4s3r wrote on Apr 20, 2018, 11:18:You can switch now or you can switch later. But if you switch later it's going to hurt all the more.
"Now for the last time, will you all please shift to IPv6?!"
The answer is no, and sod off