Agree with all except "all this tunneling really is an unstable mess".
I'd like to see some data for that. I'll bet there is none.
The tunnels on all 7 of the machines I manage have been stable for years. As far as I know, the eight or nine other machines I link to have been stable for years as well.
Michael
-----Original Message----- From: 44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Steve Wright Sent: Thursday, March 20, 2014 4:45 PM To: 44net@hamradio.ucsd.edu Subject: Re: [44net] 44net problems - was: 44net cool toys
(Please trim inclusions from previous messages) _______________________________________________ Ok here's my opinion.
Technically, it's difficult for prospective members to connect a 44 subnet of any type, using any method. It is not clear at all how this is ACTUALLY done or what options are available.
The wiki should be the authoritative document, but ;
1.) The main page is all about how to edit the wiki and a logo competition, and ONE LINE on how to set up a gateway - which the whole reason people went to the wiki.
2.) The "Setting_up_a_gateway_on_Linux" wiki page has a broken link leading to "common instructions for setting up a gateway", inviting newcomers to consider that there ARE NO such instructions, at which point they'll probably completely give up.
3.) The three main options, munge script, rip44d.pl and rip44.c are not stated clearly, nor are there links to any such subsection, nor are these options grouped from the users' perspective - namely their chosen platform, be it JNOS, x86 Linux, OpenWRT, or METARouter.
4.) There's no real index to what people are actually DOING over the 44net, and people ARE DOING some cool stuff. If there were some page in the wiki where people shared what they were making, then others might duplicate their efforts.
Sysadmins on the portal are reluctant to issue /24s, when there's lots and lots available.
The portals' "Law and Jurisdiction" section in the terms and conditions insults the user. Most of the rest of that section is pretty unsavoury too.
WISPs and others who want to peer don't have access to any toolkit or support.
Some stuff in the portal doesn't (or didn't) work, and it's not clear which.
There's not really an apparent reason WHY newcomers might even WANT to number a network with 44. It's simpler to just throw a DHCP server at an interface and add some routing - easy peasy, why number the network with 44, and if they did - HOW to do that?
It's not really clear to network builders, that they can actually number up with 44 right now, and worry about connecting to other 44/xx Networks later when they're ready. If they want to expose several 44/24's to the wild internet, then that doesn't really affect anyone else but themselves.
All this tunnelling really is an unstable mess. Apart from allowing the wild internet to connect inbound, why not just route the whole thing?
HTH, Steve