Slashdot Mirror

← Back to Stories (view on slashdot.org)

Free IPv4 Pool Now Down To Seven /8s

Posted by timothy on from the need-to-join-a-new-pool dept.

Zocalo writes "For those of you keeping score, ICANN just allocated another four /8 IPv4 blocks; 23/8 and 100/8 to ARIN, 5/8 and 37/8 to RIPE, leaving just seven /8s unassigned. In effect however, this means that there are now just two /8s available before the entire pool will be assigned due to an arrangement whereby the five Regional Internet Registries would each automatically receive one of the final five /8s once that threshold was met. The IPv4 Address Report counter at Potaroo.net is pending an update and still saying 96 days, but it's now starting to look doubtful that we're going to even make it to January."

1 of 460 comments (clear)

  1. Re:The most surprising turn of events by Obfuscant · · Score: -1, Redundant
    Lets say your ISP assigns you 10.0.32.128. Now, kindly tell me how you plan to connect to your home PC from work.

    Ok. Simple. Remember that for packets to get BACK to you from any server outside your own home network, you must have a routable address visible to the world. So, even though your home network is in the 10.0.0.0 net, your visible presence on the net is completely routable.

    Create a cron job that makes some loggable contact with your system at work from home, and you now have logged that visible, routable home address. Configure your home router to pass the port for whatever service you want to access from work to the system that can deal with it at home. Connect to that address using that port.

    I do this on a daily basis, from work to a home server behind Comcast.

    If this is insufficient for you, then configure an SSH tunnel from your home system to one at work, forwarding a port from the home system to the one at work. I do this daily, as well. I have a PeeCee with PuTTY forwarding the VNC port on that PeeCee out to a system at work. I run my local VNC server to connect to my local host on the local port, and I'm in control of that PC. I have two or three other systems around the world behind local firewalls/NAT boxes that also create SSH tunnels to a system at work. I SSH from my work system to localhost at the port I've designated for the tunnel to appear on, and bingo, I'm talking to the remote system.

    No, it's not an ideal way of doing things, but it's better than crying and complaining that I can't do what I need to do because those nasty people are running a firewall/NAT box.