I guess my point is - there are those who sit around and cry and beat their
forehead with their fist over authentication, the rules, third party
traffic etc etc, and there are those who just go ahead, build it, and use
it.
The difficulty for me is, I returned to 44net hoping for the latter, or at
the very least some tutorials on the wiki where it might be done, meet some
people that are doing it, but the reality is more that the 44net list is
dominated by crybabies who would far rather point the finger, overtly
discuss, and get irate at the rulebreakers than actually build anything
positive.
My suggestion, if you were interested, which you're not, is to sit back a
little and let the people who ARE ACTUALLY BUILDING SOMETHING, along with
those who DO ACTUALLY INTEND to build something to get on with the task and
keep your distracting discussion to yourself.
Or maybe this is just never going to happen on this list, and we are
forever doomed to listen to the repeated diatribe of how to overtly
authenticate and heavily police and analyse every vagrant network ping like
its' some heinous DDOS attack. If so, why not start a new list yourself and
name it appropriately? Hrm?? :)
Are we going put together a wiki on how to build a routable
internet-connected 44net or not? What will it be? If we're going to
shout, take offence, throw toys, and do nothing then I don't care for it.
Make a decision.
Steve
> Are we going put together a wiki on how to build a routable
> internet-connected 44net or not?
Google "setup an AMPRnet Gateway" the info is out there, one of the
entries comes back from the wiki, It's actually a very simple
process.
* Here in the Washington DC area, we are ready and willing to make use of address space over RF links and make use of 44 address space.
* I personally use 44 space for experimentation and development of new protocols, which in most cases, might not work over the Public Internet. I also am working to implement services and mesh access to/from agencies the our ARES/RACES serves (e.g. standing links in situation rooms of our local hospitals, public health facilities, shelter go-kits, etc.).
* I'm not sure you reviewed RFC-6598 before suggesting use of 100.64.0.0/10 address space; but there are many technical restrictions that must be considered if using this address space.
- DNS and Reverse DNS cannot be used
- The addresses should not be forwarded outside of the "carrier's network," which could happen easily, even if by mistake
- DNS filtering of addresses is recommended as to prevent leakage of 100.64.0.0/10 queries into the public Internet
- A gateway's connectivity to the Public Internet may be lost if the carrier providing your "public" IP address switches to Carrier-Grade NATing (CGN)
- Newer devices may be RFC6598 aware and not behave correctly using CGN IP space (e.g. not provide DNS responses, not routing or forwarding packets, etc.)
If you need other private address space consider... 100.64.0.0/10 as
defined in RFC-6598.
73,
Lynwood
KB3VWG
I can echo a lot of what Robbie wrote.
My dad was in broadcast radio when I was younger. I read an article
by Larry Kollar, KC4WZK on the Amateur Packet Radio Network that was
floating around on dial-up BBS's and really caught my attention. That
kind of sealed the deal that I needed to get into the hobby.
When the locals gave me a copy of NOS, that was great. Before you
know it I had two NOS boxes networked using NE2000 drivers. Moved
from 1200 to 9600, and drooled when reading the VE3JF higher speed
pages. We even did webpages on 9600 baud RF in the mid 90's when we
all gravitated to Linux.
Lots of learning and fun.
Moving forward if you know anyone in the hobby with coding skills
there are plenty of things that can be done. Hopefully in the future
we can attract a few more of these types when they see the relevance
ham radio can offer with higher speed networks and that sort.
I am sure Chris could use a hand. How about a openwrt package for
hams? Be that out of part 15 frequency control, or something like
rip44d
http://wiki.openwrt.org/doc/devel/packages
Then there is always application ideas on 44net. I am impressed with
what is out there already.
On the RF side the broadband hamnet firmware developers could probably
always use a hand too.
73
Steve, KB9MWR
Hello,
Charles Wyble here. I'm new to the list and thought I would introduce
myself. Glad to be here. I'm the cofounder and CTO of the Free Network
Foundation (http://www.thefnf.org). I'm not currently licensed as a HAM,
however my co founder is.
I stumbled across 44net via some folks up in Seattle doing a HAM WAN
net.
My background is in large scale systems (10000+ servers), storage,
security, virtualization and basic data center networking. I'm now
getting into WAN networking and the fact that an entire /8 is available
to HAMs has convinced me to get my license very soon.
For anyone who wants to experiment with BGP/WAN networking etc, please
do let me know. (I've seen some folks on list express that, and I'll be
reaching out). I know my cofounder will be requesting some address space
very soon to experiment with. This is a great opportunity to get started
on the real internet, because as mentioned IPv4 space is almost
impossible to get these days.
I look forward to being an active participant in the list. As far as I
know, this is the only address space that's publicly
administered/discussed etc. That alone is a huge draw for me. Everyone
else that has space keeps governance closed.
> If the answer to either of the above is "yes", then there is the potential
> for traffic which violates radio licensing laws to be carried by radio.
And
> after all, I thought RADIO was what 44-net was supposed to be about?
No, 44net is a PUBLIC IP address range. There are plenty of PRIVATE IP
ranges that we can freely and arbitrarily use without care or regard
whatsoever, and the 10/8 network is large enough for hams to build a
substantial world-wide network without further ado.
Why my main concern is with all this 44net stuff, and what we're seeing a
lot of, is peoples' scaremongering and huge propensity to self-regulate and
self-police to the absurd, resulting in the 44net never being any more than
another reason to have an argument on some forum and then sit back on our
arse and do nothing whatsoever. If this is actually going to be the case
then my recommendation would be to find some facebook group or other forum
to put ones' efforts into, and see if you might stir up some irrational
waste-of-time argument there, because doing it in a 44net forum is likely
to, at the very least, cause quite a few people to just give up, and at the
very worst, have someone very concisely and perhaps not so politely explain
the problem to you.
Steve
At 08:37 AM 04/01/14, you wrote:
>(Please trim inclusions from previous messages)
>_______________________________________________
>Somethings not right ...
>
>I did a traceroute to 44.68.52.1 and 44.68.52.254 and this is what I
>received for both:
< ... SNIP ... >
>The last hop (88.149.154.126) is address space in Italy ?
Interesting... 88.149.x.x addresses have been trying to hack me and keep
getting banned.
Although, not specifically that address.
Wm Lewis (KG6BAJ)
AMPR Net IP Address Coordinator - Northern and Central California Regions
(A 100% Volunteer Group)
(530) 263-1595 (Home/Office)
______________________________________________
----------
This message is for the designated recipient only and MAY CONTAIN
PRIVILEGED OR CONFIDENTIAL INFORMATION.
If you have received it in error, please notify the sender immediately and
delete the original. Any other use of this E-mail is prohibited.
