EchoLink is now LIVE on the Main Hub!

You can now join the system from anywhere using EchoLink. Just connect to:

KJ5MZL‑L

This links you straight into the Main AllStar Hub, the DVSwitch server, and TGIF DMR Talkgroup 28100 — all fully bridged together.

Perfect for mobile, HT, travel, or quick check‑ins. Jump in and say hello.

The post Echolink server is now online for Louisiana Nationwide first appeared on Louisiana Nationwide.

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.

Shortly before you took office, the FCC stopped GMRS repeaters from being linked, even though this had been allowed for many years. Internet linking gave families a way to talk to each other across cities and states, and during hurricanes it provided vital backup when phones were down.

We contacted Congress but were ignored. I submitted comments directly to the FCC:

• https://www.fcc.gov/ecfs/document/10802544719909/1
• https://www.fcc.gov/ecfs/document/1042511135974/1
• https://www.fcc.gov/ecfs/document/10426037020584/1

We also organized a petition:

• https://www.lagmrs.com/wp/2024/08/20/petition-to-congress-to-restore-gmrs-linking/

The FCC’s response was to post on their GMRS page that repeater linking is “not in the public interest” and might cause interference. But how does a linked repeater cause more interference than one that is not linked? No interference study has ever been done, and GMRS users have already shown that linking works safely and effectively.

Unlike amateur (ham) radio, GMRS allows an entire family to use the system under one license. There is no good reason GMRS users should be blocked from linking repeaters, especially when this restriction undermines family communication and disaster response.

I ask for your help in reversing this political decision and ending the FCC’s unfair bias against GMRS users.

Respectfully,

The post Letter to the president on GMRS linking. 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.

GMRShub – A GMRS Radio Linking Project

GMRShub is all about freedom:

1. Freedom to Communicate:
   • On GMRS hub, you can talk to whom you want to talk. There are no restrictions or limitations on who you can connect with.
   • Unlike some other networks, GMRS hub doesn’t impose passwords or barriers. It’s a community-driven effort where members enjoy open communication.
2. Freedom to Move Around the Network:
   • Feel like changing things up? No problem! GMRS hub allows you to move around the network as you please.
   • Whether you’re exploring new areas or just want a change of scenery, GMRS hub gives you the freedom to roam.
3. Freedom to Use Your Preferred Equipment:
   • Use the radio equipment you love. GMRS hub doesn’t dictate what gear you should use.
   • Whether it’s handheld radios, mobile units, or repeaters, the choice is yours.
4. Freedom to Add Features:
   • Want to enhance your experience? GMRS hub lets you add features without limitations.
   • Whether it’s linking to other systems, integrating weather updates, or experimenting with new functionalities, you’re free to explore.
5. Community-Driven and Supportive:
   • The users on GMRS hub are fantastic. They help each other out, answer questions, and contribute to making the network better.
   • It’s a collaborative effort that keeps growing and improving over time.
6. Create Your Own Thing:
   • GMRS Live encourages creativity. If you have ideas or want to try something different, this is the place.
   • Whether you’re an experienced user or just starting out, GMRS hub welcomes you.
7. No Bad Attitudes:
   • Say goodbye to negative vibes. GMRS hub fosters a positive environment where everyone can enjoy themselves.
8. How to Get Node Numbers:
   • Visit the GMRS HUB website to learn more and request your node number.
   • Do not request a node number unless you have a node or are setting on up. Node numbers are not for DV switch or your phone.
   • Explore the community, connect with fellow enthusiasts, and enjoy the freedom of GMRS Live!

Remember, GMRS Live is more than just a network—it’s a community of radio enthusiasts who value freedom and collaboration. So whether you’re a seasoned GMRS user or a curious newcomer, give Louisiana Nationwide a try!

The post GMRS HUB and Louisiana Nationwide A GMRS Radio Linking Project first appeared on Louisiana Nationwide.

Louisiana Nationwide is a community-driven GMRS network that connects users across the country — without relying on traditional repeaters. Instead, we use a custom digital linking system that allows GMRS radios, hotspots, and gateways to communicate directly over the internet, creating a seamless and reliable experience for licensed GMRS operators.

