Short sightedness has caused the depletion problem (if you can call 160 million possibilities short sightedness)...but the issue is kind of moot right now.
IPv6 is coming...and we won't run out of addresses. We need creative ways to deal with problems that we have right now as we wait for IPv6.
The issue of NATed addresses is a real one and a barrier for peer-2-peer communications, not the hype, but true application-to- application communications that can allow networks to understand their state and topology to make intelligent routing and communications decisions. In order for this to occur the Internet needs to go back to its roots of true bi-directional communications. Publishers cannot simply view nodes as passive receivers of content...but as active participants on the network at large with important things to say and receive. The current trend for ISPs to provide asynchronous bandwidth is our next barrier and a trend that hopefully is reversed as more devices and home users demand to be publishers of content and information.
With a combination of dyndns, granitecanyon and ip[commands] under linux you can set up a "NATed" infrastructure and port forward to different servers behind your linux firewall without needing to host any of your own DNS or any static IPs.
This works when your firewall recieves its IP dynamically using DHCP from a cable modem or such.
For instance:
- register a domain: such as mydomain.com
- go get a dynamic domain from dyndns (make a donation cheepo!): mydomain.dyndns.org
- create a C record on granitecanyon.com that points mydomain.com to mydomain.dyndns.org
configure your firewall box to dynamically register its new IP each boot with dyndns...
Done...now setup an http server behind the firewall running on some port 8080, for instance.
Setup ipchains and ipfw to forwad all request to the firewall on port 80 to the machine behind at 8080...you could do this for as many ports as you like.
Slashdot Mirror
Short sightedness has caused the depletion problem (if you can call 160 million possibilities short sightedness)...but the issue is kind of moot right now.
IPv6 is coming...and we won't run out of addresses. We need creative ways to deal with problems that we have right now as we wait for IPv6.
The issue of NATed addresses is a real one and a barrier for peer-2-peer communications, not the hype, but true application-to- application communications that can allow networks to understand their state and topology to make intelligent routing and communications decisions. In order for this to occur the Internet needs to go back to its roots of true bi-directional communications. Publishers cannot simply view nodes as passive receivers of content...but as active participants on the network at large with important things to say and receive. The current trend for ISPs to provide asynchronous bandwidth is our next barrier and a trend that hopefully is reversed as more devices and home users demand to be publishers of content and information.
With a combination of dyndns, granitecanyon and ip[commands] under linux you can set up a "NATed" infrastructure and port forward to different servers behind your linux firewall without needing to host any of your own DNS or any static IPs.
This works when your firewall recieves its IP dynamically using DHCP from a cable modem or such.
For instance:
- register a domain: such as mydomain.com
- go get a dynamic domain from dyndns (make a donation cheepo!): mydomain.dyndns.org
- create a C record on granitecanyon.com that points mydomain.com to mydomain.dyndns.org
configure your firewall box to dynamically register its new IP each boot with dyndns...
Done...now setup an http server behind the firewall running on some port 8080, for instance.
Setup ipchains and ipfw to forwad all request to the firewall on port 80 to the machine behind at 8080...you could do this for as many ports as you like.