Many HAMS & GMRS users believe they need to buy a static IP address from their ISP to run a home node, hotspot, or DVSwitch server. Good news: you don’t. In almost every case, a simple and free tool called Dynamic DNS (DDNS) solves the problem completely.

Below is a clear explanation you can share with anyone setting up a home node, AllStar, DVSwitch, or any remote‑access ham radio system.

So someone told you you had to have a static IP to use DVSWITCH or remote connect to your node.
This is incorrect. This problem was solved way back in the 90s. Everyone should know this.

Why People Think They Need a Static IP

Most home internet connections use a dynamic IP address. This means:

• Your IP stays the same for long periods
• It can change after a modem reboot or power outage
• It is not guaranteed to stay the same forever

If you try to connect to your home node using the raw IP address, and it changes, your connection breaks. This leads people to think they need a static IP.

But they don’t.

Dynamic DNS (DDNS) Fixes the Problem

Dynamic DNS gives your home network a permanent hostname, such as:

myshack.ddns.net mycallsign.duckdns.org mynode.no-ip.org

This hostname never changes, even if your home IP does.

Your router or Raspberry Pi automatically updates the DDNS service whenever your IP changes. So instead of connecting to: 11.11.11.18
You connect to: myshack.ddns.net
And it always points to the correct IP.

DDNS Works Perfectly With DVSwitch and Home Nodes

DVSwitch, Analog_Bridge, AllStar, Pi‑Star, and other ham radio tools don’t care whether you use:

• A static IP
• A dynamic IP
• A DDNS hostname

They only care that the hostname resolves.

Port Forwarding Still Works the Same

DDNS does not replace port forwarding — it only replaces the IP address you connect to.

If your node needs ports like:

• 30001 UDP
• 30002 UDP
• 4569 UDP (AllStar)
• 62030 TCP

…you still forward those ports in your router.

But instead of connecting to your changing IP, you connect to your DDNS hostname.

DDNS Is Free, Fast, and Reliable

Popular free DDNS providers include:

• DuckDNS.org (simple, free forever)
• No-IP Free (works well, requires periodic confirmation)
• Dynu (free tier available)

Most routers support DDNS natively. If not, a Raspberry Pi can update it automatically.

When Do You Actually Need a Static IP?

Only in rare cases:

• You’re hosting a large public reflector
• You need reverse DNS (PTR records)
• Your ISP blocks DDNS updates
• You’re running a commercial service

For 99% of ham radio home setups, DDNS is the correct solution.

Summary

• You do not need a static IP
• DDNS gives you a permanent hostname
• DVSwitch and home nodes work perfectly with DDNS
• Port forwarding still works normally
• DDNS is free and takes only a few minutes to set up

Static IPs are expensive and unnecessary for almost every ham radio use case. DDNS is the modern, simple, and reliable solution.

Absolutely — here’s a clear, practical explanation you can drop straight into your WordPress article. It explains how a DDNS client works, why it solves the “I need a static IP” myth, and exactly how to use DuckDNS on a Raspberry Pi to keep a home node or DVSwitch server reachable.

I’ll keep it clean, readable, and formatted for WordPress.

How a DDNS Client Works (and Why You Don’t Need a Static IP)

Dynamic DNS (DDNS) is the secret weapon that makes home nodes, DVSwitch servers, and remote‑access systems work without needing a static IP address. The idea is simple: instead of connecting to your home’s changing IP address, you connect to a permanent hostname that always points to your current IP.

A DDNS client is the small program that keeps that hostname updated.

What the DDNS Client Actually Does

A DDNS client (like the one from DuckDNS) runs on your Raspberry Pi or router and performs three simple jobs:

1. Detect your current public IP

Your Pi asks an external service:

• “What is my public IP right now?”

This is usually done by checking:

https://api.ipify.org

or DuckDNS’s own IP check.

2. Compare it to the last known IP

If the IP hasn’t changed, nothing happens.

If it has changed (after a reboot, power outage, ISP refresh, etc.), then:

3. Update your DDNS hostname

The client sends a secure update request to DuckDNS:

https://www.duckdns.org/update?domains=YOURDOMAIN&token=YOURTOKEN&ip=YOURIP

DuckDNS instantly updates your hostname, so:

myshack.duckdns.org

always points to your current home IP — even if it changes.

