NODE STATUS IS NOW FOUND IN THE TOP MENU BAR.
- WHAT'S ON THE NODE
The following applications are available on the SDVAZ:WY7EMT-7 node:- BBS (intra-BBS email and news groups)
- CHAT (connects to western US master chat server...see below)
- NEWS (updates for THIS node only)
- WEATHER (limited AZ locations)
- WORDLE (with network scoring)
- DAPNET (DAPNET paging gateway)
- PACKET'S DEAD
To modify the famous quote by Samuel Clemens, "the reports of packet radio's death are exaggerated".
I'm not just talking about APRS. There are areas of the country, where packet nodes are few and far between, but if you look at the worldwide node map for BPQ nodes, you'll see a LOT of nodes.
These are just the ones running BPQ - who knows how many more nodes are out there running software that doesn't "phone home" to the "main map"?
The BPQ network here in AZ seems to be growing again, like it is in many parts of the world. - SECURITY
I've had a lot of random, repeated, failed connection attempts from all over the world (mostly Africa, North Korea, China and the former Soviet-bloc countries). This has caused me to severely restrict the traffic crossing my firewall. I've been forced to impose blocks on those continents and countries. As a further measure, you will need to arrange any BPQ links to my node BEFORE you add the MAP for it. Only a MAP entry in my config is allowed access through the firewall. Even MAP entries using a random IP address from their provider will need to make arrangements. My server picks up on the IP addresses in the axipcache, strips the rest and uploads the IP addresses to my firewall every 5 minutes. The firewall reloads those IP address every 5 minutes and *POOF*. Your node's allowed through - dynamic IP address or not.
I really hate doing it this way, but even though I'm not NASA or a bank, I still don't want people just randomly hammering at the systems behind my firewall.
See LINKING below. - WHY SO FEW [ ROUTES | LINKS | NODES ]?
If I've had to restart the server or software for any reason, it can take up to 15-20m for the routes and links to be set back up. Once that's done, the system has to wait for the other nodes to tell this one all of the other nodes they can access. If one of the other nodes has to restart it's the same thing. On top of all of that, there a 2 minute cache for this website that has to expire before it'll serve a page again. Also remember that the node data shown on this site is only updated every 5 minutes, to reduce strain on my server. The most current information for the node is at http://internal.lltodd.family:8008 (NOT HTTPS!!). - #LINKING
I welcome other nodes linking into mine. If you want to link, please contact me HERE so I can add a reciprocal link. The node's map is:
MAP WY7EMT internal.lltodd.family UDP 10093 B
I can also take links from other NET/ROM-compatible nodes, though I can't help you set up your end.
REMEMBER TO CONTACT ME BEFORE ADDING MY MAP TO YOUR SYSTEM OR YOU WON'T BE ABLE TO CONNECT TO MY NODE (see SECURITY above). - PACTOR / PACKET NODES
You can access this node from other nodes via their HF/VHF/UHF packet, VARA, ARDOP, Robust Packet or Pactor nodes.
Please see the global map at https://nodes.ukpacketradio.network/packet-network-map.html?rfonly=0 to try to find one near you.
The global map is automatically updated every so many minutes by each BPQ node, so if the map shows it's online, it's actually online.
You can also access this node from any BPQ node by using their AXIP port to connect to node WY7EMT-7 or SDVAZ. - TRANSFERS
We support binary, B1 and B2 transfer protocols on the FBB port. - FORWARDING
We currently forward with all of our link partners. - CHAT
There are three #BPQ worldwide chat hubs on the planet:
#USWCH:WA3WLH-14 (Western US), #USECH:K8OPG-14 (Eastern US) and #RRRCHT:PE1RRR-4 (Netherlands)
All of the hubs are interconnected, so as long as someone is logged in on one hub, you can talk to them from any other hub.
A message sent from one hub is sent to all hubs.
- ACCESS FROM OTHER NODES OR PACKET DIGIS (NOT APRS DIGIS)
Connects from other nodes are more than welcome and are currently the only way to get to the node.
If you're using a packet digi, you'll have to connect to the closest BPQ node and then use their AXIP port to connect to WY7EMT-7 (SDVAZ).
Telnet access is strictly limited to certain situations or individuals. Email me and make your case if you ABSOLUTELY need access that way. - 145.010 1200 BPS PACKET
I'm still working on getting the node on the air. When I do, this will be the frequency. I may or may not open my node to PACTOR-1 connections at night
after I get my General. I will post a notice in THIS site's blog when the VHF radio goes on the air.
I admit that I'd really like to see all of the AZ BPQ nodes linked together into a state-wide network.
So why DryNET? I spent 10 years in the Seattle area and there are basically two different Washington states.
The part east of the Cascades, known as the "Dry Side" and the part west of the Cascades known as the "Wet Side".
The Seattle area had a packet network back then called "WetNet" and now that I live in Arizona, it made sense to refer to the growing BPQ network here as the DryNET.
Okay, it was either that or DesertNet, AZNET or some such.
If we can ever all get linked with a standardish set of connection settings, maybe we can formalize it into an actual network. Who knows.
Right now, there's only three full-time and one part-time node and one APRS-only node.