Hello Simon,   
      
   On Wednesday November 03 2010 22:31, you wrote to Marc Lewis:   
      
    SP> Hope you and others don't mind me butting in here.  I would not claim   
    SP> to be particularly knowledgeable about IREX, but as I work in the   
    SP> networking area I would make a few comments about the IPv4   
    SP> 'exhaustion' situation. There are three things that stand in the way   
    SP> of actual exhaustion of IPv4 space.   
      
   Instead of giving you an in-dept reply, I will just direct you to some experts   
   on the matter og IPv4 exhaustion.   
      
    SP> 1/ RFC1918 address ranges (10.0.0.0 - 10.255.255.255, etc.)   
    SP> 2/ Network Address Translation (NAT)   
      
      
   NAT won't save you from the need to switch to IPv6:   
   http://tinyurl.com/26klu33   
      
    SP> There are also lots of IP's that are nominally allocated, but   
    SP> although once used, are in fact unused, and could be reclaimed if   
    SP> necessary.  This has already happened in the case of a few A-class   
    SP> ranges, including some used for Australian cable internet providers.   
      
   Reclaiming unused addresses will be a time consuming process with lots of   
   legal proceduers giving us only a few month extra:   
      
   http://www.potaroo.net/ispcol/2010-09/exhaustguide.html   
      
    SP> And finally, even if all of these factors were somehow overcome and   
    SP> address space were exhausted anyway and people began to take up IPv6,   
    SP> eventually to the exclusion of v4, IPv6 can be made to run an IPv4   
    SP> tunnel, so the solution to run IREX and the like is just to build a v4   
    SP> over v6 tunnel and use that.   
      
   To run an OPv4 only server, you will need a public IPv4 address, An RFC1918   
   address won't do as that is not globally routable.   
      
    SP> Now that I have weighed into this debate, would there be any pointers   
    SP> that I could follow on fixing my internal error 11 with IREX? :)   
      
   The Linux version has a problem woth the DNS resolver. The the only way is to   
   enter the raw IP address of the destination instead of the symbolic host   
   name...   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MINGW 1.1.5-b20070503   
    * Origin: http://www.vlist.org (2:280/5555)