Lets keep this discussion going - we can change things.
Quoting as required;
Ubiquiti & Mikrotik are great for building highspeed wireless ip networks
Yup I have three APs on 2.4 and another three on 5.8 on a mountain top site. No 44 on it, because the routing daemon doesn't work on Mikrotik.
And the gear costs almost nothing - compare a "new transceiver" for these bands compared to a "new transceiver" for any other band.
If we could change the demographics of the hobby that would help.
I take your point, but you get on PSK31 and have a look at the age demographic there - be prepared to be shocked to see many of these operators over 60y.
You have to have something first to entice them.
Agreed. We need cool toys! And there ARE PLENTY.. As in the next paragraph - engage with these groups and offer them our product.
How many people even know about the 44net space? Maybe we need to reach out to;
-The broadband-hamnet developers - presently they use 10.X.X.X address space
-VOIP developers, like IRLP, Echolink, and Allstar.
-Hams who run internet servers, like qsl.net, etc
I think your suggestion is paramount. I submit this is a way forward, if not THE way forward.
Then there is the issue of how to integrate 44net into your home network.
Agree completely. Do we need a dial-in PPP server for those who "just want a 44/32" ?
The second problem is regulatory. Data bandwidth issues, content issues..
all deturants.
I agree, but the problem is not what quite you suggest here.
I think we need to ditch this attitude of heavily self-regulating ourselves. Hams have traditionally held this concept dear - one of overtly interpreting the rules heavily in our own disfavor. I don't think we do ourselves any positive service at all with this, particularly so when the result is we now stop and do nothing at all because of our own attitude. If some user does something inappropriate, it is normal to warn once then revoke access for some time - a normal and acceptable approach anywhere. I think we should free our attitude up a little.
There have been issues of bandwidth as well, but these days a VDSL or fibre connection isn't expensive, and neither is 100G of data to go with it.
Steve
On Wed, Mar 19, 2014 at 12:39 PM, Steve Wright stevewrightnz@gmail.com wrote:
Ubiquiti & Mikrotik are great for building highspeed wireless ip networks
Yup I have three APs on 2.4 and another three on 5.8 on a mountain top site. No 44 on it, because the routing daemon doesn't work on Mikrotik.
Don't let the routing daemon stop you. IPIP and routing tables work just fine on Mikrotik gear.
Tom KD7LXL
Hi All,
I am, 75 years of age and not quite senile in spite of some comments on this thread and have lots of nice ham type toys running on non 44 net services, I would love to run them on ham only 44 net but it's made just to dam hard
With the real world networks I can buy a router / modem set up a few minor parameters and hey presto I can run my own networks (2 of around my place) and have mail servers, web sites, ntp servers, ip cams, irlp, aprs igate, jnos, an fbb bbs, BPQ and packet radio all running reasonably easy.
Much of this stuff is running on raspberry pi computers but some is running on linux boxes and some (gasp horror) on windows boxes. Lots of it is connected to ham radio transceivers for other ham access to my systems.
About a year ago I decided it was high time I looked into the 44 net because some of the raspberry pi distros I was reviewing had 44 net access hard wired into the code for the various ham functions.
I joined this mail list and also applied through the portal for an address allocation.
Well I am still waiting for an allocation and am becoming more convinced that even if I had one I couldn't use it
From discussions on here it seems that, my "off the shelf" modem is not
suitable and I will have to basically replace it with another. This would be a real pain because I like my current modem/router which has heaps of nice facilities built in for traffic flow measurements and a very comprehensive and easily controllable port forwarding and redirection ability. It also has an inbuilt DECT base station, amongst lots of other things.
But to join 44 net I have to turf this out, flash an old modem with (unsupported) software and lose most of the facilities that I, as a non professional user of data services want in my network. Or so it seems to me at the moment.
Why not look at making it easier for people like me. All I want is use of the 44 address range to quickly and simply link with other fellow hams in a _hobby_ environment, not spending my days acting as a wannabe professional communications engineer (even though a few years ago I was one).
When I was setting up my various toys there were comprehensive and simple, understandable, instructions available for making them both secure and operational. This is not the case with amprnet from what I see by reading here.
I don't mind learning new things, in fact I revel in it, but if you want to expand the user base there does need to be a beginners guide or at least an accessible "dummys guide for amprnet" for people like me whose learning is either a bit dated, or based on other non data fields of endeavour. Remember ham radio is a hobby not a career. The system also needs to be more compatible with off the shelf existing hardware.
I get quite frustrated with the situation because I have a raspberry pi sitting on my work bench here with its jnos software pleading with me to tell it my 44 address and another running a nice piece of software running a combined aprs/ fbb/dx server distro also asking for my 44 address. At the moment they are just unusable curiosities because of the "missing link"
All I really want to do is share use of the toys I have built on air with other hams and provide a continuing service to my long term digital over ham radio mates.
Whilst contrary to what others have said on this thread, data services are not that cheap in Australia, I do have the use of 150Gbytes a month and my other usage is such that I can and do share a fair bit of this with over the air ham services.
Now I bow down before the amprnet gurus and worship them from afar, but please don't forget the end user like me who just wants a simple allocation that can be used just like Iike I use my real world static I.P. , that is set and forget.
If you satisfied a need like that then I am sure many more hams would participate in the valuable and amazing resource of the 44 net .
It can't be just a coincidence that my spell checker wants to replace the word amprnet with amphetamine considering that the effect both words have is similar to the end user..
I will now standby and await enlightenment from on high..........
Tony VK3API Newbie to Amprnet 50 years in digital ham radio .
Hello Tony (VK3API),
I read your story with great attention, interest and growing respect, indeed. Congratulations!
Myself I'm running successfully quite complex server on Raspberry Pi v2 http://www.sp2lob.ampr.org http://linux.sp2lob.ampr.org
Best regards. Tom - sp2lob
Just to answer a previous question of KB9MWR:
I verified ampr-ripd on the following architectures (and it runs) on Linux x86, Linux x64, Raspberry Pi and Mikrotik mipsbe OpenWRT Metarouter. Next on test this weekend is the Cubie Truck (Cortex A20 ARM7) with Debian 7.
If there is a OpenWRT implementation for WRT54G probably it could be set up for that platform, too.
Marius,
Thanks for all your hard work. I went to your website: http://www.yo2loj.ro/hamprojects/ I didn't find any documentation on how to use it. Specifically, I'd like to understand: 1) After compiling, then what? In other words, what is the recommended way to run it? 2) What timeout or hold-down timers exists and how are they configured (if possible). For example, if a route disappears from the updates sent by amprgw, how long before it is removed from the table? And is that configurable? Also, is it a two-step process (i.e. first marked as unreachable and then later removed)? 3) If amprgw updates cease completely (i.e. amprgw is down or hung), is the behavior different? Or do all routes eventually time out at the above interval? 3) Is there anything else configurable? 4) Are there any status commands? Does it generate a log? Where? What are useful tips on how to manage it and how to troubleshoot problems?
Thanks, Michael N6MEF
-----Original Message----- From: 44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu [mailto:44net- bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of marius@yo2loj.ro Sent: Thursday, March 20, 2014 7:16 AM To: AMPRNet working group Subject: Re: [44net] 44net cool toys
(Please trim inclusions from previous messages) _______________________________________________ Just to answer a previous question of KB9MWR:
I verified ampr-ripd on the following architectures (and it runs) on Linux
x86,
Linux x64, Raspberry Pi and Mikrotik mipsbe OpenWRT Metarouter. Next on test this weekend is the Cubie Truck (Cortex A20 ARM7) with Debian
7.
If there is a OpenWRT implementation for WRT54G probably it could be set
up
for that platform, too.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
1. Inside each archive, there is a "manual.txt" which describe all parameters and their defaults and the installation procedure. Also there is a script for finding the RIP password and a example startup script. 2. The route exire time is 10 minutes (parameter EXPTIME at the beginning of the source code file), meaning that if after 2 successful RIP receive rounds the route is not announced, it will be dropped. There is no 2 step process. If a route is received with metric 15, it is dropped immediately (not used in the RIP broadcasts but implemented). 3. If updates are not received, no change in existing routes take place unless RIPv2 reception is resumed. 4. No status commands or logs are available, only the latest current route configuration is stored in "/var/lib/ampr-ripd/encap.txt" (it can also be changed in the source file - just a define) For debuging, there is a -d (debug) and -v (verbose) available. For deeper debugging there are 2 additional compile options in the makefile, allowing deeper debug including netlink tracing. (thse need a recompile).
73s de Marius
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Michael E Fox - N6MEF Sent: Thursday, March 20, 2014 16:57 To: 'AMPRNet working group' Subject: Re: [44net] 44net cool toys
(Please trim inclusions from previous messages) _______________________________________________ Marius,
Thanks for all your hard work. I went to your website: http://www.yo2loj.ro/hamprojects/ I didn't find any documentation on how to use it. Specifically, I'd like to understand: 1) After compiling, then what? In other words, what is the recommended way to run it? 2) What timeout or hold-down timers exists and how are they configured (if possible). For example, if a route disappears from the updates sent by amprgw, how long before it is removed from the table? And is that configurable? Also, is it a two-step process (i.e. first marked as unreachable and then later removed)? 3) If amprgw updates cease completely (i.e. amprgw is down or hung), is the behavior different? Or do all routes eventually time out at the above interval? 3) Is there anything else configurable? 4) Are there any status commands? Does it generate a log? Where? What are useful tips on how to manage it and how to troubleshoot problems?
Thanks, Michael N6MEF
-----Original Message----- From: 44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu [mailto:44net- bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of marius@yo2loj.ro Sent: Thursday, March 20, 2014 7:16 AM To: AMPRNet working group Subject: Re: [44net] 44net cool toys
(Please trim inclusions from previous messages) _______________________________________________ Just to answer a previous question of KB9MWR:
I verified ampr-ripd on the following architectures (and it runs) on Linux
x86,
Linux x64, Raspberry Pi and Mikrotik mipsbe OpenWRT Metarouter. Next on test this weekend is the Cubie Truck (Cortex A20 ARM7) with Debian
7.
If there is a OpenWRT implementation for WRT54G probably it could be set
up
for that platform, too.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net