This is why you don’t need a static IP.
Your hostname stays the same, and the DDNS client keeps it pointed at the right place.

Using DuckDNS on a Raspberry Pi (Simple Setup)

DuckDNS is one of the easiest DDNS services to use, and it’s completely free.
Here’s how to set it up on your Pi.

1. Create your DuckDNS domain

Go to:

Sign in with:

• Google
• GitHub
• Twitter
• Reddit

Choose a domain name, for example:

myshack

Your hostname becomes:

myshack.duckdns.org

Copy your token — you’ll need it.

2. Create the DuckDNS update script on your Pi

On your Pi:

mkdir -p ~/duckdns
cd ~/duckdns
nano duck.sh

Paste this inside:

echo url="https://www.duckdns.org/update?domains=YOURDOMAIN&token=YOURTOKEN&ip=" | curl -k -o ~/duckdns/duck.log -K -

Replace:

• YOURDOMAIN with your DuckDNS name
• YOURTOKEN with your DuckDNS token

Save and exit.

3. Make the script executable

chmod 700 duck.sh

4. Add a cron job to update every 5 minutes

crontab -e

Add this line:

*/5 * * * * ~/duckdns/duck.sh >/dev/null 2>&1

This keeps your hostname updated automatically.

How This Helps DVSwitch, AllStar, and Home Nodes

Once DuckDNS is running, you no longer connect to your home IP.
You connect to your hostname:

myshack.duckdns.org

This works for:

• DVSwitch Mobile
• Analog_Bridge
• AllStarLink
• Pi‑Star
• Private dashboards
• Remote control apps
• Custom reflectors

Your Pi stays reachable even if your ISP changes your IP.

Why This Eliminates the Need for a Static IP

A static IP is only needed if:

• You’re hosting a large public reflector
• You need reverse DNS
• You’re running a commercial service

For home ham radio use:

• DDNS is free
• DDNS is automatic
• DDNS works with every node and hotspot
• DDNS solves the “changing IP” problem completely

This is why you do NOT need a static IP to run DVSwitch or a home node.

The post How to use dvswitch without a static IP address first appeared on Louisiana Nationwide.

I recently discovered a serious security issue affecting some default Hamvoip node setups. This is likely in all nodes based on that image and needs to be fixed or you need to take your nodes webpage off the internet. Close your ports.

This may explain why some users have to reboot everything after a while to stop jitter and sluggish nodes. As rebooting will give you a new IP and stop the abuse for a while.

Certain Apache proxy modules are enabled by default, which allows your node to be used as a proxy by anyone on the Internet. This can lead to massive, unintended bandwidth usage and potentially put your node at risk of abuse or blacklisting.

At this time I don’t know which nodes have this proxy enabled likely all of them. But running this script will tell you if yours is affected or not.

In our tests, we observed extreme bandwidth consumption:

Clearly, leaving these modules enabled can lead to enormous, unmonitored network usage, potentially incurring charges or throttling from your ISP.

From the nodes webserver logs
64.xxxxxxxxx- – [30/Aug/2025:08:35:17 -0500] “GET http://api.xxxxxxx.org/?format=json HTTP/1.1” 302 –
64.xxxxxxxxx- – [30/Aug/2025:08:35:19 -0500] “CONNECT www.xxxxxxxx.org:443 HTTP/1.1” 302 –

In the above example they are using the node as a proxy to download files for them. And who knows what they are doing ( hacking, spam, illegal traffic). All of which will be coming from your IP

To prevent this, I have created a safe script to fix your node:

1. change to tmp

cd /tmp

2. Download the fix script

curl -sSL -o fix_proxy.sh https://raw.githubusercontent.com/tmastersmart/gmrs_live/refs/heads/main/fix_proxy.sh

3. Inspect it before running

less fix_proxy.sh

4. Run the script

bash fix_proxy.sh

Above is on a old GMRSLive node I converted to GMRSHUB.
This fully explains most all the problems we have had for years.
Jitter, Sluggish and lockups. Ever had to reboot your router? this is why.

this is why.

What the script does:

• Scans your Apache configuration for active proxy modules.
• Comments out all potentially unsafe proxy modules.
• Displays messages showing which modules are being disabled.
• Reboots your node to apply the changes.

Why you should act immediately:

Leaving these proxy modules active exposes your node to external abuse, which can:

