Turning a Local ADS-B Feed Into an Easy to Read Dashboard

-
Image
  Have you ever wondered where the plane or helicopter overhead is coming from, where it is going or who operates it? I found myself logging into my SkyAware monitor several times a week to look up that information. The problem was that it only showed what was overhead at that moment and logging in took a minute or two each time. I knew there had to be a better way to see this information quickly and to keep a historical record of all the aircraft traffic I had observed. One of the fun side effects of running a local ADS-B receiver with dump1090-fa on a Pi with an RTL-SDR dongle, is that you end up with a constant stream of aircraft telemetry sitting on your Pi. aircraft.json updates every second or two with hex codes, positions, altitudes, speeds and it's all there waiting to be analyzed and not just sent to Flightaware. Recently, I learned about JetClock which is a slick, commercial desk clock that shows you the aircraft passing overhead with airline, route, photos and all kinds ...
Post a Comment

Automated Server Failover for Remote Stations

-

 



Overview

Here's a cool trick for anyone with a remote station that wants to have an automated computer failover. This router setup will allow you to have multiple redundant computers on site and if one fails, your remote users will automatically be sent to the backup machine.  When the primary comes back online, users are sent back there.  Any failures can be emailed to you from the router, so you can troubleshoot.


What you need

2 computers - can be Windows, Linux (Raspberry Pi, etc) or Mac

Mikrotik Router - In my case I'm using the hAP ac3 - which goes for about $110 on Amazon


Step By Step Setup (using the Mikrotik Web Gui or Winbox) - this is the IP you give to your users

1. Add a Virtual Service IP

This is the “VIP” your LAN clients will always use (e.g. 192.168.1.100).

    A. Open IP → Addresses

    B. Click Add New

        •  Address: 192.168.1.100/24

        • Interface: bridge (your LAN bridge, sometimes called bridge1)

        • Add a comment: ex. Node-RED VIP

   C. Click OK


2. Create NAT Rules

You’ll make two port-forward rules: one for the primary server (e.g. Node-RED-A), one for the backup (disabled until needed). In this example, the primary server is at 192.168.1.10 and the backup is at 192.168.1.11.

    A. Go to IP → Firewall → NAT

    B. Click Add New

        • Chain: dstnat

        • Dst. Address: 192.168.1.100

        • Protocol: tcp

        • Dst. Port: 1880 (e.g. Node-RED port number)

        • Action: dst-nat → To Addresses: 192.168.1.10

        • Add a comment: e.g. Primary Node-RED

        • Click OK


     C. Add another NAT rule for your second server (e.g. Node-RED-B)

        • Chain: dstnat

        • Dst. Address: 192.168.1.100

        • Protocol: tcp

        • Dst. Port: 1880 (e.g. Node-RED port number)

        • Action: dst-nat → To Addresses: 192.168.1.11

        • Add a comment: e.g. Backup Node-RED

        • Click OK

3. Configure Netwatch - This tells MikroTik router to monitor the primary Node-RED                     (192.168.1.10) and switch NAT rules if it goes down. This will send your users to the backup     server.

    A. Go to Tools → Netwatch

    B. Click Add New

        • Host: 192.168.1.10

        • Interval: 00:00:10 (check every 10 seconds)

    C. In the Down tab (script to run if .10 is unreachable), paste (make sure these match your             comment labels from above):

        /ip firewall nat disable [find comment="Primary Node-RED"];

        /ip firewall nat enable [find comment="Backup Node-RED"];

    D. In the Up tab (script to run when .10 comes back), paste:

        /ip firewall nat enable [find comment="Primary Node-RED"];

        /ip firewall nat disable [find comment="Backup Node-RED"];

    E. Click OK

4. Add Hairpin NAT - This allows clients that are in the same subnet as the servers to route correctly, you’ll need a srcnat masquerade to handle “hairpin NAT” (required when client and server are on the same network and traffic goes through the router).

    A. Open IP → Firewall → NAT

    B. Click Add New

    C. On the General section:

        • Chain: srcnat

        • Src. Address: 192.168.1.0/24

        • Dst. Address: 192.168.1.0/24

    D. Switch to the Action section:

        • Action: masquerade

        • Add a Comment: e.g. Hairpin NAT for Node-RED

     E. Click OK

