Update 1: Ongoing AMPRNet, ampr.org, 44 Net problems
July 12, 2009:
Probably better titled “AMPRNet ongoing challenges!”
Back on June 25th I published a blog entry titled “Ongoing AMPRNet, ampr.org, 44 Net problems.” This would turn into the most popular ham radio related posts on my blog and drew several email inquiries. After a few emails to key folks, chatting with a few folks on my last trip up there, and watching list traffic, I figure it’s time for some updates.
1. It appears external connectivity to AMRPNet is back as of late June 2009. Some gateway systems have had to make changes and/or have pretty much disappeared recently. List traffic has calmed down, so I guess most folks are either happy or moved on to other projects for now.
2. I think mirrorshades.ampr.org got at least a partial upgrade. Judging from tidbits here and there, I believe Brian Kantor has a few more glitches to be worked out before it’s fully upgraded. I believe the original mirrorshades server was built upon FreeBSD (or a BSDi variant). The BSD kernels and network stack have a rock solid track record, but they have understandably changed just a wee bit over the last decade or so. Thus the major upgrade to a much newer OS version necessitated several changes to the AMPRNet software.
3. I gather Brian Kantor, WB6CYT is working on the needed changes to the gateway code, but is currently very busy with other work/research related priorities. Don’t take this wrong, that’s all fine and understandable. It’s a hobby so family, work, and so forth takes priority.
4. These latest problems do illustrate why building networks and links that count on the AMRPNet gateway to be there is probably a bad idea. It might be one thing to use it for non-critical links and experimentation, but another thing to use AMPRNet for critical links. Stop cutting corners and build out your local RF infrastructure!
UPDATE 2012: Due to the evolution and growing threats of a cyber-attack/cyber-warfare I no longer feel it wise to build EMCOMM networks with ANY internet exposure. Also suggest AR EMCOMM folks think twice about building any system that has any TCP/IP exposure to it. Think RF only, minimal infrastructure, and completely independent of any IP based network…public or private/internal.
Hams need to wise up to today’s world of EMCOMM, what today’s real world communication emergencies will probably look like, and start thinking/planning past the threats of the 1980-90′s. If your approaches could easily leave you just as impacted as your served agencies…then you will not be of much use to them in a variety of scenarios where ham radio will be needed the most.
5. Best I can tell, all of Richard “Brian” Rogers, N1URO’s systems are gone from the internet. The last I checked, his various domains/email domains continue to be gone/down. (Update: See #7 & 8 below)
6. While I’ve never met N1URO personally, I’ve traded a few emails with him over the years. Brian was always struck me as very dedicated to packet radio and his AMPRnet networks up in New England. So him just “pulling the plug” suddenly and without notice, just didn’t add up.
7. I’ve now confirmed what happened with N1URO and his packet radio/AMPRNet systems and it explains things. Back in late May 2009, Brian was presented with some very serious and unexpected personal challenges. Let’s hope things work out the way they should for him and I’ll leave it at that for now.
8. Based upon the recent information regarding N1URO and his packet/AMRPNet systems, it’s probably safe to say that those systems will not be returning to the airwaves. Folks holding out hope for those systems to return are probably going to be very disappointed. The best I can tell, this leaves the New England area (at least CT) with no easy “remote” telnet access into the local RF networks from outside the area (see #9 below).
9. I am currently looking for someone in the southern Connecticut or even the Long Island area interested in hosting a BPQ32 packet switch with telnet access. Drop me a note (callsign at yahoo.com) if you’re interested. Due to location, terrain, and not wanting to impose another antenna on my landlord, my 2nd QTH up there is not a good choice. I might be able to hide a 2 or 3 element UHF yagi aimed at the Shelton BBS site, but would rather explore a better location.
UPDATE 2012: Not interested in this anymore. The packet BBS network up there is in shambles and too unreliable for usage beyond “local” coverage. Several of us have ran some tests on in it and Missing Sysop Syndrome (MSS) was very present. It’s hard to bite my lip when I hear them “chest beating”one day, then complaining about lack of usage the next. I have just adopted an approach that doesn’t depend on the very broken global/national BBS network and keep my own HF gear staged there so I can stay in contact back home if needed.
To climb up on this soap-box more…. Hurricane Irene, the October snowstorm, and the last few SETs should of been huge wake up calls for CT ARES, but apparently not. The existing packet system there seems barely useful for moving NTS traffic if the links are working, but forget moving non-local p-mail or ICS traffic flows over it.
There was virtually no “real” usage of NTS except maybe a few NTS op self-generated msgs during several serious EMCOMM scenarios that played out in 2011. When you see those monthly NTS traffic counts/reports, try to get a breakdown of “book” vs “real” traffic from them….good luck. I’m sorry, but the current NTS approaches just don’t fit well in an increasingly ICS/NIMS world. Doesn’t mean NTS needs to go away, but it will if it stays on the present course. Unfortunately NTS leadership can’t seem to come to grips with that reality. My ARRL HQ contact hinted that they are very worried about how to break this “reality” to the NTS folks due to past reaction to very subtle “hints” about how NTS must change to regain relevance.
10. While I haven’t talked to Jay Ferron, N4GAA in ages, I think I can guess at what happened with his AMPRNet to RF gateway up in West Haven, CT. I think N1URO has been maintaining the N4GAA gear for the last few years now. Now with Brian’s situation, I’m guessing that Jay didn’t have the time to resume maintaining/supporting the N4GAA packet gear, gear that would be highly impacted by the loss of N1URO’s gear/links. Thus he choose to “unplug and move on.” (Update: see #11 below)
11. I was up there in CT a few days ago and thought I heard something on N4GAA’s user channel (145.090), but it could of been other systems up there. I also thought I heard some traffic flows on the 441.0500 1.2kb user channel, but this may of been the W1HAD BBS/node just polling/probing that port. I was busy with other priorities so I didn’t have the time to hook the D7 HT up to the laptop and see exactly who/what the traffic was. I also didn’t have time to see what 223, 421, and 438 MHz RF links are still in place. Will have to pack my IC-R10 receiver with me on the next trip up.
UPDATE: I have unconfirmed reports that N4GAA’s RF infrastructure is still in place at West Haven, CT. Maybe just the gateway was turned off?
UPDATE 2: The packet systems at N4GAA are gone. The traffic I heard on 145.090 was likely K2YYD’s WinLink station over on Long Island. The 441.0500 traffic flows are a link from the Shelton BBS/FlexNet node over to WA2PNU’s node/BBS on Long Island. I don’t think the 421.9500 9.6k port at Shelton to K2PUT is back up yet. I’ve observed that all my connects to W1HAD seems to go over the 220 or 441 1200 baud links.
12. K2MF’s gateway is gone for now. I say “for now” as I detect hints that it might return later on down the road? There are some hints that he’s tinkering around with some stuff to overcome the recent challenges due to N1URO’s departure from the packet scene. I think he’s about to retire form WCBS soon and maybe moving to Florida (at least part time).
UPDATE: I don’t think the above is coming back.
13. I think Barry, K2MF was very dependent upon N1URO’s hubs/gateways. When that gear and associated connections disappeared, it pretty much clobbered his AMPRNet connectivity with no quick fixes available to him. I’d say there’s a good lesson to be learned here, hint hint. Again, not bashing or dissing anyone, but let’s learn from it.
There are several fairly large packet networks out there linked together without the use of AMPRnet infrastructure. The myth that you have to use AMPRnet/44 net to do internet linking of packet radio systems is just that…a myth.
Some lessons we can learn from this can be found in these related posts:
AMRPNet – lessons learned, things to consider.
Your local ham radio infrastructure, use it or loose it.
