Re: [44net] tunneling

I can't stand to keep quiet any longer!!!! Why not forget the tunnels? Or at least do something in addition? My ISP (who is also a long time Ham, and is also me) has requested several times a block of addresses to provide to Hams who are on his Internet service, which is a wireless based ISP covering 13 cities including the Atlanta area and fed by 2 Tier 1 providers via fiber. If we do not use the resource, then we face losing it. We are tying up what- a million addresses? IP addresses are in short supply. How many do we use? 1,000 even if that many? What happens if Brian loses his job at UCSD? If everything goes through there, the whole thing is hosed. Ralph N4NEQ -----Original Message----- From: 44net-bounces+ralphlists=bsrg.org(a)hamradio.ucsd.edu [mailto:44net-bounces+ralphlists=bsrg.org@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: Sunday, June 03, 2012 10:36 AM To: AMPRNet working group Subject: Re: [44net] tunneling (Please trim inclusions from previous messages) _______________________________________________ On Sun, Jun 03, 2012 at 09:46:11AM +0100, Max Lock wrote: No, it's not a policy, just a practical matter as the tunnel ("encap") table is only updated at most once a day and many of the stations which incorporate it manually do so less often than that. There is interest in accomodating 'dyndns' and similar measures in a future implementation. - Brian _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2178 / Virus Database: 2425/5042 - Release Date: 06/03/12