5. From another computer on the router, go to 192.168.1.100:1880 and then plug and unplug your primary and backup servers from the router to test the failover. You can also see it enable and disable routing rules on the router screen by going to IP → Firewall → NAT.

Setting Up Email Alerts (optional)

When a server goes down, you might want to be notified. The router also has the ability to send emails to you when a server fails.

1. (optional) Configure Email App Password Settings - Gmail (if this is your provider/you have 2-Step Verification on)

          • Go to your Google Account (myaccount.google.com)

          • Select Secuirty (left hand column)

          • Under "How you sign in to Google" select 2-Step Verification
        
          • Scroll down to App passwords

          • At the bottom of the page, enter a name for the App password (e.g. Node-RED)

          • Click Create

          • A screen will not pop up saying - Your app password for your device - with a password

          • Copy this into a file as you will not ever see it again and will need to make a new one if              you lose it

          • Click Done

2. Configure Email Settings

    A. Go to: Tools → Email

    B. Enter in (for the example settings, we'll use Gmail):

        • Server: smtp.gmail.com

        • Port: 587

        • TLS: start tls

        • From: the email address you be sending from (e.g. dave@gmail.com)

        • User: your email address at Gmail (e.g. dave@gmail.com)

        • Password: the application password you set up above

        • Click Apply

3. Create a Netwatch Monitor

     A. Go to Tools → Netwatch

    B. Click Add New

        • (optional) Type: httpd-get (if you want to test for a specific service (e.g., Node-RED) -                 otherwise leave as default

        • Host: Enter the IP/hostname you want to monitor (e.g. 192.168.1.10 from above)

        • Interval: How often to check (e.g., 00:10:00 = every 10 minuntes)

        • Timeout: How long before it’s considered “down” in seconds (e.g., 30.00) 

        • (optional) Port: 1880 (if you want to test for a specific service (e.g., Node-RED)

        • In the Up second (script to run when .10 comes back), paste - adjust what's in quotes to              your preferences:

 /tool e-mail send to="dave@yahoo.com" subject=".10 Host UP" body="The host 192.168.1.10 is now reachable."

        • In the Down section (script to run if .10 is unreachable), paste - adjust what's in quotes              to your preferences:

/tool e-mail send to="dave@yahoo.com" subject=".10 Host Down" body="The host 192.168.1.10 is DOWN."

Do this for each server you want to monitor.

4. Test - plug and unplug servers and you should receive the corresponding up and down emails.

If you've made it this far, you now have a highly available server setup for Node-RED or any other important application.








     



    




Comments

Post a Comment

Popular posts from this blog

How To Get Precise Time Outside Your Shack

-
Image
  Often when I decide to do Parks on the Air (POTA), I just grab my gear and go forgetting to sync my laptop’s time.  When I get to the park, sometimes my system clock is 5-30 seconds off which means I’m not able to do FT8. I have found some inexpensive solutions to help fix this issue.  First, you’ll need a GPS dongle to capture accurate time signals.  These dongles are great and can get time almost anywhere, if they have a good view of the sky.  Here is the one I like since I can move it around if I need to and can keep it away from my radio to reduce RFI. It is called the “VFAN USB GPS Receiver Antenna Gmouse for Laptop PC Car Marine Navigation Magnetic Base” and available on Amazon for $20.  If you want something less expensive ($12) and smaller, I’ve heard good things about this unit (although I have never used it) – “HiLetgo VK172 G-Mouse USB GPS/GLONASS USB GPS Receiver for Windows 10/8/7/VISTA/XP”. Next, you’ll need software to allow your computer...
Read more

How to Put Your AllStar Node on 44Net Connect

-
Image
  Recently a blog reader, Will WY7WL reached out about putting his Allstar node on to 44Net.  He was running into issues with connectivity to his node since it was behind CGNAT and wanted to see if he could adapt the 44net-cloud-wireguard-rpi script I had on Github for his application.  As I began testing it for him, I saw several things that needed to be customized to make the script work with the HamVoIP software, including making sure the software was at a current version, employing iptables for better compatibility and tweaking firewall settings to support Supermon.  So, I have created a special script to support this Allstar HamVoIP that handles everything soup to nuts and it is located at https://github.com/n3bkv/hamvoip-wireguard/blob/main/setup_hamvoip_wireguard.sh I also have an ASL3 version that Will help me test (since I do not run ASL on any of my own nodes).  That is available at - https://github.com/n3bkv/asl3-wireguard/blob/main/asl3-wg-setup.sh W...
Read more

How To Set Up Your Own Remote Station

-
Image
  I’m going to share with you an inexpensive way you can control your station from a web browser on your home network.  This is the first step in setting up a remote station for yourself.  Once you have the radio  working locally, you can explore more advanced access solutions like Tailscale or Zerotier VPNs for operation outside of your home network. I found a great free program to remote control radios from F4HTB called “Universal_HamRadio_Remote_HTML5”.  Here is a link to his Github with more information - https://github.com/F4HTB/Universal_HamRadio_Remote_HTML5. Since there are a lot of steps to setting it up manually, I have put together a script that will do a large portion of the work for you.  I have tested the script with an Icom IC-705 and Yaesu FTDX10 utilizing both radio soundcards so there is no need to construct the hardware interface for these radios that he mentions.  The difference between the two radios is which version of Hamlib is...
Read more

Why You Might Want To Set Up Your Raspberry Pi Internet Web Server on 44Net

-
Image
  I had a big problem with my blog. Since it’s hosted on Blogger, there were issues with Google and Bing indexing it. I must have spent nearly two weeks trying to figure out why search engines were having trouble with redirects and couldn’t index the site. After some research, I found out this is a common problem with Blogger. So, I decided it was time to set up my own web server. That way, I’d have full control over everything—from which content management system and plug-ins I use to how the site is hosted. I had a spare Raspberry Pi sitting around that I could use, since my site doesn’t get a lot of traffic. All I needed was a static, internet-addressable IP address. But those are generally hard to come by without an expensive business-class internet connection. As hams, we have access to millions of IPs for free, thanks to some forward-thinking operators from the 1980s via 44Net. Here’s a link to an article and a short video on the history of 44Net: https://www.ardc.net/ardc-ki...
Read more

Build a Central N3FJP Field Day Log Server With Local DHCP and GPS Time

-
Image
Centralized Field Day logging is one of those things that looks simple until the network hiccups, the generator burps, Windows decides it is “helping,” or one laptop thinks it is 2019 and another thinks it is next Tuesday. My club was looking for an easy-to-use solution for FD 2026 that would tie all the logging computers in our main tent together to simplify log submission and track our total progress during the event. But past attempts with a logging server brought to light many issues, especially individual station computers locking up when there were server or network issues. The goal is simple: all operators log to one reliable N3FJP server with consistent local IPs and accurate time without internet access. Here is a practical way to build a central N3FJP Field Day logging server that does not depend on the internet: One Windows server laptop or mini-PC that runs the N3FJP master FD log. The server also hands out local IP addresses using a local DHCP Server for Windows. All Field...
Read more

Building a Secure Web Portal on 44Net Without VPN Headaches

-
Image
I've been running Node-RED on my home network for a while now, controlling various ham station functions and monitoring gear remotely. The problem? Accessing it from outside my network meant either opening it directly to the internet (yikes) or dealing with VPN clients on every device I wanted to use. VPNs work, sure, but they're a pain. You need to install clients, manage configurations, deal with connection drops and if you want to give access to other hams in your club? Good luck walking everyone through VPN setup on their computers. Plus, most free VPN solutions limit you to a handful of users. I wanted something better. A secure web portal that I could access from anywhere with just a browser. No client software, no complicated setup for users, but still locked down tight with proper authentication and encryption. That's when I decided to build out a proper web portal on 44Net using Traefik and Authelia. After getting it working, I packaged the whole thing into an auto...
Read more

Getting WaveNode Power Meter Data Into Node-RED

-
Image
  I've been using a WaveNode WN-2 power meter at our remote station for years now. It's a fantastic piece of gear - four independent RF channels, high SWR alarms, forward and reverse wattage monitoring and a Windows app that displays everything in real time. Check it out at: https://wavenodedevelop.com/controllers/wavenode-wn-2/ But here's the problem: the data lives in the WaveNode application and nowhere else. I wanted that data in my Node-RED dashboard. I wanted it in Grafana for historical trending. I wanted to trigger automations based on SWR readings or power levels. The WaveNode software wasn't designed to share its data with other applications. So I built a bridge. The result is WaveNode-to-MQTT, a small Windows utility that grabs all the WaveNode data and republishes it to MQTT topics. Once it's in MQTT, you can do anything with it - display it in dashboards, log it to databases, trigger alerts, whatever you need. Here is the project link: https://github.co...
Read more

A Non-Programmers Guide on How To Use AI to Write Your Own Custom Ham Radio Computer Applications

-
Image
  These days you can’t get away from the Artificial Intelligence (AI) hype, it is unavoidable.  Supposedly it can do anything and everything with no limitations. But beyond the marketing, there is a lot that AI can do to help make your life easier. I’m going to walk you through how you can utilize AI for ham radio applications.  It is a great way to solve problems and create software for your projects, even if you are not a programmer.  I think the best way to show you how to use an AI Large Language Model (LLM) is to run through the prompts I used on a project for remote station temperature monitoring. I needed a way to get sensor readings from an external sensing board on a Raspberry Pi for display on a computer data dashboard.  I decided I wanted a script that could collect the readings every few minutes and transmit them to a second computer that served up all the dashboards for the station.  Some call this a “single pane of glass” since you can go to...
Read more

Turning Your Starlink Mini into a Real Telemetry Device - How to bridge Starlink Mini into MQTT and Node-RED for real-time monitoring and automation

-
Image
  If you’re running a remote station, digital voice system or any kind of modern connected ham infrastructure, your internet link is no longer “just internet” — it’s part of your station. Starlink Mini gives you portable, high-availability connectivity, but out of the box it’s still a black box. You can see “online/offline,” but you can’t easily observe performance, uptime, obstruction trends or state changes in a way that integrates with the rest of your telemetry systems. That’s exactly what the starlink-mini-mqtt-node-red-1 project solves. This project creates a bridge between Starlink Mini, MQTT and Node-RED, allowing you to treat your satellite link like any other piece of instrumented infrastructure in your shack. What It Does The system polls Starlink Mini status data and publishes it into MQTT topics that can be consumed by: - Node-RED - Home Assistant - Grafana - InfluxDB - Custom automation workflows Once it’s in MQTT, it becomes part of your normal telemetry pipeline. Ty...
Read more

Why You Should Use SSH Keys Instead of Passwords on Your Raspberry Pi

-
Image
  If you’re running a Raspberry Pi that’s reachable from the Internet — such as through 44Net, or any public-facing IP — security should be your top priority. One of the most important steps you can take is to disable password logins and use SSH keys instead. Why Passwords Are a Problem Password authentication over SSH might feel convenient, but it’s one of the biggest security weaknesses for exposed systems:      • Brute-force attacks — Bots continuously scan IPv4 and IPv6 ranges trying common usernames like pi, admin, or ubuntu.      • Leaked credentials — If you’ve reused a password elsewhere and that service gets breached,             attackers can easily try it against your Pi.      • Keylogging and phishing — Passwords can be intercepted if you log in from an insecure machine or network. Even strong passwords can’t match the security of asymmetric cryptography used by SSH key pairs. What SSH...
Read more

Ham RSS News Feeds

Amateur Radio Daily

Loading...

ARRL News

Loading...

Zero Retries

Loading...