Whether you’re in rural Louisiana or across the country, you can join the conversation and stay connected with others — no repeater coverage required. Perfect for families, travelers, and off-grid communication enthusiasts, the Louisiana Nationwide system brings the GMRS community closer than ever.

The post Louisiana Nationwide GMRS first appeared on Louisiana Nationwide.

DVSWITCH LINK

The post DVswitch access first appeared on Louisiana Nationwide.

Download the Best Louisiana Node Image for GMRS

Louisiana GMRS Image

The new node image is ready,. Still need people to test this if you see any bugs please let me know.

The post Louisiana GMRS Node Image Download. Improved updated ARCH LINIX first appeared on Louisiana Nationwide.

Brendan Carr: A Veteran Leader for the FCC

President-elect Donald Trump’s decision to appoint Brendan Carr as the head of the Federal Communications Commission (FCC) signals a strategic focus on fostering innovation and reducing regulatory burdens in the telecommunications and broadcasting industries. Carr, a seasoned Republican FCC commissioner, has extensive experience navigating the complexities of telecommunications law and policy. His leadership reflects a commitment to promoting investment in broadband infrastructure, ensuring regulatory efficiency, and advancing U.S. leadership in communications technologies.

Professional Background and Experience

Brendan Carr joined the FCC in 2012 and has served in various capacities, including as the General Counsel of the agency. His deep understanding of communications law is rooted in his time as a telecommunications attorney at Wiley Rein LLP and his service as an advisor to former FCC Commissioner Ajit Pai. In 2017, Carr was confirmed as an FCC commissioner, where he became an outspoken advocate for modernizing the FCC’s regulatory framework to keep pace with the rapidly evolving digital economy.

Carr’s tenure at the FCC has been marked by a focus on expanding broadband access to underserved areas, a crucial component of his “5G Fast Plan.” This initiative has streamlined the deployment of next-generation wireless networks, positioning the United States as a leader in global 5G deployment. His work emphasizes reducing bureaucratic barriers that delay infrastructure projects, particularly in rural communities where connectivity gaps persist.

Policy Focus and Vision

Carr’s regulatory philosophy aligns with the Trump administration’s broader agenda of reducing government oversight to stimulate economic growth. His leadership at the FCC is expected to prioritize:

1. Broadband Expansion: Carr has consistently advocated for closing the digital divide by expanding high-speed internet access to rural and underserved areas. His policies aim to encourage private investment and streamline permitting processes for broadband infrastructure.
2. Deregulation: Carr supports a lighter regulatory touch, particularly for emerging technologies. He has argued that overly stringent rules can stifle innovation and delay the deployment of transformative technologies.
3. 5G Leadership: Under Carr’s guidance, the FCC has worked to accelerate the deployment of 5G networks. By reducing the costs and timelines associated with infrastructure deployment, he aims to solidify the U.S.’s competitive edge in the global technology landscape.
4. Consumer Protection: While advocating for deregulation, Carr has also emphasized the importance of protecting consumers, particularly in areas like robocalls and privacy. He has supported measures to hold bad actors accountable without imposing excessive burdens on legitimate businesses.

Advocacy for GMRS Repeater Linking

Brendan Carr’s appointment as FCC Chair presents a unique opportunity for the General Mobile Radio Service (GMRS) community to address critical issues. Recent rule changes have restricted repeater linking, which has traditionally been an essential feature for GMRS operators to extend communication range and foster connectivity during emergencies and routine use.

As a proponent of deregulation and industry-driven solutions, Carr may be open to reconsidering these limitations. It is crucial for GMRS users, organizations, and stakeholders to contact him after he assumes office to advocate for:

• Restoring Repeater Linking: Allowing repeater linking to promote interoperability and enhance the functionality of GMRS networks.
• Revisiting Recent Rules: Urging the FCC to remove restrictions that hinder the operational flexibility of GMRS systems.
• Highlighting Community Benefits: Emphasizing how repeater linking supports public safety, disaster preparedness, and community engagement.

A coordinated effort by the GMRS community to voice concerns and provide evidence of the benefits of repeater linking can create a compelling case for revising these rules. Brendan Carr’s leadership provides a pivotal moment to influence policies that affect GMRS operations and ensure they align with the needs of the community.

The post New FCC Commissioner first appeared on Louisiana Nationwide.

The post Podcast Stats first appeared on Louisiana Nationwide.