• Consume massive amounts of bandwidth.
• Slow down your node for legitimate GMRS use.
• Create potential legal or ISP issues if your node is used for malicious activity.

We strongly encourage all GMRS Hamvoip node operators to review their Apache configuration and run this fix script to ensure their nodes are secure.

Manual Instructions for Advanced Users

If you prefer to manually inspect and fix your node:

1. Check which proxy modules are loaded

httpd -M | grep proxy

2. Open your Apache config file

nano /etc/httpd/conf/httpd.conf

or wherever your Hamvoip Apache config is located.

3. Comment out all potentially unsafe proxy modules by adding a # at the start of lines like:

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_express_module modules/mod_proxy_express.so

4. Save and exit, then restart Apache:

systemctl restart httpd

5. Verify the modules are disabled:

httpd -M | grep proxy

You should only see modules that are intentionally enabled, and none of the risky proxy modules.

Takeaway: Act immediately. Leaving these proxy modules active exposes your node to abuse, which can consume massive amounts of bandwidth and may lead to network or legal issues.

I would be interested in finding out if you node is affected and which release it is. Please add your comment here. Perhaps some don’t have this but I suspect they all.

Final thought is after finding how bad this software is setup, even after patching I would not expose any ports to the internet if you need a status page you need a hub in the cloud or a hub running on a desktop. Don’t use a pi image for a hub. And don’t expose the port 222 as I am sure this old ssh also has problems. I am in the process of Harding the Louisiana Image since its also hamvoip based, to this and will have a new release tonight.
It would be interesting to see who activated this proxy by seeing which images have it.

Vulnerability of HAMVOIP and other pi images to Proxy Exploits

The Hamvoip system, particularly when configured default or unsecure settings exhibits notable vulnerabilities proxy functionalities. These weaknesses primarily stem from the default enabling certain Apache proxy modules, which can be exploited malicious actors to the node as an open proxy.

Exploitation of this vulnerability allows unauthorized users to leverage the node bandwidth for malicious activities such as illegal file transfers, spam distribution, or hacking attempts. Consequently, this can lead to bandwidth consumption, network slowdown, and potential blacklisting by service providersFurthermore the exposure of modules increases the risk of external abuse which may result in legal complications or of ISP policies. It is imperative operators to review configuration settings diligently and disable any unnecessary proxy modules mitigate these risks.

Proactive measures include running scripts designed to identify and comment out active proxy modules within the Apache configuration. Manual inspection and disabling of these modules are recommended for advanced users aiming to fort their against potential proxy exploits.

summary, while Hamvoip offers robust communication capabilities, its default proxy configurations pose significant security concerns necessitate immediate attention and remediation to prevent misuse and safeguard operational integrity.

The post Critical Security Update for Hamvoip proxy first appeared on Louisiana Nationwide.

Bubble packed radios are forbidden from using and do not have the 8 repeater input channels 23-30. If you have a channels with no repeater on it you can use that interference free. You may have seen other incomplete frequency charts online. Here is mine the channels are ordered by frequency showing band 1 462 on the left and band 2 467 on the right 1 making it more clear what channels are next to your node.
Example if you have walmart on ch 3 then ch 17 and ch 18 are on each side of that.

Channels 23-30 are repeater inputs that bubble packed radios do not have. They are licensed for mobiles not bases and your node is mobile so you can use them. They are not licensed only for repeater use.
In most charts they don’t list these channels or they don’t give them channel numbers and proper frequency locations on a chart.

Changing tones.

You can change your tones. You can also use digital codes. USB radios don’t have the digital codes but nodes built with actual radios do. the BF888 has both digital and analog and is programmed by chirp.

I had a lost of codes not to use but Im still searching for it..

The post STOP bubble pack Local GMRS traffic from getting into your node. first appeared on Louisiana Nationwide.

The chip was designed for another use and has unused io pins that can be accessed by USB so its perfect for a node to control a radio.

In the above drawing.
This chip has 4 unused GPIO pins. And unused button inputs VOLUP, VOLDOWN and SELECT.
It has 2 LED outputs LED0 is used and it starts out ON then flashes in operation.
LEDR is a unused mute indicator.

COS is pin48 which is a unused vol down button.
PPT is pin 13 a unused GPIO3.

The above is my schematic for modifying this card. Some use torids on the cables and I do to but there is so much noise on these wires that it needs a coil choke.

The unused audio line could be used to drive a local speaker.. And this card doesn’t have a shield around the USB so it needs a extension cable since it will move around if plugged direct into the PI.

Most people have removed the jacks in the past but you don’t need to remove them. You could actually plug into them and use them. Or just solder on top of them. They are very hard to remove and the pads under will likely break. I have found good luck inserting a small screwdriver into them to pull them off while heating. But now I really see no point in removing them. Just solder on top of them.

The easiest way to connect to COS and PPT is to use enamel wire and run it from the bottom under all the pins till it comes out at the top. Having it under the other pins holds it in place to prevent it moving while soldering and after.

For me I find its easer to strap it to a project board and place all my parts on that board so I can use normal sized parts and not the chip parts seen online.
If you need some of these and cant do it yourself I will do it for you let me know.
Im going to make up some more and look for a final photo soon.

I Use glasses to do all the work not a microscope, These are all over amazon.

The post Modifying CM108 For GMRS/Alstar nodes first appeared on Louisiana Nationwide.

Just get yourself a raspberry pi3 doesn’t matter if its a A or a B

A PI 3 A has no lan port and only 1 usb port and is smaller it requires a smaller case. They make great nodes and cost less. Since they only have 1 usb port you need a USB hub to connect a keyboard and a sound card. However for a DVSWITCH node the USB port wont even be used.

A PI3B and 3B+ has 2 USB ports and a LAN jack.

And you need a good Memory card. WARNING the cheep cards are often fake memory, Be sure you use a name brand card in a clamshell not lose cards. https://www.makeuseof.com/tag/how-to-spot-fake-microsd-card/ You also need to scan the memory cards with the fake memory card scanner after you buy them to make sure they are real and you can return them under the return window. A fake memory card will lie about its size and overwrite old files to simulate a large card. They are designed to fail after the Amazon return window closes. This scam works for cameras as you still see your old photos you just cant load them. Its disaster for a pi because it erases the OS as it fills up. It will also corrupt if you reboot because the fake os in the card will crash. Most of the reported card crashes on nodes are due to fake cards.

You need to signup for node numbers and enter them into the pi

Download from GMRS LIve the image connect a monitor and a keyboard and boot up the PI enter your node numbers.
To setup for DV Switch install my node manager as follows.

Drop to a shell and type

cd /tmp/
wget https://raw.githubusercontent.com/tmastersmart/gmrs_live/main/install.php
php install.php

Using the above menu Install Supermon and DVswitch one click installs.
This software is subject to change and the newer version will include a GMRS version of supermon.

he software will give you your DV switch settings to enter in your phone. Remember you should not enter your IP address use the Dynamic dns service of gmrslive if your node is 123 enter 123.node.gmrslive.com

You will also need to open the port number on your router. All routers are different so you will have to looks this up for your router. The PI will also need a static IP that wont change you do this in you router by finding your PI and reserving the IP for it.

IF you have questions post them here. Or if you need help. If you live in Louisiana I will build you one for free if you provide the parts.

Update there is now a small DVSWITCH only installer. Here

cd /tmp
wget https://raw.githubusercontent.com/tmastersmart/gmrs_live/main/install_dvswitch.php
php install_dvswitch.php

The post GMRS node for DV switch Under $50 first appeared on Louisiana Nationwide.

Drop to a shell and type

cd /etc/asterisk/local/
 

wget https://raw.githubusercontent.com/tmastersmart/gmrs_live/main/install.php

php install.php

follow install prompts and See instructions here

Once installed you can edit ID settings from the command line or from the webinterface.

You need to install the GMRS supermon interface to get the web setup screen,

The post Using node manager to set Morse and Voice IDS first appeared on Louisiana Nationwide.

The post GMRSKurvey 10min node setup first appeared on Louisiana Nationwide.

The post GMRS- 10 MINUTE NODE SETUP MADE EASY first appeared on Louisiana Nationwide.

The post GMRS 4-LINE RADIO NODE SETUP first appeared on Louisiana Nationwide.

*3<node#> example *31195 connects but wont reconnect if dropped.
*73<node#> example *731195 connects and will auto reconnect if dropped
*1<node#> example a node is connected to you node 33 and you want to force it to disconnect type *133

Remember never connect to 2 systems at the same time this is called bridging. Always send *76 before connecting to a new hub.

The post DTMF commands for Allstar Nodes first appeared on Louisiana Nationwide.