20 Mar
2014
20 Mar
'14
6:45 p.m.
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
--
Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
+64 21 040 5067
20 Mar
20 Mar
7:45 p.m.
New subject: 44net problems - was: 44net cool toys
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(a)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(a)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
--
Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
+64 21 040 5067
8:03 p.m.
New subject: 44net problems - was: 44net cool toys
Thanks Steve I couldn't have put it better myself..
Thanks also to the others on this list that refrained from flaming and
to those who were and are sympathetic.
Brian suggested that my application for an allocation might have been
lost in the portal changes and this may be true but Samantha was also
helpful however she was in the throes of a move of QTH and things do
tend to get a bit deferred at such times
I will re-apply through the portal in a day or two but it still leaves
me more than a trifle confused as to how I am going to connect.
Should I apply for a tunnel or a gateway? What size allocation is
recommended for someone like myself with lots of on air services. Can I
set up a raspberry pi to look after all of the internet side of
things, particularly the security problems I see mentioned so frequently
on here and if so is there any advice or guidance on how to do so or a
preferred distro (wheezian)?..
And of course from my point of view can I retain my Fritzbox
modem/router and connect successfully though that to both my standard
125 I.P. and the 44 I.P. at the same time
The price of power in VK3 is through the roof and looks like continuing
to climb so as many of my 24/7 ham services that can be raspberryfied
the better.
I have no problem in allowing other hams onto the network through my
system and in fact many do so through the other services that I offer
from here.
I look froward to any advice that can be offered on where I should start
to become 44 literate.
73's Tony VK3API
Grumpy old man par excellence
On 21/03/2014 10:45 AM, Steve Wright wrote:
(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.
8:56 p.m.
New subject: 44net problems - was: 44net cool toys
I've been little more than an observer for some time, but I must say ALL
the points in this e-mail are right on. I began thinking about 44 almost
5 years ago, and to reiterate a few points made:
1. Coordination at first seemed almost impossible. I was told by a few
other hams, "Good luck getting an address. 44-net is dead". I sent a
number of emails over a span of 2 years before I got the attention of who I
believe is the most recent coordinator for my area. I was greeted with a
"You DO know that a /24 is 253 routable IPs?" After 3+ years of trying to
get anything, I asked for a sizeable segment that I could break up and
route as needed. I didn't want to wait 3 years for every /29 I needed for
a new project. I'm sure the portal has made things easier, but with all
the space available, why the grief over a /24? I didn't ask for a
networking lecture, I know what a /24 is..
2. Some of my experience with even getting addresses coordinated, along
with what Steve pointed out in the Terms and Conditions, as well as the
overall complexity, I haven't found 44 to be very welcoming. If a club
posts their repeater rules, and they consist of "Feel free to use the
repeater. The tone is unpublished... you'll need to figure it out, here's
a list of 20 things NOT to do, oh, and we're watching you!", I am probably
not going to use the repeater.
I have a strong networking background, and I am far from being an appliance
operator, but it's hard to make a pizza if you've never seen one, the
recipes are so vastly different that the concepts aren't clear, and it
almost appears intentional.
Danny
On Thu, Mar 20, 2014 at 7:45 PM, Steve Wright <stevewrightnz(a)gmail.com>wrote;wrote:
> (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
>
>
> --
> Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
> +64 21 040 5067
>
21 Mar
21 Mar
7:38 a.m.
New subject: 44net problems - was: 44net cool toys
I tend to agree with Danny here. I have a networking background in the wireless LAN world
and was thrilled to find out that there was some public IP's set aside for hams as we
all are wireless geeks one way or another. I thought it would be great to experiment
around wireless mesh since we have RouterOS, HamWan, OpenWRT, and such. Before last
night, I didn't even realize that someone was hosting a VPN server to traverse the
commodity internet so that I could portal to the 44 space. I just wish that there was
more documentation to newcomers like me, so that other gen-x'ers might want to play
around too.
So I agree, but let's remember that the network is for experimenting. If everyone
knew everything about networking, then no one would even want to mess with the 44. Maybe
someday it could be updated to include routing protocols like BGP and OSPF, like normal
networks use. RIPv2 is pretty old, and very limited. No one wants to play with that.
But, I can see why we have to use it as the 44's link to the internet is probably 1
Gig or less.
So, besides my early morning rambling, here are some questions from a newcomer's
perspective:
1. How do I use the 44 net?
2. What equipment do I need to get started?
3. How do I route my IP range from my house to California without asking Comcast to
advertise my IP's?
4. Besides Linux programs, what types of programs are out there for normal hams to use on
PC's?
5. Why is there generally only an EMCOMM use case for the 44 net?
I'd like to experiment with the 44 net and I probably will. Maybe we should all come
together and make suggestions on ways to modernize the 44 net.
Matthew L. Bonadies
Campus Network Operations
Wireless Networks
Indiana University - Bloomington
mbonadie(a)iu.edu
(812) 855-2422
-----Original Message-----
From: 44net-bounces+mbonadie=iu.edu(a)hamradio.ucsd.edu
[mailto:44net-bounces+mbonadie=iu.edu@hamradio.ucsd.edu] On Behalf Of Danny Messano
Sent: Thursday, March 20, 2014 9:56 PM
To: AMPRNet working group
Subject: Re: [44net] 44net problems - was: 44net cool toys
(Please trim inclusions from previous messages)
_______________________________________________
I've been little more than an observer for some time, but I must say ALL
the points in this e-mail are right on. I began thinking about 44 almost
5 years ago, and to reiterate a few points made:
1. Coordination at first seemed almost impossible. I was told by a few other hams,
"Good luck getting an address. 44-net is dead". I sent a number of emails over
a span of 2 years before I got the attention of who I believe is the most recent
coordinator for my area. I was greeted with a "You DO know that a /24 is 253
routable IPs?" After 3+ years of trying to get anything, I asked for a sizeable
segment that I could break up and route as needed. I didn't want to wait 3 years for
every /29 I needed for a new project. I'm sure the portal has made things easier, but
with all the space available, why the grief over a /24? I didn't ask for a networking
lecture, I know what a /24 is..
2. Some of my experience with even getting addresses coordinated, along with what Steve
pointed out in the Terms and Conditions, as well as the overall complexity, I haven't
found 44 to be very welcoming. If a club posts their repeater rules, and they consist of
"Feel free to use the repeater. The tone is unpublished... you'll need to figure
it out, here's a list of 20 things NOT to do, oh, and we're watching you!", I
am probably not going to use the repeater.
I have a strong networking background, and I am far from being an appliance operator, but
it's hard to make a pizza if you've never seen one, the recipes are so vastly
different that the concepts aren't clear, and it almost appears intentional.
Danny
On Thu, Mar 20, 2014 at 7:45 PM, Steve Wright <stevewrightnz(a)gmail.com>wrote;wrote:
(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
--
Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
+64 21 040 5067
-------------- next part -------------- An HTML attachment was
scrubbed...
URL: <
http://hamradio.ucsd.edu/mailman/private/44net/attachments/20140321/65
5b8111/attachment.html
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
--
"From the moment I picked your book up until I laid it down I was convulsed with
laughter. Some day I intend reading it."
- Groucho Marx (1895-1977)
22 Mar
22 Mar
10:14 a.m.
New subject: 44net problems - was: 44net cool toys
On Thu, 20 Mar 2014 21:56:28 -0400, Danny Messano
<drmessano(a)gmail.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
I've been little more than an observer for some time, but I must say ALL
the points in this e-mail are right on. I began thinking about 44 almost
5 years ago, and to reiterate a few points made:
1. Coordination at first seemed almost impossible. I was told by a few
other hams, "Good luck getting an address. 44-net is dead". I sent a
number of emails over a span of 2 years before I got the attention of who I
believe is the most recent coordinator for my area. I was greeted with a
"You DO know that a /24 is 253 routable IPs?" After 3+ years of trying to
get anything, I asked for a sizeable segment that I could break up and
route as needed. I didn't want to wait 3 years for every /29 I needed for
a new project. I'm sure the portal has made things easier, but with all
the space available, why the grief over a /24? I didn't ask for a
networking lecture, I know what a /24 is..
As a coordinator I've never hesitated when assigning a block of any
size, including /24's to any ham who asked for one. Perhaps I am
exceptional but I didn't see a reason to be stingy with addresses. In
the beginning I used to assign individual addresses in 44.18.0.x in
continuation of my predecessor's policy, since everyone was on 1200
baud on 2 meters and routing was manual but when it came time to
assign for entities I assigned whole subnets and eventually designed a
frequency/geography scheme for assigning subnets and if someone wanted
a single IP, they got one from within that subnet. My biggest problem
now is determining whether an address is even being used anymore and
whether or not I need to care.
Brian originally reserved the middle two bits of the dotted quad to
future expansion, resulting in a somewhat conservative approach in the
minds of the sub-coordinators toward their net blocks. I believe that
reservation no longer exists.
2. Some of my experience with even getting addresses coordinated, along
with what Steve pointed out in the Terms and Conditions, as well as the
overall complexity, I haven't found 44 to be very welcoming. If a club
posts their repeater rules, and they consist of "Feel free to use the
repeater. The tone is unpublished... you'll need to figure it out, here's
a list of 20 things NOT to do, oh, and we're watching you!", I am probably
not going to use the repeater.
This is unfortunate. I've never considered it my job to be a
conservator of a scarce resource or to "regulate" what hams were doing
with their address blocks. IP addresses are not repeaters and as a
former repeater owner I don't have time to be a nanny and never did
like being a nanny. But then again, I've heard some pretty foolish
things done on repeaters that the "offending" ham should have known
was against the regs and unlike IP address coordinators, the guy who's
callsign is on the repeater can be held responsible for what people do
with it. I also don't feel I need to teach TCP/IP protocol to someone
just because he's new. I used to have a list of resources I'd pass out
or just point them at the UCSD FTP site for all the code and docs.
YOU have to understand that if the environment seems to be unwelcoming
it might just be because experimenters are experimenters and not
necessarily good teachers, coders can be good coders and more often
than not, they are lousy documentation writers. I've found some
brilliant individuals who are doing some interesting things in their
net blocks but they don't publish articles or how-to's, leading to a
lot of hidden effort.
I challenge you to take a leadership role and publish your work and
create some documentation and develop scripts and methods that people
can use as templates so we can start making some forward progress
instead of reinventing the wheel.
I have a strong networking background, and I am far from being an appliance
operator, but it's hard to make a pizza if you've never seen one, the
recipes are so vastly different that the concepts aren't clear, and it
almost appears intentional.
Danny
What have you done to publish your recipes? How many new hams have you
brought online in your community?
On Thu, Mar 20, 2014 at 7:45 PM, Steve Wright <stevewrightnz(a)gmail.com>wrote;wrote:
> (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
>
Steve,
Wiki's are a collective effort, what have you done to fix the flaws
you see there? Have you signed on as a Wiki editor? Have you written
articles for inclusion on that Wiki? Links go stale, there has to be
an "ugly bag of mostly water" behind the keyboard to keep a document
tree fresh and healthy, otherwise off-site links go bad when someone
drops dead or an organization folds. What are you doing in YOUR spare
time.
I see a whole lot of room for improvement and a whole lot of
networking experts who can "advance the state of the art" but who
don't seem to be inclined to actually publish what they know.
What I see above from both of you is "this is a mess, someone needs to
clean it up, but that someone isn't going to be me". I must boldly
state that if you have the time to discern a problem and criticize a
state of affairs, you have the time to take ownership of that problem
and fix it.
--
Geoff Joy - ke6qh -
AmprNet IP Address Coordinator for San Bernardino & Riverside Counties.
geoff(a)windomeister.com
20 Mar
20 Mar
9 p.m.
New subject: 44net problems - was: 44net cool toys
Steve,
Feel free to write up better instructions. I'm sure that Brain and
Chris would be thrilled to have someone like you volunteer to do
this.....
-Neil
On Thu, Mar 20, 2014 at 6:45 PM, Steve Wright <stevewrightnz(a)gmail.com> wrote:
> (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
>
>
> --
> Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
> +64 21 040 5067
>
21 Mar
21 Mar
4:08 a.m.
New subject: 44net problems - was: 44net cool toys
On 21 Mar 2014, at 02:00, Neil Johnson <neil.johnson(a)erudicon.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Steve,
Feel free to write up better instructions. I'm sure that Brain and
Chris would be thrilled to have someone like you volunteer to do
this…..
I couldn’t have put it better myself Neil. It’s very easy to sit out there and complain,
it’s more hassle to actually do something about it.
The wiki is supposed to be a collaborative effort, the whole point of a wiki is that it is
populated and updated by everyone, not just by one or two. So if you are disappointed with
the content, please feel free to do something about it. Wiki’s only work if enough people
interested in the subject matter get stuck in, if everyone on this list did half a page
we’d have weeks of reading material available.
With regards to the portal, I appreciate there have been issues, mainly because it’s just
me doing the coding and so I did it “my way”, which not everyone agreed with. Again, it
shouldn’t be down to just one individual, I could really do with some help with the PHP
coding if anyone has the skills and time? I’ve been working on putting it all on a
subversion repository to make it easier to collaborate. A couple of people did offer to
help, but when it came down to it they went very quiet. The only person who offered to
help and actually did was Maiko who kindly wrote the code for the gateway email robot.
So please, if anyone has reasonable PHP skills and some spare time, I’d love some help!
I also setup the portal to be multi-lingual and some time ago asked for volunteers to
maintain languages other than English, guess what? it’s still only got English! So again,
if anyone would like to translate the portal to another language and can spare the time to
maintain it as it develops, please make yourself known! (you only need very minimal
knowledge of PHP to do this).
Thanks,
Chris
22 Mar
22 Mar
10:31 a.m.
New subject: 44net problems - was: 44net cool toys
On Fri, 21 Mar 2014 12:45:00 +1300, Steve Wright
<stevewrightnz(a)gmail.com> wrote:
Sysadmins on the portal are reluctant to issue /24s,
when there's lots and
lots available.
There are precisely 256 /24's in each coordinator's block, -2 for
broadcasts and (initially) only 64 of them were assignable by the
coordinators directly. How many hams are in your area? Do they all
actually need a /24? When distributed across a populated region, whole
/24's can become a commodity. Each /24 assignee effectively becomes a
sub-coordinator.
I regard the granularity of the automatic routing protocols to be a
defect when it comes to masking for blocks smaller than /24.
--
Geoff Joy - ke6qh -
AmprNet IP Address Coordinator for San Bernardino & Riverside Counties.
geoff(a)windomeister.com
3900
days inactive
3902
days old
8 comments
8 participants
participants (8)
-
amprnet＠wizards.sytes.net -
Bonadies, Matt -
Chris -
Danny Messano -
Geoff Joy -
Michael E Fox - N6MEF -
Neil Johnson -
Steve Wright