Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    IREX    |    Internet Rex (FTN <=> Internet) Public S    |    1,458 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 105 of 1,458    |
|    Simon Phillips to Marc Lewis    |
|    re [2]: W7 + REX v2.29    |
|    03 Nov 10 22:31:34    |
      Hello Marc and others,              Hope you and others don't mind me butting in here. I would not claim       to be particularly knowledgeable about IREX, but as I work in the       networking area I would make a few comments about the IPv4       'exhaustion' situation. There are three things that stand in the way       of actual exhaustion of IPv4 space.              1/ RFC1918 address ranges (10.0.0.0 - 10.255.255.255, etc.)       2/ Network Address Translation (NAT)       3/ Difference between 'allocated' and 'really not available anymore'              Most businesses don't use real IP's internally anymore, only RFC1918       ranges, and those who don't, could for the most part use RFC1918       addresses if they wanted to, or make their allocation irrelevant by       using NAT. A new corporate customer will typically ask for only a       small block of IP addresses, not the thousands that were requested in       days gone by.              There are also lots of IP's that are nominally allocated, but       although once used, are in fact unused, and could be reclaimed if       necessary. This has already happened in the case of a few A-class       ranges, including some used for Australian cable internet providers.       I personally know of a good half dozen class B's that could be       reclaimed given the will and effort, and there are probably more out       there, allocated but not routed on the Internet, or routed but of       which only a few are actually in use, and the rest are behind a NATing       firewall. The ones I am referring to are mostly allocated to       Australian public universities and the like - orgs that got in early       on the Internet and were allocated lots of addresses they don't really       need.              Theoretically, Australian ISP's ran out of IPv4 address space in the       late 90's when APNIC exhausted its allocation. So in the terms of 5%       of addresses being still available, Australia has 0%, but somehow, new       addresses are still available from my ISP if I ask for one :)              And finally, even if all of these factors were somehow overcome and       address space were exhausted anyway and people began to take up IPv6,       eventually to the exclusion of v4, IPv6 can be made to run an IPv4       tunnel, so the solution to run IREX and the like is just to build a v4       over v6 tunnel and use that.              Much the same principle as allows me to run DOS software under Linux       :)              Now that I have weighed into this debate, would there be any pointers       that I could follow on fixing my internal error 11 with IREX? :) I       don't really want to dig through hundreds of pages of truss output,       which would seem to be my only other option, besides random trial and       error.                     Regards,              Simon.              --- Ezycom V2.15g2 01FA0281        * Origin: ZZap BBS, Melbourne Vic AU - telnet://bbs.zzap.org (3:690/682.303)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca