44net-request(a)hamradio.ucsd.edu wrote:
> I have had a couple requests to tailor my attempt to document setting
> up a Linux AMPRNet gateway for the Raspberry Pi.
>
> I've just recently purchased a Pi and have been looking over the
> documentation, and I don't think it will work for what I'm trying to
> document.
I have a quite simple setup for a Raspberry Pi as a Linux AMPRnet gateway,
but in my experience everyone's setup is different and what works fine for me
is not what other people want to use.
My Raspberry Pi is in a datacenter so no NAT worries. It terminates all tunnels
(IPIP) and users Marius' RIP daemon for automatic routing. This works very
well after we have ironed out some problems.
It also runs a local copy of KA9Q NET which I access from home via "screen", and
it forwards a subnet of 44 adresses via an IPsec tunnel to my home machine,
where several of these addresses are used to provide other services (e.g. WWW).
The setup basically only brings up tunl0 and assigns an address, sets up a
separate route table and rules for net-44, manually inserts a couple of routes
and then fires up the ampr-ripd. Maybe 10 lines of bash code, that is all.
As I wrote, the setup is very simple and the details vary enough for it to be less
useful to others than I thought. I forwarded my complete config to a fellow
amateur who has a Raspberry Pi as well, ready for him to load it, but he never
did that and somehow prefers to build it again for himself. And probably that
is better anyway, as most of the fun of building such a thing is the studying
of the matter and the debugging.
Tinkering with the Raspberry Pi and networking is like homebrewing, copying an
existing configuration is like buying a shiny new Icom.
Rob
--- Snip ---
One of the major drawbacks to the IPIP tunnels used to transport
AMPRNet data is that they don't work when you are using Network
Address Translation (NAT).
--- Snip ---
I disagree. As long as protocol 4 is forwarded (or just use DMZ) it works fine.
I use 192.168.1.X on all my normal stuff at home, and my Ras Pi
running rip44d has a an address of 192.168.1.2. In my main home
router I point DMZ to that address of the Pi. I use a single USB
dongle and that interface has a 44.92.X.X address and connects to some
Ubiquiti gear. Works fine.
http://www.qsl.net/kb9mwr/wapr/tcpip/rip44d.htmlhttp://www.qsl.net/kb9mwr/wapr/tcpip/
Ok what are people actually DOING over their Internet-connected 44 radio
net?
VOIP? APRS? Video links? Repeater linking? IP cameras? Remote bases?
Any innovative suggestions?
Steve
--
Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
+64 21 040 5067
> From: "Marius Petrescu" <marius(a)yo2loj.ro>
> Why do you need to get off this list to do it another way?
> That is the whole idea of this list: Find new ways, and share your ideas.
> Boldly go where no one has gone before :-)
Sorry, I received a very discouraging email from a list member. I'll go
back to my usual tasks for a while.
Steve
Screenshot
This network (44.24.240.0/20) is available via both 209.189.196.68 and
198.178.136.80. However, I'm unable to list more than one point of
contact. I realize this was probably a design decision at some point,
but it doesn't seem like a good idea from a redundancy perspective.
--Bart
PS: If you're wondering why the image looks like crap, it's to satisfy
the puny 32kB message size limit of the list.
Can someone tell me if the encap.txt file is still available in the portal? I was looking for it today and cannot seem to find it.
Thanks
Jesse - WC3XS
On 3/24/14, 7:22 PM, Robbie De Lise wrote:
> Each link you setup between 2 nodes in the mesh needs a /30.
> You can get 64 /30's in a /24.
/31's are better :)
http://tools.ietf.org/rfc/rfc3021.txt
73's
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
On 3/22/14, 11:14 AM, Geoff Joy wrote:
> 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.
+1
I've said there are numerous things I don't care for with the way 44net is
used and deployed (not a personal attack :).
I've also mentioned I don't have the time to write up proposals and do stuff
to change it. As such I'm not going to bitch about it (or at least try not to).
I'd be happy to start a working group if I have some help, but between my day
job, building a simulcast repeater system, and doing the paperwork to get our
repeater group to to be 501c3 non-profit I just don't have the time to do it
all myself. I for one would like to get away from the IPIP encap, and get
more distributed interconnects to the internet for 44/8.
73's
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
Hi all,
It's a work in progress but the following link should provide a link
to the IP 44/8 address allocation document for NJ.
http://mrprosser.g7ltt.com
We have very little AX.25 traffic in NJ but we do have a growing Mesh
community which would benefit from this space.
Hands up if you want some!
Mark
> From: Robbie De Lise <robbie.delise(a)gmail.com>
> To: AMPRNet working group <44net(a)hamradio.ucsd.edu>
> Subject: Re: [44net] 44net problems - was: 44net cool toys
>
> We announce 44.144.0.0/16 over BGP to the public internet (in Belgium)
> This ip space is then run on our local variant of "hamwan/hamnet" in
> Belgium on 2.4ghz accesspoints and 5ghz and recently 24ghz backbone
> links.
> [....] very interesting read trimmed
Well done! Very nice! I think the best way to set up my local HamWAN is
just to get off this list and go do it your way. Others can also make up
their mind for themselves.
Steve
