/rss20.xml">

Fedora People

PHP version 8.2.24RC1 and 8.3.12RC1

Posted by Remi Collet on 2024-09-13 08:59:00 UTC

Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for a parallel installation, the perfect solution for such tests, and also as base packages.

RPMs of PHP version 8.3.12RC1 are available

  • as base packages in the remi-modular-test for Fedora 39-41 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

RPMs of PHP version 8.2.24RC1 are available

  • as base packages in the remi-modular-test for Fedora 39-41 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

emblem-notice-24.png The packages are available for x86_64 and aarch64.

emblem-notice-24.pngPHP version 8.1 is now in security mode only, so no more RC will be released.

emblem-notice-24.pngInstallation: follow the wizard instructions.

emblem-notice-24.png Announcements:

Parallel installation of version 8.3 as Software Collection:

yum --enablerepo=remi-test install php83

Parallel installation of version 8.2 as Software Collection:

yum --enablerepo=remi-test install php82

Update of system version 8.3:

dnf module switch-to php:remi-8.3
dnf --enablerepo=remi-modular-test update php\*

Update of system version 8.2:

dnf module switch-to php:remi-8.2
dnf --enablerepo=remi-modular-test update php\*

emblem-notice-24.png Notice:

  • version 8.3.11RC1 is also in Fedora rawhide for QA
  • version 8.4.0beta5 is also available in the repository
  • EL-9 packages are built using RHEL-9.4
  • EL-8 packages are built using RHEL-8.10
  • oci8 extension uses the RPM of the Oracle Instant Client version 23.5 on x86_64 or 19.24 on aarch64
  • intl extension uses libicu 74.2
  • RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
  • versions 8.2.24 and 8.3.12 are planed for September 26th, in 2 weeks.

Software Collections (php82, php83)

Base packages (php)

🚀 Convert Your 433 MHz Heltec Wireless Tracker into a 433 MHz LoRa APRS Tracker

Posted by Piju 9M2PJU on 2024-09-13 12:51:23 UTC

In this guide, we’ll walk you through the steps to convert a 433 MHz Heltec Wireless Tracker into a 433 MHz LoRa APRS (Automatic Packet Reporting System) tracker. All you need is a Heltec Wireless Tracker, a Windows computer, Visual Studio Code, and a few additional tools. Let’s get started!

🛠 Prerequisites

  • Heltec Wireless Tracker: Comes with a plastic case and an antenna.
  • Computer: A Windows machine is needed.
  • USB Type-C Cable: To connect the Heltec Wireless Tracker to your computer.

💻 Step 1: Set Up Your Computer

  1. Download and Install Visual Studio Code:
    Visit the Visual Studio Code website, download the installer for Windows, and follow the instructions to install it.
  2. Install PlatformIO Extension for Visual Studio Code:
    Open Visual Studio Code, click on the square icon in the sidebar (or press Ctrl+Shift+X), search for “PlatformIO IDE,” and install the extension.

🔧 Step 2: Install the Heltec Wireless Tracker Driver

  • Head over to the Heltec website and navigate to the Support section under “Resources Download.”
  • Download the CP210x Universal Driver for your Heltec Wireless Tracker.
  • Follow the on-screen instructions to install the driver on your computer.

📦 Step 3: Download and Prepare the LoRa APRS Tracker Code

  • Go to the LoRa APRS Tracker GitHub repository and download the code as a ZIP file.
  • Extract the contents of the ZIP file to a folder on your computer.
  • Open Visual Studio Code, navigate to File > Open Folder…, and select the folder where you extracted the LoRa APRS Tracker code.

📝 Step 4: Configure the Tracker

  • In Visual Studio Code, open the data folder within the LoRa APRS Tracker project.
  • Find and open the tracker_config.json file.
  • Edit the file to include your specific details, such as callsign, SSID, and other necessary parameters.

⚙ Step 5: Update the PlatformIO Environment

  • Open the platformio.ini file located in the root directory of the LoRa APRS Tracker project.
  • Make sure it contains the following line to set the correct environment for the Heltec Wireless Tracker:
  [platformio]
  default_envs = heltec_wireless_tracker

🛠 Step 6: Build and Upload the Firmware

  1. Build the Firmware:
    Press Ctrl+Alt+B in Visual Studio Code to compile the firmware for your Heltec Wireless Tracker.
  2. Connect the Heltec Wireless Tracker:
    Use a USB Type-C cable to connect your Heltec Wireless Tracker to the computer. While connecting, hold down the USER button on the device to enter upload mode.
  3. Upload the Firmware:
    Press Ctrl+Alt+U in Visual Studio Code to upload the firmware to your device.

📂 Step 7: Upload the Filesystem Image

  • Once the firmware upload is successful, click on the PlatformIO icon in the Visual Studio Code sidebar.
  • In the PlatformIO tab, locate “Heltec Wireless Tracker.”
  • Click on Platform -> Upload Filesystem Image to upload the required files to the device.

🎉 Step 8: Complete the Setup

Congratulations! 🎊 Your 433 MHz Heltec Wireless Tracker is now a fully functioning 433 MHz LoRa APRS tracker. You’re all set to start using it!

Enjoy your new LoRa APRS tracker and happy tracking! 📡

image-1 🚀 Convert Your 433 MHz Heltec Wireless Tracker into a 433 MHz LoRa APRS Tracker

The post 🚀 Convert Your 433 MHz Heltec Wireless Tracker into a 433 MHz LoRa APRS Tracker appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

Infra and RelEng Update – Week 37 2024

Posted by Fedora Community Blog on 2024-09-13 10:00:00 UTC

This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contains updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.

We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

Week: 09 September – 13 September 2024

I&R infographic

Infrastructure & Release Engineering

The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues

Fedora Infra

CentOS Infra including CentOS CI

Release Engineering

CPE Initiatives

EPEL

Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux (SL) and Oracle Linux (OL).

Updates

Community Design

CPE has few members that are working as part of Community Design Team. This team is working on anything related to design in Fedora Community.

Updates

  • Fedora:
    • [Closed] DEI Team Report ComBlog Graphic Revamp #42
    • [Closed] FCOREOS Swag #160
    • SWAG: Fedora Websites & Apps Revamp Community Initiative #53
  • Podman Desktop:
    • #2363: Mockup for extension install web page
    • #8338: UX: Mockups for Docker Compatibility page
  • Other:
    • Posted initial ideas for Ramalama logo #166

ARC Investigations

The ARC (which is a subset of the CPE team) investigates possible initiatives that CPE might take on.

Updates

  • Dist Git Move
    • User stories are updated on the website – We have 79 of them now
    • Work in progress – Seeding of GitLab and Forgejo for workflow testing

If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.

The post Infra and RelEng Update – Week 37 2024 appeared first on Fedora Community Blog.

New Fedora shirts available at HELLOTUX

Posted by Fedora Magazine on 2024-09-13 08:00:00 UTC

We’ve upgraded the embroidered Fedora shirt collection with dark blue and white T-shirts and polo shirts. There’s a coupon code below, read onward for more details.

Half of the Fedora backpacks were for free

After delivering more than 800 embroidered Fedora garments to more than 50 countries, we’d like to share some numbers about our Fedora shirt project.

Our most popular items are of course shirts: 266 T-shirts, and 267 polo shirts were sold and there are 30 Fedora laptop backpacks around the world. Half of them were gifts from us to people ordering four or more other items (shirts or sweatshirts). You can still get a backpack too.

The most popular sizes are large (27%) and extra large (26%), followed by medium (19%) and 2XL (16%).

Since we ship worldwide, our Fedora garments are in 53 countries. Most of them in the United States (33%), Germany (14%), United Kingdom (5%) and France (5%). But can you find Moldova, Macao, Ghana or Réunion on the map? Fedora users show their commitment to our favorite operating system with Fedora shirts in these countries and territories too.

Currently in the HELLOTUX Fedora collection you can find T-shirts, polo shirts, a jacket, a hoodie and a laptop backpack. All of these are embroidered with the Fedora logo.

The coupon code

You can get a $5 discount on every Fedora item with the coupon code FEDORA5, and there is the Fedora laptop backpack promo as well.

Order now

Order directly from the HELLOTUX website.

Understanding APRS Wide Path Configurations: From Wide1-1 to Wide3-3

Posted by Piju 9M2PJU on 2024-09-13 06:08:06 UTC

Amateur radio enthusiasts and emergency communication specialists often rely on the Automatic Packet Reporting System (APRS) for position reporting and short messaging. One of the key features that make APRS so effective is its ability to relay messages through multiple digipeaters using “wide path” configurations. In this post, we’ll explore the various wide path settings from Wide1-1 to Wide3-3 and understand their implications for your APRS communications.

What is a Wide Path?

Before diving into specific configurations, let’s clarify what a “wide path” means in APRS:

  • A wide path is a routing mechanism that allows APRS packets to be relayed through multiple digipeaters.
  • The format “WIDEn-N” indicates how many hops (n) a packet can take, and how many hops remain (N).
  • Each time a digipeater relays the packet, it decreases the N value by 1.

Now, let’s break down each wide path configuration:

Wide1-1

  • Hops: 1
  • Usage: Local area communications
  • Description: This is the most basic wide path. Your packet will be relayed only once by the first compatible digipeater that hears it.
  • Best for: Urban areas with good digipeater coverage or direct communication with nearby stations.

Wide2-1

  • Hops: Up to 2
  • Usage: Extended local area
  • Description: Your packet can be relayed twice. After the first relay, it becomes Wide2-0, allowing one more hop.
  • Best for: Suburban areas or situations where you need slightly extended range beyond Wide1-1.

Wide2-2

  • Hops: Up to 2
  • Usage: Regional communications
  • Description: Similar to Wide2-1, but allows for two full hops. After the first relay, it becomes Wide2-1, permitting one more full-strength hop.
  • Best for: Covering larger areas or reaching more distant digipeaters.

Wide3-1

  • Hops: Up to 3
  • Usage: Extended regional communications
  • Description: Allows for up to three hops. After two relays, it becomes Wide3-0, permitting one final hop.
  • Best for: Reaching distant stations or filling gaps in digipeater coverage.

Wide3-2

  • Hops: Up to 3
  • Usage: Wide area communications
  • Description: Permits three hops, with the last two at full strength. After the first relay, it becomes Wide3-1.
  • Best for: Covering very large areas or ensuring your signal reaches key digipeaters.

Wide3-3

  • Hops: 3
  • Usage: Maximum coverage
  • Description: Allows for three full-strength hops. Each relay reduces it (Wide3-2, then Wide3-1, then Wide3-0).
  • Best for: Maximum theoretical coverage, but use with caution to avoid network congestion.

Choosing the Right Wide Path

Selecting the appropriate wide path depends on several factors:

  1. Local network topology: Understand the digipeater coverage in your area.
  2. Purpose of transmission: Emergency communications might justify wider paths.
  3. Network congestion: Using wider paths unnecessarily can congest the network.
  4. Power and antenna: Consider your station’s effective radiated power.

Best Practices

  1. Start with the minimum path needed (often Wide1-1) and increase only if necessary.
  2. Use Wide3-3 sparingly to avoid network congestion.
  3. Consider using specific digipeater callsigns for more efficient routing in well-known networks.
  4. Regularly review and adjust your settings based on local conditions and feedback.

Conclusion

Understanding APRS wide path configurations is crucial for effective and responsible use of the APRS network. By choosing the right path for your situation, you can ensure your messages reach their intended audience without unnecessarily burdening the system. Remember, the goal is efficient communication, not maximum coverage at all times.

Happy APRSing!

The post Understanding APRS Wide Path Configurations: From Wide1-1 to Wide3-3 appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

The syslog-ng Insider 2024-09: documentation; TRANSPORT macro; rolling RPMs

Posted by Peter Czanik on 2024-09-11 11:13:13 UTC

The September syslog-ng newsletter is now on-line:

  • You can also contribute to the syslog-ng OSE documentation
  • The $TRANSPORT macro of syslog-ng
  • Rolling RPM platforms added to the syslog-ng package build system

It is available at https://www.syslog-ng.com/community/b/blog/posts/the-syslog-ng-insider-2024-09-documentation-transport-macro-rolling-rpms

syslog-ng logo

System insights with command line tools: lsof and lsblk

Posted by Fedora Magazine on 2024-09-11 08:00:00 UTC

In our ongoing series on Linux system insights, we have a look into essential command-line utilities that provide information about the system’s hardware and status. Following our previous discussions on lscpu, lsusb, dmidecode and lspci, we now turn our attention to lsof and lsblk. These tools are particularly useful for investigating open files, active network connections, and mounted block devices on your Fedora Linux system.

Exploring open files with lsof

lsof (list open files) is a powerful command-line tool. Since almost everything in Linux is treated as a file, lsof provides detailed insight into many parts of your system by listing what files are being used, which processes are accessing them, and even which network ports are open (see e.g. Wikipedia on Network socket for more information).

Basic usage

To start with, execute the basic lsof command to get an overview of the system’s open files:

$ sudo lsof

sudo was used for extended privileges. This is needed to get information about files not opened by processes started by your user. The command outputs a lot of information which can be overwhelming. We are going to narrow down the output to specific information about some common use cases in the following examples.

Example 1: Finding open files by user or process

To identify which files a specific user or process has open, lsof can be very helpful.

To list all files opened by a specific user:

$ sudo lsof -u <username>

This will return a list of open files owned by the given user. For example:

$ sudo lsof -u johndoe

You’ll see details such as the process ID (PID), the file descriptor, the type of file, and the file’s path.

To filter by process, use the -p flag:

$ lsof -p <PID>

This is particularly useful for troubleshooting issues related to specific processes or when you need to check which files a service is holding open. Use sudo if the process is not owned by your user.

Example output:

$ lsof -p 873648
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
bash 873648 user cwd DIR 0,39 8666 257 /home/user
bash 873648 user rtd DIR 0,35 158 256 /
bash 873648 user txt REG 0,35 1443376 12841259 /usr/bin/bash
bash 873648 user mem REG 0,33 12841259 /usr/bin/bash (path dev=0,35)
bash 873648 user mem REG 0,33 14055145 /usr/lib/locale/locale-archive (path dev=0,35)
bash 873648 user mem REG 0,33 14055914 /usr/lib64/libc.so.6 (path dev=0,35)
bash 873648 user mem REG 0,33 13309071 /usr/lib64/libtinfo.so.6.4 (path dev=0,35)
bash 873648 user mem REG 0,33 14059926 /usr/lib64/gconv/gconv-modules.cache (path dev=0,35)
bash 873648 user mem REG 0,33 14055911 /usr/lib64/ld-linux-x86-64.so.2 (path dev=0,35)
bash 873648 user 0u CHR 136,3 0t0 6 /dev/pts/3
bash 873648 user 1u CHR 136,3 0t0 6 /dev/pts/3
bash 873648 user 2u CHR 136,3 0t0 6 /dev/pts/3
bash 873648 user 255u CHR 136,3 0t0 6 /dev/pts/3

Example 2: identifying open network connections via sockets

With its ability to list network connections, lsof also becomes a handy tool for diagnosing network-related issues as it is usually even available on hardened, minimal systems.

To display all open network connections (TCP/UDP sockets), run:

$ sudo lsof -i

This will list active Internet connections along with the associated protocol, port, and process details.

You can filter for specific protocols (like TCP or UDP), include or exclude IPv4 and v6 and combine several values (the example section of man lsof provides a lot of useful information, including negation):

$ sudo lsof -i tcp
$ sudo lsof -i udp
$ sudo lsof -i 4tcp
$ sudo lsof -i 6tcp
$ sudo lsof -i 4tcp@example.com

For connections associated with a particular port:

$ sudo lsof -i :<port_number>

For example, to list connections to port 22 (SSH):

$ sudo lsof -i :22
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sshd 904379 root 3u IPv4 5622530 0t0 TCP *:ssh (LISTEN)
sshd 904379 root 4u IPv6 5622532 0t0 TCP *:ssh (LISTEN)

This information can be critical for identifying unauthorized connections or simply monitoring network activity on a system for debugging.

Investigating block devices with lsblk

Another useful tool is lsblk, which displays information about all available block devices on your system. Block devices include hard drives, SSDs, and USB storage. This command provides a tree-like view, helping you understand the relationships between partitions, devices, and their mount points.

Basic usage

Running lsblk without any options provides a clean hierarchical structure of the block devices:

$ lsblk

This shows all block devices in a tree structure, including their size, type (disk, partition), and mount point (if applicable).

Examples

For a deeper look into the file systems on your block devices, use the -f flag:

$ lsblk -f

This will display not just the block devices, but also details about the file systems on each partition, including the type (e.g., ext4, vfat, swap), the UUID, and the current mount points.

If you want less information about the devices themselves (without showing partitions or mount points), the -d option is useful:

$ lsblk -d

There is also a -J or –json option. If used, the command outputs the information in JSON format. This provides a structured view that is particularly useful for scripting and automation.

Example outputs from my laptop (some long information like UUIDs stripped for readability):

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 0B 0 disk
sdb 8:16 1 0B 0 disk
sdc 8:32 1 0B 0 disk
zram0 252:0 0 8G 0 disk [SWAP]
nvme0n1 259:0 0 931,5G 0 disk
├─nvme0n1p1 259:1 0 600M 0 part /boot/efi
├─nvme0n1p2 259:2 0 1G 0 part /boot
└─nvme0n1p3 259:3 0 929,9G 0 part
└─luks-84257c20[...] 253:0 0 929,9G 0 crypt /home


$ lsblk -d
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 0B 0 disk
sdb 8:16 1 0B 0 disk
sdc 8:32 1 0B 0 disk
zram0 252:0 0 8G 0 disk [SWAP]
nvme0n1 259:0 0 931,5G 0 disk

$ lsblk -f
NAME FSTYPE [...]LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
sdb
sdc
zram0 [SWAP]
nvme0n1
├─nvme0n1p1 vfat 4C5B-4355 579,7M 3% /boot/efi
├─nvme0n1p2 ext4 30eff827[...] 605M 31% /boot
└─nvme0n1p3 crypto_LUKS 84257c20[...]
└─luks-84257[...] btrfs fe[...] 666f9d6f[...] 303,1G 67% /home
/

$ lsblk -f -J
{
"blockdevices": [
[...],{
"name": "nvme0n1",
"fstype": null,
"fsver": null,
"label": null,
"uuid": null,
"fsavail": null,
"fsuse%": null,
"mountpoints": [
null
],
"children": [
{
"name": "nvme0n1p1",
"fstype": "vfat",
"fsver": "FAT32",
"label": null,
"uuid": "4C5B-4355",
"fsavail": "579,7M",
"fsuse%": "3%",
"mountpoints": [
"/boot/efi"
]
},{
"name": "nvme0n1p2",
"fstype": "ext4",
"fsver": "1.0",
"label": null,
"uuid": "30eff827-[...]",
"fsavail": "605M",
"fsuse%": "31%",
"mountpoints": [
"/boot"
]
},{
"name": "nvme0n1p3",
"fstype": "crypto_LUKS",
"fsver": "2",
"label": null,
"uuid": "84257c20-[...]",
"fsavail": null,
"fsuse%": null,
"mountpoints": [
null
],
"children": [
{
"name": "luks-[...]",
"fstype": "btrfs",
"fsver": null,
"label": "fedora_localhost-live",
"uuid": "666f9d6f-[...]",
"fsavail": "303,1G",
"fsuse%": "67%",
"mountpoints": [
"/home", "/"
]
}
]
}
]
}
]
}

Conclusion

The lsof and lsblk commands are providing insights into file usage, network activity, and block device structures. Whether you’re tracking down open file handles, diagnosing network connections, or reviewing storage devices; whether you’re troubleshooting, optimizing, or simply curious; these tools provide valuable data that can help you better understand and manage your Fedora Linux environment. See you next time when we will have a look at more useful listing and information command line tools and how to use them.

Using Ubuntu as Your Ham Shack Operating System: A Comprehensive Guide for Amateur Radio Enthusiasts

Posted by Piju 9M2PJU on 2024-09-10 17:16:54 UTC

Amateur radio, or “ham” radio, is a hobby that combines electronics, communication technology, and experimentation. It’s a perfect blend for those who enjoy tinkering with both hardware and software. While Windows and macOS are popular choices for many hams, Linux distributions, especially Ubuntu, offer a robust, flexible, and cost-effective alternative for building a ham shack. In this blog post, we’ll explore why Ubuntu is a great choice for ham radio operators and provide a step-by-step guide on setting up a ham shack operating system using Ubuntu.

Why Choose Ubuntu for Your Ham Shack?

Ubuntu, a Debian-based Linux distribution, is known for its user-friendly interface, vast repository of software, and strong community support. Here are a few reasons why Ubuntu is a great choice for amateur radio enthusiasts:

  1. Open Source and Free: Ubuntu is free to download, install, and use. Being open-source means you have full control over the operating system, including the ability to tweak it to suit your specific needs.
  2. Stability and Security: Ubuntu is known for its stability and security. The Linux kernel is less prone to viruses and malware compared to other operating systems, which is crucial when running a reliable ham shack.
  3. Vast Software Repository: Ubuntu has a huge software repository, including a wide variety of applications specifically designed for amateur radio. This makes it easy to find and install the tools you need.
  4. Community Support: Ubuntu has a large, active community. If you run into problems or need help setting up a particular piece of software, you’re likely to find solutions in forums, user groups, or dedicated ham radio communities.
  5. Customization: Ubuntu allows for extensive customization. You can strip down the OS to its bare essentials to maximize performance or build a fully-featured desktop environment with all the tools and utilities you need.

Getting Started: Installing Ubuntu

Step 1: Download Ubuntu

Visit the official Ubuntu website to download the latest version of Ubuntu. You can choose between the Long-Term Support (LTS) version, which is stable and receives updates for five years, or the regular release, which includes newer features but is only supported for nine months.

Step 2: Create a Bootable USB Drive

Once you have downloaded the Ubuntu ISO file, create a bootable USB drive. You can use tools like Rufus (Windows) or Etcher (Linux/macOS) to make a bootable USB stick.

Step 3: Install Ubuntu

Boot your computer from the USB drive and follow the on-screen instructions to install Ubuntu. You can choose to install Ubuntu alongside your existing operating system or as a standalone OS.

Essential Ham Radio Software for Ubuntu

Now that you have Ubuntu installed, it’s time to set up your ham shack environment. Here are some essential ham radio software packages you should consider:

1. FLDigi

FLDigi (Fast Light Digital Modem Application) is a popular digital mode software suite for Linux, Windows, and macOS. It supports a wide range of digital modes like PSK31, RTTY, MFSK, and more. FLDigi integrates well with other software, making it an essential part of any ham shack setup.

  • Installation: You can install FLDigi directly from the Ubuntu repository using the following command:
  sudo apt-get install fldigi

2. WSJT-X

WSJT-X is a software suite designed for weak-signal digital communication by K1JT. It supports FT8, JT65, JT9, and other popular digital modes. The software is user-friendly and widely used in the ham radio community.

  • Installation: Download the latest WSJT-X package from the official website and follow the installation instructions provided.

3. CQRLOG

CQRLOG is an advanced logging program for Linux that integrates seamlessly with ham radio applications. It supports real-time logging, QSO records, and features like LoTW and eQSL synchronization.

  • Installation: Install CQRLOG from the Ubuntu repository:
  sudo apt-get install cqrlog

4. GPredict

GPredict is a satellite tracking application that helps you monitor satellite passes in real-time. It’s a must-have for any ham operator interested in satellite communication.

  • Installation: Install GPredict using the following command:
  sudo apt-get install gpredict

5. Hamlib

Hamlib provides a standardized API for controlling radios and other shack equipment. Many ham radio applications rely on Hamlib to interface with various radios. It’s an essential library for integrating different hardware with your Ubuntu system.

  • Installation: Install Hamlib via the terminal:
  sudo apt-get install libhamlib-utils

Setting Up Rig Control and CAT Interfaces

One of the key aspects of setting up a ham shack on Ubuntu is ensuring seamless communication between your computer and radio equipment. This usually involves setting up rig control and Computer-Aided Transceiver (CAT) interfaces. The Hamlib library mentioned earlier is crucial for this.

  • Rig Control Setup: Use rigctl (part of Hamlib) to set up rig control. You may need to specify the serial port or USB port where your rig is connected:
  rigctl -m <radio_model_number> -r /dev/ttyUSB0 -s <baud_rate>
  • Testing the Interface: Once set up, test the interface to ensure commands from the computer are correctly interpreted by the radio.

Customizing Ubuntu for Ham Radio Use

To optimize Ubuntu for your ham shack, consider the following:

  1. Disable Unnecessary Services: Disable services that aren’t needed to reduce system load.
  2. Optimize Audio Settings: Properly configure ALSA and PulseAudio settings to ensure clear and reliable audio communication.
  3. Set Up a Backup System: Use tools like rsync or Timeshift to set up regular backups of your log files and settings.
  4. Use Virtual Desktops: Take advantage of Ubuntu’s multiple desktops feature to separate your ham radio operations from general computing tasks.

Conclusion

Using Ubuntu as your ham shack operating system offers flexibility, stability, and a wide range of powerful software tools. Whether you’re a digital mode enthusiast, a satellite tracker, or someone who loves experimenting with different radio setups, Ubuntu provides an open, customizable platform that can meet your needs. With a little bit of setup and configuration, you’ll have a robust, reliable ham shack operating system tailored just for you.

Dive in, experiment, and enjoy the freedom that comes with using an open-source operating system like Ubuntu in your amateur radio adventures!

The post Using Ubuntu as Your Ham Shack Operating System: A Comprehensive Guide for Amateur Radio Enthusiasts appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

Setting Up Personal DNS over HTTPS (DoH) and DNS over TLS (DoT) Using Open-Source Software

Posted by Piju 9M2PJU on 2024-09-10 13:55:20 UTC

In an era where digital privacy is increasingly at risk, securing your DNS (Domain Name System) queries is crucial. Traditional DNS requests are sent in plaintext, making them vulnerable to eavesdropping and tampering. Fortunately, DNS over HTTPS (DoH) and DNS over TLS (DoT) offer encrypted channels for DNS queries, significantly enhancing your privacy and security.

In this guide, we’ll explore how to set up your own personal DNS resolver using open-source software that supports both DoH and DoT. We will cover the installation and configuration of Unbound, Caddy, Stubby, and other relevant tools to ensure your DNS traffic remains private and secure.

Understanding DoH and DoT

  • DNS over HTTPS (DoH): Encrypts DNS queries using the HTTPS protocol, making it difficult to distinguish DNS traffic from regular web traffic. This helps bypass censorship and improve privacy.
  • DNS over TLS (DoT): Encrypts DNS queries using Transport Layer Security (TLS), securing the communication channel between your device and the DNS resolver.

Both protocols prevent eavesdropping and manipulation of DNS data by external parties, such as ISPs or malicious actors.

Why Run Your Own DNS Resolver?

Running your own DNS resolver has several advantages:

  1. Enhanced Privacy: Prevent third-party DNS services from logging or selling your DNS queries.
  2. Increased Security: Protect against DNS hijacking and other DNS-related threats.
  3. Customization: Apply custom DNS filtering rules, block ads and trackers, or direct specific domains to chosen IPs.
  4. Improved Performance: Reduce latency by caching DNS responses and optimizing resolver placement.

Open-Source Software for DoH and DoT

We’ll focus on the following open-source tools to set up a personal DNS resolver with support for DoH and DoT:

  1. Unbound: A high-performance DNS resolver that supports DNS over TLS (DoT).
  2. Caddy: A modern web server with native support for DNS over HTTPS (DoH).
  3. Stubby: A DNS privacy daemon designed for DNS over TLS (DoT).
  4. Knot Resolver: A versatile DNS resolver supporting both DoH and DoT.
  5. CoreDNS: A DNS server with modular support for DoH and DoT via plugins.
  6. DNSDist: A DNS load balancer that can proxy DNS queries over HTTPS and TLS.

Protect your online privacy and enhance your security by setting up your personal DNS resolver with DNS over HTTPS (DoH) and DNS over TLS (DoT). Learn how to install and configure popular open-source tools like Unbound, Caddy, Stubby, Knot Resolver, CoreDNS, and DNSDist to secure your DNS queries.

1. Unbound: High-Performance DNS Resolver with DoT Support

Unbound is a powerful DNS resolver that supports DNS over TLS (DoT). Here’s how to install and configure it:

Install Unbound

For Debian-based systems:

sudo apt update
sudo apt install unbound

For Red Hat-based systems:

sudo yum install unbound

Configure Unbound

Edit the Unbound configuration file at /etc/unbound/unbound.conf:

server:
    interface: 0.0.0.0@853
    interface: ::0@853
    tls-service-key: "/etc/unbound/unbound_server.key"
    tls-service-pem: "/etc/unbound/unbound_server.pem"
    access-control: 127.0.0.0/8 allow
    access-control: ::1 allow
    root-hints: "/etc/unbound/root.hints"
    cache-max-ttl: 86400
    cache-min-ttl: 3600

forward-zone:
    name: "."
    forward-tls-upstream: yes
    forward-addr: 1.1.1.1@853
    forward-addr: 8.8.8.8@853

Generate TLS certificates:

openssl req -x509 -newkey rsa:4096 -keyout /etc/unbound/unbound_server.key -out /etc/unbound/unbound_server.pem -days 365 -nodes -subj "/CN=yourdomain.com"

Start Unbound:

sudo systemctl enable unbound
sudo systemctl start unbound

2. Caddy: Modern Web Server with Native DoH Support

Caddy provides built-in support for DNS over HTTPS (DoH).

Install Caddy

For Debian-based systems:

sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo tee /etc/apt/trusted.gpg.d/caddy-stable.asc
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo apt install caddy

Configure Caddy

Create or edit the Caddyfile at /etc/caddy/Caddyfile:

yourdomain.com {
    tls /etc/caddy/caddy_server.pem /etc/caddy/caddy_server.key

    route {
        forward_proxy {
            to dns://127.0.0.1:53
        }
    }
}

Generate TLS certificates:

openssl req -x509 -newkey rsa:4096 -keyout /etc/caddy/caddy_server.key -out /etc/caddy/caddy_server.pem -days 365 -nodes -subj "/CN=yourdomain.com"

Start Caddy:

sudo systemctl enable caddy
sudo systemctl start caddy

3. Stubby: DNS Privacy Daemon for DoT

Stubby is a lightweight daemon for DNS over TLS.

Install Stubby

For Debian-based systems:

sudo apt update
sudo apt install stubby

Configure Stubby

Edit the configuration file at /etc/stubby/stubby.yml:

resolution_type: GETDNS_RESOLUTION_STUB
dns_transport_list:
  - GETDNS_TRANSPORT_TLS

tls_authentication: GETDNS_AUTHENTICATION_REQUIRED
tls_query_padding_blocksize: 128
edns_client_subnet_private: 1

round_robin_upstreams: 1

upstream_recursive_servers:
  - address_data: 1.1.1.1
    tls_port: 853
    tls_auth_name: "cloudflare-dns.com"
  - address_data: 8.8.8.8
    tls_port: 853
    tls_auth_name: "dns.google"

Start Stubby:

sudo systemctl enable stubby
sudo systemctl start stubby

4. Knot Resolver: Versatile DNS Resolver with DoH and DoT

Knot Resolver supports both DoH and DoT.

Install Knot Resolver

For Debian-based systems:

sudo apt update
sudo apt install knot-resolver

Configure Knot Resolver

Edit the configuration file at /etc/knot-resolver/kresd.conf:

-- Set up DNS over TLS
resolver:tls("1.1.1.1", 853)
resolver:tls("8.8.8.8", 853)

-- Set up DNS over HTTPS
http:doa({
  ["doh"] = "https://yourdomain.com/dns-query"
})

Start Knot Resolver:

sudo systemctl enable kresd
sudo systemctl start kresd

5. CoreDNS: Modular DNS Server with DoH and DoT Plugins

CoreDNS supports DoH and DoT through plugins.

Install CoreDNS

For Debian-based systems:

curl -sL https://coredns.io/downloads/ | tar xz
sudo mv coredns /usr/local/bin/

Configure CoreDNS

Create or edit the CoreDNS configuration file (e.g., Corefile):

.:53 {
    forward . 1.1.1.1 8.8.8.8
    log
}

# For DoH
example.org {
    forward . https://yourdomain.com/dns-query
}

Start CoreDNS:

coredns

6. DNSDist: DNS Load Balancer with DoH and DoT Proxy

DNSDist can proxy DNS queries over HTTPS and TLS.

Install DNSDist

For Debian-based systems:

sudo apt update
sudo apt install dnsdist

Configure DNSDist

Edit the configuration file at /etc/dnsdist/dnsdist.conf:

-- Configure DNS over TLS
addTLS("127.0.0.1", 853)
addServer("1.1.1.1", {tls = true})
addServer("8.8.8.8", {tls = true})

-- Configure DNS over HTTPS
addDOH("127.0.0.1", 443, "https://yourdomain.com/dns-query")

Start DNSDist:

sudo systemctl enable dnsdist
sudo systemctl start dnsdist

Combining Tools for Comprehensive DNS Privacy

Integrating multiple tools can provide a robust DNS privacy solution. For instance:

  • Stubby + Unbound: Use Stubby to forward queries over TLS to Unbound, which performs DNS resolution and caching.
  • Caddy + Unbound: Set up Unbound for DoT and Caddy for DoH to provide secure DNS resolution over both protocols.
  • Knot Resolver: As an all-in-one solution for both DoH and DoT.

Conclusion

Securing your DNS traffic is essential to maintaining privacy and protecting against potential threats. With open-source tools like Unbound, Caddy, Stubby, Knot Resolver, CoreDNS, and DNSDist, you can set up a personal DNS resolver that supports both DNS over HTTPS and DNS over TLS. These tools offer flexibility, privacy, and control over your DNS queries, ensuring a more secure and private browsing experience.

Explore and configure these solutions to meet your specific needs and enjoy a safer online experience.

The post Setting Up Personal DNS over HTTPS (DoH) and DNS over TLS (DoT) Using Open-Source Software appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

koji buildsystem issues

Posted by Fedora Infrastructure Status on 2024-09-08 16:00:00 UTC

The koji buildsytem is under heavy load and not processing requests correctly. We are investigating.

The buildsystem should be back up and going now.

Contribute at the Fedora Linux 41 i18n and Tuned Test Week

Posted by Fedora Magazine on 2024-09-08 08:00:00 UTC

Fedora test days are events where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed to Fedora before, this is a perfect way to start.

There are two upcoming test periods in the next two weeks covering two topics:

  • Tuesday 10 Sept through Monday 16 Sept , is to test i18n
  • Monday 09 Sept through Friday 13 Sept, is to test the Tuned as Default Power Profile.

Come and test with us to make Fedora 41 even better. Read more below on how to do it.

i18n Test Days

The i18n team is testing changes for Fedora Linux 41 (IBus Chewing default for Traditional Chinese (Taiwan) and others). As a result, the i18n and QA teams organized a test week from Tuesday, September 10, 2024, through Monday, September 16, 2024. The wiki page contains links to the test images you’ll need to participate.

Tuned as default

We’re excited to invite testers to participate in the testing of the new Tuned Power Daemon in Fedora 41, which will soon become the default power profile daemon. This new feature aims to improve power management by offering more efficient power-saving profiles and enhanced customization options. Your feedback will be instrumental in ensuring a smooth transition from the previous power-profiles-daemon to Tuned.

Whether you’re a seasoned tester or new to Fedora, your contributions will help identify any bugs and refine this feature to offer the best experience for all Fedora users. Join us in shaping the future of power management in Fedora 41! Testing will occur Monday 09 Sept through Friday 13 Sept,The wiki page has more information about how to continue.

How do test days work?

A test day is an event where anyone can help make sure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. This is a perfect way to start contributing.

To contribute, you only need to be able to download test materials (which include some large files) and then read and follow directions step by step.

Detailed information about all the test days is available on the wiki pages mentioned above. If you’re available on or around the days of the events, please do some testing and report your results. All the test day pages receive some final touches which complete about 24 hrs before the test day begins. We urge you to be patient about resources that are, in most cases, uploaded hours before the test day starts.

Come and test with us to make the upcoming Fedora Linux 41 even better.

Understanding DNS over TLS (DoT) and DNS over HTTPS (DoH)

Posted by Piju 9M2PJU on 2024-09-08 02:24:42 UTC

As our data increasingly travels over the Internet, safeguarding it from prying eyes is crucial. DNS over TLS (DoT) and DNS over HTTPS (DoH) are two protocols designed to encrypt DNS requests, ensuring that your data remains secure. In this post, we’ll explore how these protocols enhance your privacy and how they differ from one another.

What is DNS, and Why Does It Need TLS or HTTPS?

The Domain Name System (DNS) is like the internet’s phone book, translating human-friendly domain names into IP addresses that computers use to communicate. However, standard DNS queries are not encrypted, leaving them vulnerable to interception. This can pose significant security risks. Encrypting DNS requests with TLS (Transport Layer Security) or HTTPS (Hypertext Transfer Protocol Secure) helps protect this data from unauthorized access and reduces the risk of data breaches. Essentially, these encryption protocols ensure that your DNS queries remain private and secure.

The Importance of Encrypting DNS Requests

Encrypting DNS requests is vital for maintaining data privacy and security. It prevents malicious actors from intercepting or tampering with the data, protecting users from potential threats such as DNS hijacking, where cybercriminals redirect your traffic to malicious sites. Encryption ensures that your browsing activity remains confidential and your data is shielded from prying eyes.

DNS over TLS (DoT) – What Is It?

DNS over TLS (DoT) is a protocol that enhances the security of DNS queries by encrypting them using TLS. This protocol adds a layer of encryption over the User Datagram Protocol (UDP), which is used for sending DNS queries. By establishing a secure TLS tunnel, DoT ensures that DNS requests and responses are encrypted and protected from unauthorized access. This is particularly beneficial when using public or shared networks, as it provides a safeguard against potential snooping.

What Is DNS over HTTPS (DoH)?

DNS over HTTPS (DoH) is another method for securing DNS queries, but it operates differently than DoT. DoH encrypts DNS traffic using HTTPS, which is the same protocol used for securing web traffic. This approach disguises DNS queries within regular HTTPS traffic, making it harder for third parties to monitor or block these queries. DoH also encrypts the entire DNS response, including the IP address, providing a higher level of privacy.

Comparing DNS over TLS and DNS over HTTPS

Both DoT and DoH offer encryption for DNS queries, but they differ in how they implement it:

  • Encryption Protocol: DoT uses TLS to encrypt DNS queries over TCP, while DoH uses HTTPS.
  • Ports: DoT operates on its own port (TCP 853), whereas DoH uses the standard HTTPS port (TCP 443).
  • Encryption Complexity: DoH employs more complex encryption through HTTPS, including encrypting the entire DNS response. DoT adds a TLS layer over UDP, which is simpler but still effective.

Which Is Better, DoT or DoH?

The choice between DoT and DoH depends on specific needs:

  • Network Security: DoT is often preferred for network security because it allows administrators to monitor and block DNS queries more easily.
  • Privacy: DoH may be more suitable for privacy since it hides DNS traffic within regular HTTPS traffic, making it harder for ISPs and other entities to track.

The Role of Private DNS Servers

Private DNS servers resolve external DNS queries and benefit from DoT and DoH encryption. Using these protocols ensures that the data exchanged between private DNS servers and external servers is secure, preventing potential attacks and maintaining data integrity.

Challenges in Implementing DoT and DoH

  • Compatibility: Some older systems and applications may not support DoT or DoH.
  • Configuration: Setting up DoT or DoH can be complex, especially if existing security measures are in place.
  • Mixed Content: Websites that use HTTPS but have DNS requests over unencrypted channels can pose challenges in enforcing DoT or DoH.

Setting Up DoT and DoH

To enhance your privacy and security, configure DoT or DoH on various operating systems:

  • Windows: Use Network Settings or third-party applications to enable DoT/DoH.
  • macOS: Configure DNS settings in Network Preferences or use apps to automate the process.
  • Linux: Edit the resolv.conf file or use systemd-resolved for DoT/DoH configuration.
  • Android: Specify a Private DNS provider in network settings for DoT.
  • iOS: Use a DNS profile or third-party app for DoT/DoH, as iOS does not natively support these settings for cellular networks.

DoT/DoH vs. VPNs

While DoT and DoH secure DNS queries, VPNs provide comprehensive privacy by encrypting all internet traffic. VPNs create a secure tunnel between your device and a remote server, protecting all your online activities from interception.

Conclusion

With increasing concerns about data privacy and the need for faster browsing, DoT and DoH offer essential security and performance benefits. Adopting these protocols can help make your internet experience safer and more secure.

The post Understanding DNS over TLS (DoT) and DNS over HTTPS (DoH) appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

Introducing BB-Link: A Revolutionary Tool for Amateur Radio Enthusiasts

Posted by Piju 9M2PJU on 2024-09-07 22:48:48 UTC

In the ever-evolving world of amateur radio, finding tools that streamline operations and enhance connectivity is a continuous pursuit for many enthusiasts. Enter BB-Link, an innovative tool that promises to be a game-changer in this realm.

BB-Link is a comprehensive solution designed to facilitate seamless communication between various amateur radio systems. Developed with both beginners and seasoned operators in mind, BB-Link offers an intuitive interface and robust functionality that bridges the gap between different radio technologies.

1. Cross-Platform Compatibility: One of BB-Link’s standout features is its cross-platform compatibility. Whether you’re using Windows, macOS, or Linux, BB-Link ensures that users across different operating systems can easily connect and communicate.

2. User-Friendly Interface: The tool boasts a clean and straightforward interface, making it accessible even for those who are new to amateur radio. The design focuses on ease of use, enabling users to quickly set up and start using the software without a steep learning curve.

3. Enhanced Connectivity: BB-Link supports a wide range of amateur radio protocols and standards. This versatility means it can integrate with various radio systems, improving overall connectivity and functionality.

4. Active Development and Support: BB-Link is not just a static tool; it’s actively developed with regular updates and community support. The developers are responsive to user feedback and continuously work to enhance the tool’s performance and features.

In a landscape crowded with radio communication tools, BB-Link differentiates itself through its focus on user experience and adaptability. The tool’s ability to work across different platforms and its support for multiple protocols make it a versatile choice for any amateur radio operator.

Additionally, the active development and strong community support ensure that BB-Link remains relevant and up-to-date with the latest advancements in radio technology.

To get started with BB-Link, visit the GitHub repository at https://github.com/islandmagic/bb-link. There, you’ll find comprehensive documentation, installation instructions, and updates about the latest features. Whether you’re looking to enhance your existing setup or explore new possibilities in amateur radio, BB-Link is worth checking out.

Conclusion

BB-Link represents a significant step forward in the world of amateur radio communication. With its user-friendly design, cross-platform support, and active development, it offers a compelling solution for radio enthusiasts seeking to optimize their operations. Dive into the BB-Link experience today and discover how it can elevate your amateur radio activities.

The post Introducing BB-Link: A Revolutionary Tool for Amateur Radio Enthusiasts appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

ESP32 APRS Projects

Posted by Piju 9M2PJU on 2024-09-07 22:34:17 UTC

1. ESP32 KISS TNC for APRS

An ESP32-based KISS TNC (Terminal Node Controller) can handle APRS messaging, beaconing, and digipeating. This type of project provides a modern and compact interface for APRS operations.

Key Features:

  • Acts as a KISS TNC for APRS communication.
  • Compatible with software like Xastir and APRSISCE/32.
  • Portable and power-efficient.

Components Needed:

  • ESP32 dev board
  • Radio interface (e.g., HT or mobile radio with audio coupling)
  • Optional GPS module for positioning

Repository Example:
While the link provided earlier was incorrect, you can find similar projects by searching GitHub for “ESP32 KISS TNC APRS.” For example, you can explore alternatives like this one:

  • Search for “ESP32 TNC” on GitHub or GitLab repositories.

2. LoRa APRS Tracker with ESP32

A LoRa-based APRS tracker utilizes the ESP32 and a LoRa module to send position reports and messages using the APRS protocol.

Key Features:

  • Long-range communication using LoRa technology.
  • Lightweight and low-power, suitable for portable setups.
  • Simple and easy to configure.

Components Needed:

  • ESP32 dev board
  • LoRa module (e.g., SX1276)
  • GPS module (e.g., NEO-6M)

Repository Example:
For a LoRa APRS Tracker, you might consider searching for LoRa-based APRS projects on GitHub. An example project can be found here:

  • Visit GitHub and search for “ESP32 LoRa APRS Tracker.”

3. APRS iGate with ESP32

An APRS iGate listens for APRS packets from a radio network and forwards them to the APRS-IS network. The ESP32 can act as a gateway to expand APRS coverage.

Key Features:

  • Bidirectional APRS packet handling.
  • Web interface for monitoring and setup.
  • Efficient and ideal for remote deployments.

Components Needed:

  • ESP32 dev board
  • RF module or VHF/UHF transceiver
  • Wi-Fi for internet access

Repository Example:
For iGate functionality, search GitHub for ESP32-based APRS iGate projects. Here is a similar repository that might serve the purpose:

  • Search GitHub for “ESP32 APRS iGate” to find up-to-date repositories.

The post ESP32 APRS Projects appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

The ESP32 Development Board: A Versatile Tool for Amateur Radio Enthusiasts

Posted by Piju 9M2PJU on 2024-09-07 22:17:31 UTC

The ESP32 development board is a powerful and versatile platform that has gained popularity among amateur radio enthusiasts. With built-in Wi-Fi, Bluetooth, and a dual-core microcontroller, the ESP32 is not only cost-effective but also highly functional for various amateur radio projects. This post explores some exciting projects you can undertake using the ESP32 dev board, ranging from digital mode interfaces to remote antenna controllers.

Why Choose the ESP32 for Amateur Radio Projects?

The ESP32 offers a low-cost, low-power System on a Chip (SoC) with integrated Wi-Fi and Bluetooth capabilities, making it ideal for wireless communication projects. Its dual-core processing power and extensive I/O options (GPIO, ADC, DAC, I2C, SPI, UART) make it suitable for digital mode interfaces, signal processing, remote controllers, and more. Its flexibility and power make it a great choice for building custom solutions for amateur radio setups.

Top Amateur Radio Projects with ESP32 Dev Board

Here are some of the best projects you can build with the ESP32 dev board to enhance your amateur radio experience:

1. Wi-Fi Enabled Transceiver

Build a Wi-Fi-enabled transceiver using the ESP32, capable of transmitting and receiving radio signals. The ESP32 can handle digital signal processing (DSP) tasks and connect to a web interface for remote operation via Wi-Fi.

Key Features:

  • Remote control through a web interface.
  • Operation in various digital modes like FT8, PSK31, RTTY.
  • Portable and remote operation.

Components Needed:

  • ESP32 dev board
  • SDR (Software Defined Radio) module (e.g., RTL-SDR)
  • Amplifiers, filters, antenna, and connectors

Project Links:

  • For a project related to SDR and ESP32, search for “ESP32 SDR projects” on GitHub or relevant forums.

2. Digital Mode Interface (Wi-Fi to Sound Card)

Create a digital mode interface using the ESP32 to connect your computer or mobile device to your radio over Wi-Fi, removing the need for physical cables.

Key Features:

  • Wireless connectivity reduces cable clutter.
  • Supports digital modes like FT8, PSK31, RTTY.
  • Low noise transmission.

Components Needed:

  • ESP32 dev board
  • Sound card module (e.g., PCM5102A)
  • Isolation transformers and audio connectors

Project Links:

  • Explore similar projects by searching for “ESP32 Digital Mode Interface” on GitHub.

3. Automatic Antenna Tuner

Build an automatic antenna tuner that adjusts the impedance between your radio and antenna, ensuring optimal performance.

Key Features:

  • Real-time tuning for impedance matching.
  • SWR monitoring and display.
  • Remote control capability.

Components Needed:

  • ESP32 dev board
  • Relays for switching capacitors and inductors
  • Capacitors, inductors, SWR meter circuit
  • LCD or OLED display module

Project Links:

  • Search for “ESP32 Automatic Antenna Tuner” on GitHub or electronics forums for related projects.

4. Remote Antenna Rotator Controller

Design a remote antenna rotator controller using the ESP32, allowing you to control the azimuth and elevation of your antenna remotely.

Key Features:

  • Remote operation via web or mobile interface.
  • Supports multiple rotators.
  • Can use GPS data for automatic direction setting.

Components Needed:

  • ESP32 dev board
  • Motor driver circuit
  • GPS module
  • Web server code

Project Links:

  • Look for “ESP32 Antenna Rotator Controller” on GitHub for detailed guides.

5. Portable QRP (Low Power) Station Monitor

Monitor operating conditions of a QRP station, such as temperature, voltage, current, and signal strength, using the ESP32.

Key Features:

  • Real-time monitoring of conditions.
  • Data logging.
  • Bluetooth alerts for specific thresholds.

Components Needed:

  • ESP32 dev board
  • Various sensors (temperature, voltage, current)
  • OLED or LCD display
  • Power supply circuit

Project Links:

  • Search for “ESP32 QRP Station Monitor” on GitHub or electronics communities.

6. Internet-Connected Beacon

Build an internet-connected beacon with the ESP32 for digital propagation modes like WSPR, transmitting your callsign and location.

Key Features:

  • Automatic beaconing operation.
  • Integration with WSPR or APRS networks.
  • Low power consumption.

Components Needed:

  • ESP32 dev board
  • Low-pass filters
  • GPS module
  • Antenna and connectors

Project Links:

  • For WSPR beacon projects, search “ESP32 WSPR Beacon” on GitHub.

7. Morse Code Decoder and Encoder

Create a Morse code decoder and encoder using the ESP32, operating over Wi-Fi or Bluetooth to decode incoming CW signals or transmit CW from text.

Key Features:

  • Real-time Morse decoding.
  • Portable and compact.
  • Adjustable CW speed.

Components Needed:

  • ESP32 dev board
  • Audio interface
  • OLED or LCD display
  • Keyer circuit

Project Links:

  • Look for “ESP32 Morse Code Decoder” on GitHub for related examples.

8. Digital Voice Hotspot (D-STAR, DMR, System Fusion)

Build a digital voice hotspot with the ESP32 that connects to networks like D-STAR, DMR, or System Fusion, allowing communication through various transceivers.

Key Features:

  • Supports D-STAR, DMR, System Fusion.
  • Wi-Fi connectivity.
  • Compact design.

Components Needed:

  • ESP32 dev board
  • MMDVM (Multi-Mode Digital Voice Modem) board
  • OLED display
  • RF module and power supply

Project Links:

  • Search for “ESP32 Digital Voice Hotspot” on GitHub for relevant projects.

9. Ham Clock

Build a Ham Clock with the ESP32 to display UTC time, local time, solar data, and DX cluster spots, synchronized over the network.

Key Features:

  • Real-time UTC and local time display.
  • Solar data for propagation forecasting.
  • Customizable interface.

Components Needed:

  • ESP32 dev board
  • TFT or OLED display
  • Wi-Fi for NTP synchronization

Project Links:

  • Explore “ESP32 Ham Clock” projects on GitHub for detailed guides.

10. Packet Radio Terminal

Use the ESP32 to build a packet radio terminal that emulates a KISS TNC for packet radio and APRS.

Key Features:

  • Emulates a KISS TNC.
  • Supports APRS messaging and BBS access.
  • Compact and low-power.

Components Needed:

  • ESP32 dev board
  • Radio interface
  • Display module and keyboard (optional)

Project Links:

  • Search “ESP32 Packet Radio Terminal” on GitHub for related projects.

Conclusion

The ESP32 development board opens up a world of possibilities for amateur radio enthusiasts. Whether you’re interested in building a digital voice hotspot, a Wi-Fi-enabled transceiver, or an automatic antenna tuner, the ESP32 provides a robust and versatile platform. With its powerful processing capabilities, built-in Wi-Fi, and Bluetooth support, the ESP32 makes integrating modern technology into traditional amateur radio setups easy. Explore these projects and see where your creativity takes you!

The post The ESP32 Development Board: A Versatile Tool for Amateur Radio Enthusiasts appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

The Ultimate Guide to the Automatic Position Reporting System (APRS): A Comprehensive Resource for Amateur Radio Enthusiasts

Posted by Piju 9M2PJU on 2024-09-07 14:25:27 UTC

Introduction to APRS

The Automatic Position Reporting System (APRS) is a digital communication protocol used by amateur radio operators to share real-time data, such as locations, weather conditions, text messages, and telemetry data. Developed by Bob Bruninga (WB4APR) in 1992, APRS transformed amateur radio by allowing dynamic information exchange in real-time. It is now a standard application for amateur radio operators worldwide, revolutionizing emergency communication, public service, and even daily radio activities.

APRS fundamentally differs from traditional packet radio systems by focusing on one-to-many communication instead of point-to-point. This means that any data sent from one station is instantly available to all other stations within range, without the need for pre-existing direct connections. This capability makes APRS an essential tool for amateur radio operators, emergency responders, event organizers, and anyone interested in real-time data sharing via radio waves.

The Core Features and Capabilities of APRS

APRS is renowned for its versatility and capability to handle various data types. Here is a deep dive into its primary features:

Real-Time Position Tracking and Mapping One of APRS’s most significant contributions to amateur radio is its ability to track positions in real-time using GPS data. This feature combines packet radio with GPS technology, enabling APRS stations to display the positions of other stations, vehicles, or objects on a digital map. Each station can see the positions of other stations on their screen, whether on a computer, mobile device, or dedicated APRS-enabled radio.

    • Applications: This is especially valuable for emergency management, where tracking the location of rescue teams, ambulances, or other critical assets can make a difference in response times and overall coordination. It is also popular in public events, such as marathons or parades, where event organizers need to monitor the real-time location of participants and support vehicles.
    • Visualization Tools: APRS data can be visualized on a variety of mapping software and platforms, including standalone software like UI-View, Xastir, and APRSISCE/32, as well as web-based platforms like APRS.fi. These tools provide rich visual representations of APRS data, enabling operators to see and understand the data in a meaningful context.

    Weather Station Reporting APRS has the built-in capability to integrate with remote weather stations and share their data over the network. This includes temperature, humidity, wind speed, wind direction, barometric pressure, and rainfall information. Many amateur weather stations transmit this data over APRS, providing valuable localized weather information that can be critical for disaster response and situational awareness.

      • Applications: APRS weather data is often used by storm spotters, emergency managers, and amateur meteorologists. This data can also be incorporated into broader weather networks, offering real-time updates that can help in monitoring and predicting weather changes.

      Two-Way Messaging, Bulletins, and Announcements APRS supports the transmission and reception of text messages, which can be either directed to specific stations or broadcast to all stations within the network. This capability is particularly important for emergency communication, where quick, reliable communication is needed.

        • Types of Messages:
          • Direct Messages: Sent to specific stations with the expectation of acknowledgment.
          • Bulletins: These are one-to-many messages broadcast to all stations. They are useful for making general announcements like event updates or emergency alerts.
          • Group Messages: Targeted at specific groups rather than individual stations, which is useful for organized groups like search and rescue teams or weather spotting groups.
        • Reliability: APRS ensures that messages are acknowledged by the receiving station. If an acknowledgment is not received, the message is retransmitted, increasing the likelihood that it will be received successfully.

        Internet Integration: APRS-IS and Global Accessibility The APRS Internet System (APRS-IS) connects local APRS networks with a global network of servers, providing worldwide access to APRS data. By linking local radio-based APRS networks to the Internet, APRS-IS enables stations from around the world to share their information, making APRS a globally accessible communication tool.

          • Web-Based Interfaces: Websites like APRS.fi offer real-time access to APRS data, allowing users to track stations, view messages, and even monitor weather reports from any web browser. These interfaces provide rich features such as historical playback, filtering options, and detailed mapping.
          • Cross-Band and Cross-Medium Connectivity: APRS-IS also facilitates cross-band (e.g., VHF to HF) and cross-medium (radio to Internet and vice versa) communication, significantly expanding the versatility and reach of APRS networks.

          Digipeating and Smart Path Management APRS uses digipeaters to extend the range of APRS transmissions. Digipeaters are relay stations that retransmit packets they receive, thereby increasing the coverage area of the original transmission. APRS employs generic digipeating, where packets use predefined aliases like RELAY, WIDE, or TRACE to manage how they are retransmitted.

            • Generic Digipeaters: Stations configured with aliases like RELAY and WIDE can serve as digipeaters. This setup allows any station to automatically use nearby digipeaters without knowing the specific callsigns or configurations, simplifying setup and operation.
            • Smart Digipeating (WIDEn-N and TRACEn-N): More advanced digipeaters support WIDEn-N and TRACEn-N algorithms, which dynamically adjust how packets are relayed based on their journey through the network. This reduces redundant transmissions and prevents packet loops, optimizing network efficiency.
            • Gating to Other Networks: APRS data can also be gated to other networks like HF (High Frequency) to VHF (Very High Frequency) or even to the Internet. This makes APRS a powerful tool for linking different communication mediums and extending the operational range of amateur radio.

            Support for Specialized Hardware and Devices Devices like the Kenwood TH-D7, TM-D710, TM-D700, and Yaesu FTM-400XDR radios come with built-in APRS functionality. These devices include integrated GPS receivers, TNCs (Terminal Node Controllers), and APRS software, making them highly efficient for mobile operations. The built-in APRS interfaces make these radios user-friendly for both beginners and seasoned operators.

              • APRS-Specific Features: These radios provide interfaces that allow users to send/receive messages, view nearby stations, track objects, and much more. Many also support DPRS (Digital Position Reporting System), which is a variant of APRS for digital radios, further extending the functionality.

              APRS Protocol Structure and Technical Details

              APRS is built on the AX.25 protocol, which is widely used in amateur radio for packet-based communication. The AX.25 protocol is derived from the X.25 protocol suite, a protocol designed for packet-switched networks. APRS utilizes the UI-frames (Unnumbered Information frames) mode of AX.25, enabling connectionless communication. This means that APRS frames are transmitted without the need for establishing a connection, making it ideal for real-time broadcast-style communication.

              APRS Packet Structure Breakdown

              An APRS packet is composed of several fields:

              1. Destination Address Field: This field specifies the intended recipient of the packet. However, in APRS, this field can also contain information like the type of data (e.g., GPS data, messages) or specify a group to which the packet is directed. Some examples of destination addresses include GPS, APRS, and BEACON.
              2. Source Address Field: This field contains the callsign and SSID of the transmitting station. The SSID (Secondary Station Identifier) is an additional identifier that differentiates between different types of APRS transmissions or specifies icons that represent the station on the map (e.g., car, house, weather station).
              3. Digipeater Address Field: This field contains the callsigns of digipeaters that will relay the packet. Up to eight digipeaters can be specified in an APRS packet, but the use of smart path management reduces the need for specifying each one.
              4. Control and Protocol Identifier Fields: These fields are standard in all AX.25 packets. The Control field is set to 0x03 for UI-frames, and the Protocol Identifier (PID) field is set to 0xf0, indicating no layer 3 protocol.
              5. Information Field: The information field is the core of an APRS packet. It contains the actual APRS data and always starts with a Data Type Identifier (DTI) that specifies what kind of data follows (e.g., position, message, weather report). The information field can include position reports, text messages, weather information, or even telemetry data.

              Detailed Overview of APRS Data Types and Extensions

              APRS supports a variety of data types, each designed to carry different information. Here are some of the most critical APRS data types:

              Position Reports: These are perhaps the most widely used data type in APRS. A position report contains the latitude and longitude of a station or object, its symbol, and optionally additional information like course, speed, or altitude. Position reports can be **

                compressed** or uncompressed, with compressed reports using fewer bytes and thus reducing bandwidth usage.

                • Uncompressed Format: A typical uncompressed position report looks like 4903.50N/07201.75W>Comment. The latitude is represented as 4903.50N (49 degrees, 3.50 minutes North), and the longitude as 07201.75W (72 degrees, 1.75 minutes West). The / character is a Symbol Table Identifier, and the > character is the Symbol Code representing an icon on the map.
                • Compressed Format: Compressed format uses Base-91 encoding to reduce the size of position data. This format is essential for environments where bandwidth is limited, like in mobile or satellite operations.

                Objects and Items: APRS allows users to create and manage objects or items on their maps. An Object can be a fixed or moving entity with a unique identifier, such as a checkpoint, an emergency location, or a weather balloon. An Item is similar but is typically temporary or less significant, such as a hazard on a course or a mobile point of interest.

                  • Creating Objects: Operators can manually input the object’s position, description, and other attributes. Once created, these objects are broadcasted over APRS, and all stations in the vicinity will see them on their maps.
                  • Tracking and Updating: Objects can have dynamic data like position updates and status changes. For example, a moving weather balloon’s position can be updated continuously, providing real-time tracking.

                  Weather Reports: Weather data is essential in APRS, and it supports several formats to represent it:

                    • Complete Weather Report: Includes data like temperature, humidity, wind speed and direction, barometric pressure, and rainfall. These reports are timestamped and usually contain positional information.
                    • Positionless Weather Report: This is used when the weather station is static. These reports are useful for continuously monitoring specific locations without repetitive position data.
                    • Integration with APRS Clients: APRS clients, such as APRSISCE/32 and Xastir, can decode and display weather data directly on the map, giving users immediate insight into weather conditions around them.

                    Telemetry Data: APRS supports telemetry reporting, which is widely used for remote monitoring of equipment. Telemetry data can represent almost anything from environmental sensors to equipment status indicators.

                      • Standard Format: The telemetry format is well-defined in the APRS specification, and it supports several channels of analog and digital data.
                      • Applications: APRS telemetry is often used to monitor remote repeater sites, weather stations, power systems, or even personal health monitors.

                      Mic-E Data Format: Mic-E (Mic Encoder) is a specialized APRS format that compactly encodes position information and status messages into the AX.25 packet header. This format is used mainly by mobile trackers to reduce the size of the data transmitted, which is crucial for bandwidth efficiency.

                        • Position Encoding: Mic-E encoding reduces position data to just a few bytes, freeing up bandwidth for other critical data.
                        • Applications: Mic-E is commonly used in trackers like the Byonics TinyTrak and Argent Data Systems OpenTracker, which are popular among mobile operators and for APRS beacons.

                        Data Extensions: APRS allows for additional information to be appended to position reports or other data types. These extensions include:

                          • Course and Speed (CSE/SPD): Specifies the course and speed of a moving station or object.
                          • Wind Direction and Speed (DIR/SPD): Used in weather reports to represent wind data.
                          • Power, Height Gain Directivity (PHG): Specifies the power, antenna height, gain, and directivity of a station, which is used to calculate radio coverage circles around stations.

                          The APRS Design Philosophy

                          APRS is built on several core principles that make it highly effective as a tactical communication tool:

                          1. Real-Time Tactical Communications: APRS is designed for use in dynamic and time-sensitive environments such as emergencies and public service events. It provides real-time visibility and communication without requiring complex setup or configuration.
                          2. Decentralized, Self-Organizing Networks: Unlike traditional networks that rely on fixed infrastructure, APRS networks are self-organizing and can function effectively with minimal infrastructure. The use of digipeaters and smart algorithms ensures that data flows efficiently across the network.
                          3. Adaptive Traffic Management: APRS uses several algorithms to manage traffic on the network dynamically. For example, the Decay Algorithm increases the interval between redundant transmissions, allowing new and urgent data to be prioritized over older, less critical data. Similarly, Message-On-Heard logic retransmits important messages if a receiving station is detected nearby, enhancing delivery reliability.
                          4. Symbol and Iconography Support: APRS supports a rich set of symbols and icons that represent different types of stations or objects on a map. This visual differentiation helps operators quickly identify key assets or hazards during operations, enhancing situational awareness.
                          5. Extensibility and Interoperability: APRS is designed to be easily extensible. New data types and extensions can be added without breaking compatibility with existing systems. APRS also supports interoperability with various platforms, including digital modes, satellite operations, and Internet-linked systems like APRS-IS.

                          Applications and Use Cases of APRS

                          The versatility of APRS makes it useful in a wide range of applications:

                          1. Emergency Communication and Disaster Management During emergencies like earthquakes, floods, or wildfires, APRS provides a powerful tool for coordinating rescue efforts, tracking resources, and communicating with teams in the field. Its real-time nature ensures that all responders have the latest information, which is critical in life-and-death situations.
                          2. Public Service Events APRS is ideal for managing communications in public service events such as marathons, parades, and community fairs. It allows organizers to monitor the location of participants, manage checkpoints, and coordinate logistics seamlessly.
                          3. Search and Rescue (SAR) Operations APRS has become a staple in search and rescue missions due to its ability to provide real-time tracking of search teams, assets, and resources. By integrating APRS with digital maps and mobile devices, SAR teams can achieve a high level of coordination and effectiveness.
                          4. Amateur Radio Networking For amateur radio enthusiasts, APRS offers an interactive platform to engage with others, share information, and experiment with digital communication. APRS networks often serve as the backbone for community projects, emergency preparedness drills, and hobbyist experimentation.
                          5. Weather Monitoring APRS-enabled weather stations are vital for amateur meteorologists and storm spotters. The ability to share localized weather data in real-time enhances weather monitoring capabilities and provides valuable data for both amateur and professional meteorological research.
                          6. Education and Outreach APRS is a valuable educational tool for teaching about radio communication, networking principles, data formats, and geographic information systems (GIS). Many amateur radio clubs and educational programs incorporate APRS into their curriculum to engage students and new radio operators.

                          Getting Started with APRS: A Step-by-Step Guide

                          Choosing the Right Hardware and Software

                            • Radios: Consider radios with built-in APRS functionality like the Kenwood TH-D74, Yaesu FTM-400XDR, or handheld options like the Yaesu FT3DR.
                            • TNCs and Modems: For non-APRS-ready radios, external TNCs (e.g., Kantronics KPC-3+, Byonics TinyTrak) or sound card modems (e.g., Signalink USB) are needed to encode and decode APRS packets.
                            • APRS Software: Software like APRSISCE/32, UI-View, Xastir (Linux), and mobile apps like APRSdroid or PocketPacket offer comprehensive APRS functionality.

                            Setting Up Your APRS Station

                              • Install and Configure the Software: Download and install the APRS software of your choice. Configure your callsign, SSID, beacon settings, and APRS-IS server details.
                              • Connect Your Radio to the Computer: Use the appropriate interface cable or TNC to connect your radio to the computer or mobile device.
                              • Test Your Setup: Use local APRS frequency (typically 144.390 MHz in North America) and verify that your station is transmitting and receiving APRS data.

                              Understanding Beacon Settings and Path Management

                                • Set Your Beacon Interval: Depending on your mobility and network congestion, set an appropriate beacon interval to avoid network overload.
                                • Configure Digipeater Paths: For wide-area coverage, use paths like WIDE1-1,WIDE2-1. Adjust the path settings based on local recommendations to optimize network traffic.

                                Engaging with the APRS Community

                                  • Join APRS Networks and Communities: Engage with local and online APRS communities to share information, participate in events, and collaborate on projects.
                                  • Participate in Public Service Events: Volunteer your APRS station and expertise for local events and emergency preparedness drills.

                                  Conclusion

                                  The Automatic Position Reporting System (APRS) stands as a testament to the innovative spirit of the amateur radio community. It bridges the gap between traditional voice communication and digital data exchange, providing a versatile, reliable, and efficient tool for real-time information sharing. Whether for emergency response, public service, or just for fun, APRS continues to evolve, offering new capabilities and expanding its reach across the globe. With its unique blend of simplicity, power, and community-driven innovation, APRS remains a cornerstone of amateur radio communication.

                                  The post The Ultimate Guide to the Automatic Position Reporting System (APRS): A Comprehensive Resource for Amateur Radio Enthusiasts appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

                                  Exploring the Tiered Structures of DNS and APRS-IS: A Technical Comparison

                                  Posted by Piju 9M2PJU on 2024-09-07 10:48:56 UTC

                                  In the world of digital communication, both the Domain Name System (DNS) and APRS-IS (APRS Internet Service) play crucial roles, each managing data in its own way. Despite their different applications, these systems share similarities in their tiered architectures. Understanding these similarities not only highlights the efficiency of each system but also provides insights into how hierarchical structures can optimize data management and communication.

                                  image-1024x576 Exploring the Tiered Structures of DNS and APRS-IS: A Technical Comparison

                                  What is DNS?

                                  The Domain Name System (DNS) is a fundamental component of the internet, serving as its directory service. When you type a web address like www.example.com into your browser, DNS translates this human-readable name into an IP address that your computer can use to find the website. This process involves a multi-tiered system:

                                  • Root Servers: At the top of the hierarchy, these servers handle queries related to the root of the DNS namespace and direct requests to TLD (Top-Level Domain) servers.
                                  • Top-Level Domain (TLD) Servers: These servers manage domain extensions such as .com, .org, and country codes like .uk or .jp.
                                  • Authoritative Servers: The final tier in the DNS hierarchy, these servers provide the actual IP address for a given domain, completing the lookup process.

                                  What is APRS-IS?

                                  APRS-IS is a network used by amateur radio operators to share real-time data such as GPS coordinates, weather information, and messages. APRS (Automatic Packet Reporting System) uses radio frequencies and the internet to disseminate data. The APRS-IS network consists of several key layers:

                                  • IGates (Internet Gateways): These are the entry points for APRS data, receiving packets from local APRS stations and injecting them into the APRS-IS network.
                                  • Regional Servers: These servers handle data from specific geographic areas, managing regional traffic and ensuring efficient distribution within their scope.
                                  • Core Servers: At the heart of the APRS-IS network, core servers aggregate and distribute data globally, ensuring that APRS information is available across the entire network.

                                  Similarities Between DNS and APRS-IS Tiered Structures

                                  1. Hierarchical Data Management

                                  Both DNS and APRS-IS operate using a hierarchical model where each tier has a specific role:

                                  • DNS: Queries start at the root and move through TLD servers to authoritative servers, each level playing a role in resolving the domain name.
                                  • APRS-IS: Data flows from local APRS stations through IGates to regional servers and finally to core servers, with each tier ensuring the data reaches its destination efficiently.

                                  2. Redundancy and Load Balancing

                                  To maintain reliability and performance:

                                  • DNS: Multiple servers at each tier handle requests to prevent overload and ensure availability. This redundancy protects against failures and balances the load across the system.
                                  • APRS-IS: Similarly, multiple IGates and servers ensure that data is reliably transmitted and distributed. If one server fails, others can take over, maintaining the system’s robustness.

                                  3. Local and Global Scope

                                  Each system manages data with different scopes:

                                  • DNS: Handles global queries at the root level but has more localized servers at the TLD and authoritative levels.
                                  • APRS-IS: Manages local data through IGates and regional servers, while core servers handle global distribution, ensuring that information is accessible worldwide.

                                  4. Bidirectional Data Flow

                                  While DNS primarily handles unidirectional queries (from client to server), APRS-IS supports bidirectional communication:

                                  • DNS: Updates and changes generally move from authoritative sources back through the hierarchy.
                                  • APRS-IS: Allows for two-way communication, where users can send messages via the internet that are then transmitted over radio frequencies, bridging the gap between internet and radio-based data.

                                  Conclusion

                                  The tiered structures of DNS and APRS-IS demonstrate how hierarchical models can effectively manage data flow and communication. Whether resolving domain names or sharing real-time APRS data, these systems rely on a carefully designed hierarchy to ensure efficiency, reliability, and global reach. By examining these similarities, we gain a deeper appreciation for the technical architecture that supports our digital and radio communication networks.

                                  The post Exploring the Tiered Structures of DNS and APRS-IS: A Technical Comparison appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

                                  Setting Up Your Own Mail Server with Mailcow and Docker: A Step-by-Step Guide

                                  Posted by Piju 9M2PJU on 2024-09-07 08:29:38 UTC

                                  Managing your own email server can be a game-changer, especially if you are concerned about privacy, control, and customization. Enter Mailcow, a versatile open-source suite for managing your email that integrates beautifully with Docker. In this post, we’ll explore what Mailcow is, why you should consider using it, and a step-by-step guide to installing it using Docker.

                                  What is Mailcow?

                                  Mailcow is a modern, self-hosted mail server suite based on Docker. It bundles several popular open-source software components to provide a complete email solution. Mailcow is designed to be easy to deploy and maintain, allowing users to create a secure and feature-rich email environment with a clean and intuitive web interface.

                                  Key Features of Mailcow:

                                  • Web-Based Management Interface: A user-friendly interface to manage users, domains, and settings.
                                  • Anti-Spam and Anti-Virus: Integrated tools like SpamAssassin and ClamAV for security.
                                  • DKIM, DMARC, and SPF Support: Helps in securing your email traffic and reducing spam.
                                  • Calendar and Contact Synchronization: Includes SOGo for calendaring, contact, and mail client support.
                                  • Integrated Backup: Automated and easy-to-manage backups.
                                  • Multiple Language Support: Supports a wide range of languages, making it accessible globally.

                                  Why Use Mailcow?

                                  There are several reasons to choose Mailcow as your email server:

                                  1. Control and Privacy: Keep your data private by hosting your email service.
                                  2. Cost Efficiency: Save on costs associated with paid email services.
                                  3. Feature-Rich: Offers all features that a modern email system should have.
                                  4. Community Support: As an open-source project, Mailcow has an active community providing support and updates.

                                  How to Install Mailcow using Docker

                                  Installing Mailcow using Docker simplifies the deployment process by isolating each component in its container. Here’s a step-by-step guide to setting up Mailcow on a fresh Ubuntu or Debian server.

                                  Step 1: System Requirements and Preparation

                                  Before installing Mailcow, ensure you have the following:

                                  • A fresh server running Ubuntu 20.04 LTS or Debian 10/11.
                                  • At least 2 GB of RAM (recommended 4 GB or more).
                                  • 10 GB of disk space, although more is better for storing emails.
                                  • A fully qualified domain name (FQDN) for your server, e.g., mail.yourdomain.com.

                                  Ensure your system is up-to-date:

                                  sudo apt update && sudo apt upgrade -y

                                  Step 2: Install Docker and Docker Compose

                                  Mailcow runs on Docker, so the first step is to install Docker and Docker Compose.

                                  1. Install Docker:
                                  curl -fsSL https://get.docker.com -o get-docker.sh
                                  sudo sh get-docker.sh
                                  1. Install Docker Compose:
                                  sudo apt install docker-compose -y

                                  Step 3: Clone the Mailcow Repository

                                  Now, download Mailcow from its GitHub repository to get the latest version:

                                  git clone https://github.com/mailcow/mailcow-dockerized
                                  cd mailcow-dockerized

                                  Step 4: Configure Mailcow

                                  1. Generate Configuration Files:

                                  Run the script to generate the necessary configuration files:

                                  ./generate_config.sh

                                  You will be prompted to enter your server’s FQDN (e.g., mail.yourdomain.com).

                                  1. Adjust Configuration Files:

                                  You can customize your configuration by editing the mailcow.conf file generated by the script.

                                  Step 5: Set Up DNS Records

                                  To make your Mailcow server fully operational, set up the following DNS records for your domain:

                                  • A Record: Points your domain (e.g., mail.yourdomain.com) to your server’s IP address.
                                  • MX Record: Directs emails to your domain. Set it to mail.yourdomain.com.
                                  • SPF, DKIM, and DMARC Records: These records help in securing and authenticating your domain. Mailcow can help you generate these records.

                                  Step 6: Start Mailcow

                                  Now that everything is set up, it’s time to start Mailcow:

                                  docker-compose pull
                                  docker-compose up -d

                                  This command will pull the necessary Docker images and start the Mailcow services in detached mode.

                                  Step 7: Access the Mailcow Web Interface

                                  Once Mailcow is up and running, open your browser and navigate to https://mail.yourdomain.com. You should see the Mailcow login screen. The default credentials are:

                                  • Username: admin
                                  • Password: moohoo

                                  For security reasons, change these credentials immediately after the first login.

                                  Step 8: Configure Mailcow

                                  From the Mailcow admin interface, you can add domains, create email accounts, set up DKIM signing, configure spam filtering, and much more. The web interface is intuitive and provides a straightforward way to manage your mail server.

                                  Step 9: Set Up Backups and Maintenance

                                  Mailcow provides built-in tools for backup and maintenance. You can configure automatic backups and manage them through the web interface to ensure your emails are safe and your server runs smoothly.

                                  Conclusion

                                  Mailcow offers an excellent solution for anyone looking to host their own email server. With Docker’s simplicity and Mailcow’s feature-rich environment, setting up and maintaining a self-hosted mail server has never been easier. Whether you are a business looking to control your communication or a tech enthusiast who loves having everything in-house, Mailcow is a fantastic option.

                                  By following this guide, you’ll have your Mailcow server up and running in no time! Enjoy full control of your emails and the security that comes with it.

                                  The post Setting Up Your Own Mail Server with Mailcow and Docker: A Step-by-Step Guide appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

                                  Secure DNS DoH/DoT Server from the MyBSD Community

                                  Posted by Piju 9M2PJU on 2024-09-07 08:11:59 UTC

                                  Established in the 1990s, MyBSD is a community dedicated to providing secure and efficient digital infrastructure for all. In line with our commitment to enhancing internet security and protecting user privacy, MyBSD are excited to introduce their Secure DNS (DoH/DoT) server, now available for the community.

                                  Introduction to MyBSD’s DoH/DoT Server

                                  MyBSD Secure DNS server operates on the FreeBSD operating system, known for its stability, security, and high performance. This server is designed for users who seek a safer and more private browsing experience, free from data interception and filtering. To ensure lowest latency to Malaysian users, this server is running from Cyberjaya, Malaysia.

                                  🖥 MyBSD DoH/DoT Server Specifications:

                                  💡 Note: This server supports both IPv4 and IPv6 users.

                                  Why the Name “MANIS”?

                                  The server is named MANIS in tribute to the 6bone network JARING.MY, which was Malaysia’s first IPv6 Tunnel Broker. MANIS, short for Malaysian Advanced Network Integrated System, is a name deeply rooted in the history of Malaysia’s internet infrastructure development. With this name, we aim to continue the legacy of JARING.MY in advancing internet technology in Malaysia.

                                  Why Use DoH/DoT?

                                  With increasing online security threats and various forms of data censorship, using DNS over HTTPS (DoH) and DNS over TLS (DoT) has become crucial. These protocols encrypt DNS requests to ensure that data transmitted and received is unreadable by unauthorized third parties. This allows users to browse the internet more securely and privately.

                                  Start Using the MANIS Server Today!

                                  We invite you to start using the MyBSD DoH/DoT server and experience enhanced security and privacy firsthand. With support for both IPv4 and IPv6, this server is suitable for all internet users in Malaysia and beyond. Let’s work together to build a safer and more secure digital community!

                                  🔗 Enjoy a better, safer browsing experience with the MANIS DNS server! 🌐✨

                                  Thank you for supporting the MyBSD community since the 1990s.

                                  #MyBSD #SecureDNS #DoH #DoT #FreeBSD #DigitalSecurity #6bone #MANIS #JARINGMY #InternetSecurity

                                  The post Secure DNS DoH/DoT Server from the MyBSD Community appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

                                  How to Bypass Government DNS Redirection: A Comprehensive Guide

                                  Posted by Piju 9M2PJU on 2024-09-06 20:35:57 UTC

                                  In many countries, governments control internet access and block certain websites by redirecting DNS (Domain Name System) requests. This is known as DNS redirection or DNS hijacking. When you type a website address into your browser, your device sends a DNS request to a DNS server to convert the domain name (like www.example.com) into an IP address. If a government controls the DNS servers or intercepts DNS requests, they can redirect you to a blocked page or an unintended website. If you’re looking for ways to bypass government DNS redirection and access the free web, here are some effective methods:

                                  1. Use a Trusted Third-Party DNS Provider

                                  The easiest way to bypass government-controlled DNS servers is to use a third-party DNS provider that is known for its reliability and privacy. Some popular options include Google Public DNS (8.8.8.8 and 8.8.4.4), Cloudflare (1.1.1.1 and 1.0.0.1), and OpenDNS (208.67.222.222 and 208.67.220.220). Changing your DNS settings to one of these providers can often bypass government redirection. Here’s how to do it:

                                  • For Windows: Go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click on your network connection and select Properties. Choose Internet Protocol Version 4 (TCP/IPv4) and click Properties. Enter the DNS addresses of your chosen provider.
                                  • For macOS: Go to System Preferences > Network. Select your network connection and click Advanced. Go to the DNS tab and add the DNS addresses.
                                  • For Android/iOS: Go to Settings > Wi-Fi. Tap on your network and look for DNS settings. Enter the new DNS addresses manually.

                                  2. Use DNS over HTTPS (DoH) or DNS over TLS (DoT)

                                  DNS over HTTPS (DoH) and DNS over TLS (DoT) encrypt DNS queries to prevent interception or manipulation. When using DoH or DoT, your DNS queries are encrypted and sent over HTTPS or TLS, making them indistinguishable from regular encrypted web traffic. This makes it difficult for governments to redirect or block specific DNS requests.

                                  • Enable DoH in Browsers: Most modern browsers like Google Chrome, Mozilla Firefox, and Microsoft Edge support DoH. Go to the settings and look for the DNS or privacy section to enable DoH. Choose a trusted DNS provider like Cloudflare, Google, or NextDNS.
                                  • Use Apps and Tools: Some apps, like 1.1.1.1 by Cloudflare or Intra by Jigsaw, provide simple solutions to enable encrypted DNS on mobile devices. These apps automatically use DoH or DoT to secure your DNS traffic.

                                  3. Use a Virtual Private Network (VPN)

                                  A VPN routes all your internet traffic through a secure, encrypted tunnel to a server in another location, bypassing any local DNS resolution. With a VPN, your DNS requests are handled by the VPN provider, and the government won’t be able to redirect or intercept them.

                                  • Choose a Reliable VPN: Not all VPNs are equal. Some VPNs may still leak DNS requests (DNS leaks), so it’s essential to use a trusted VPN provider known for strong privacy policies, such as ExpressVPN, NordVPN, or ProtonVPN.
                                  • Configure Your Device: Install the VPN app on your device and connect to a server outside your country. Ensure that the VPN’s DNS leak protection is enabled in the settings.

                                  4. Use a Smart DNS Service

                                  Smart DNS services provide a way to bypass geo-restrictions by rerouting specific parts of your internet traffic. While Smart DNS doesn’t encrypt your traffic like a VPN, it is faster and useful for accessing blocked content.

                                  • Choose a Smart DNS Provider: Some popular Smart DNS providers include Unlocator, SmartDNSProxy, and OverPlay. Sign up for a service and follow their instructions to set it up on your device.
                                  • Configure DNS Settings: Update your device’s DNS settings with the Smart DNS addresses provided by the service.

                                  5. Tor Browser and Onion Routing

                                  The Tor network allows you to browse the web anonymously by routing your traffic through multiple volunteer-operated servers (nodes). Using the Tor Browser, you can bypass DNS redirection as your DNS requests are resolved outside the government’s network.

                                  • Download and Install Tor Browser: Go to the official Tor website and download the Tor Browser for your platform.
                                  • Start Browsing Anonymously: Open Tor Browser and connect to the Tor network. You can now browse websites without worrying about DNS redirection or surveillance.

                                  6. Utilize Encrypted DNS Resolvers like DNSCrypt

                                  DNSCrypt is a protocol that encrypts DNS requests between your device and a DNS resolver. This prevents third parties, including governments, from intercepting or redirecting your DNS traffic.

                                  • Set Up DNSCrypt: Download a DNSCrypt client or use a service like Simple DNSCrypt for Windows. Configure it with a trusted resolver, and it will encrypt all your DNS requests.

                                  Conclusion

                                  Bypassing government DNS redirection is crucial for maintaining internet freedom and privacy. Whether you use third-party DNS services, encrypted DNS protocols, VPNs, Smart DNS, Tor, or DNSCrypt, it’s essential to choose the method that best fits your needs and technical skills. Always prioritize secure and reliable tools to protect your online activity from prying eyes. Stay safe and stay informed! 🌐🔒

                                  The post How to Bypass Government DNS Redirection: A Comprehensive Guide appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

                                  Week 27--36 update

                                  Posted by Ankur Sinha on 2024-09-06 14:06:07 UTC

                                  It's been a busy summer, so here's a consolidated post on what went on. I'm sure there's a lot more, but here are the salient points.

                                  Conference: CNS 2024 in July

                                  The annual conference for computational neuroscience, held by the Organization for Computational Neurosciences happens in July every year. It alternates between Europe and non-Europe locations to ensure that it's accessible to as much of the research community as possible. This year, it was organised in Natal, Brazil.

                                  We had a tutorial on NeuroML and a couple of posters accepted at the conference. We also had a couple of posters accepted.

                                  I'm also on the Board of Directors for CNS. As part of my duties, I organised a career development session this year on life "beyond academia" where we had a panel of people who had trained in academia but now had moved on to non-academic careers. The idea was to give students and early career researchers (ECRs) some idea of the "black box" that is industry, given that most of us have never worked in industry and therefore don't quite know much about it, which makes moving from academia to non-academic careers quite a daunting task.

                                  The conference was great. It was nice to see a lot of our colleagues, who we hadn't seen in a while. Natal, and Brazil in general, was a brilliant place to go to too. We had numerous Caipirinhas, delicious food, and enjoyed the warm weather. The days were hectic as always---absorbing information non-stop from 9 o'clock till the end of the day at about six o'clock, but then heading over to the socials and staying out late too.

                                  I had half a day extra or so after the conference, and a few of us drove to Praia de Pipa (Pipa Beach). It was absolutely beautiful. Since I was flying out in the evening and had already checked out of my hotel, I didn't get into the water, but we paddled around for quite a bit before having a scrumptious sea-food lunch.

                                  INCF/OCNS Software Working Group

                                  The working group is ticking along. We hosted another session where Adam Tyson spoke to us about the software tools their group develops.

                                  The Neuroinformatics Unit at the Sainsbury Wellcome Centre develops software tools for systems neuroscience.

                                  The Neuroinformatics Unit at the Sainsbury Wellcome Centre develops software tools for systems neuroscience.

                                  We'll organise more sessions now that the summer holidays are over.

                                  Some time off and other things

                                  I took a few days off here and there to relax too; it wasn't all work. Since I'd already been away for the conference, I didn't have another holiday planned this summer, though. A few of our friends got married over the summer and we were lucky enough to be there to share their special day with them. We were also lucky enough to see Shania Twain and Stevie Nicks perform in London at the British Summertime Festival at Hyde Park. Obviously very moving, and great fun.

                                  So, it's been a good couple of months.

                                  Infra and RelEng Update – Week 36 2024

                                  Posted by Fedora Community Blog on 2024-09-06 10:00:00 UTC

                                  This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contains updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.

                                  We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

                                  Week: 02 September – 06 September 2024

                                  I&R infographic

                                  Infrastructure & Release Engineering

                                  The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
                                  It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
                                  List of planned/in-progress issues

                                  Fedora Infra

                                  CentOS Infra including CentOS CI

                                  Release Engineering

                                  CPE Initiatives

                                  EPEL

                                  Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux (SL) and Oracle Linux (OL).

                                  Updates

                                  Community Design

                                  CPE has few members that are working as part of Community Design Team. This team is working on anything related to design in Fedora Community.

                                  Updates

                                  • CPE Swag Ticket being worked on
                                  • FCOREOS swag ticket almost complete

                                  ARC Investigations

                                  The ARC (which is a subset of the CPE team) investigates possible initiatives that CPE might take on.

                                  Updates

                                  • Ongoing interaction with the Fedora QA team for the user stories
                                  • Additional communication to be made once per week
                                  • Awareness in Design Team, Accessibility SIG and Docs Team
                                  • Expected completion of report for review – October 24, 2024

                                  If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.

                                  The post Infra and RelEng Update – Week 36 2024 appeared first on Fedora Community Blog.

                                  The Crucial Role of Digital Logging in Amateur Radio

                                  Posted by Piju 9M2PJU on 2024-09-06 09:53:06 UTC

                                  In the ever-evolving world of amateur radio, maintaining accurate and accessible logs is more important than ever. For many radio enthusiasts, logging QSOs (contacts) is not just a hobby but a crucial part of their operations, particularly when it comes to confirming international contacts and earning awards. Here’s why investing in digital logging systems is essential and how you can maximize your logging strategy.

                                  Why Digital Logging Matters

                                  The days of sending QSL cards by mail are dwindling. With the rising costs of postage and the global nature of amateur radio, many operators are shifting towards digital logging solutions. These systems not only streamline the process of confirming contacts but also provide a faster, more efficient way to manage and access your log data.

                                  Embrace Logbook of The World (LoTW)

                                  One of the best practices for modern amateur radio operators is to use Logbook of The World (LoTW), a cloud-based logging system provided by the ARRL. LoTW is widely recognized and supported by most online logbook platforms, making it a go-to solution for verifying QSOs. By integrating with LoTW, you ensure that your logs are accurately recorded and easily accessible for confirmation, whether you’re aiming for awards or simply verifying your contacts.

                                  The Importance of Backup

                                  Just like any other crucial data on your computer, your radio logs need to be safeguarded. Computers can crash, and storage devices can fail, leading to potential loss of valuable information. To prevent this, it’s essential to backup your logs to a cloud-based app. Cloud-based logging systems provide a reliable and secure way to store your data, ensuring that it remains safe and accessible no matter what happens to your local hardware.

                                  Utilize Multiple Cloud-Based Logging Apps

                                  When it comes to safeguarding your data, don’t settle for just one solution. Using multiple cloud-based logging apps to back up your logs can add an extra layer of protection. This approach ensures that your data is replicated across different platforms, reducing the risk of loss due to any single point of failure. Remember, having multiple backups is not just a precaution; it’s a smart and proactive strategy.

                                  Conclusion

                                  Amateur radio is a hobby filled with excitement and discovery, but for many operators, the need for accurate and confirmed logs is a serious matter. By leveraging digital logging systems like LoTW, backing up your data to the cloud, and using multiple logging platforms, you can ensure that your QSOs are recorded, confirmed, and preserved. This way, you can focus on the joy of radio communications while knowing that your valuable logs are secure and easily accessible.

                                  So, embrace the power of digital logging, keep your records safe, and continue to enjoy the fascinating world of amateur radio. 🌍✨


                                  Feel free to share your thoughts or experiences with digital logging in the comments below! #HamRadio #AmateurRadio #LoTW #QSO #DXing #HamCommunity #DataBackup #CloudLogging

                                  The post The Crucial Role of Digital Logging in Amateur Radio appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.

                                  Demonstrating Email via APRS using APRSDroid and Winlink

                                  Posted by Piju 9M2PJU on 2024-09-05 18:57:12 UTC

                                  In this blog post, I’ll guide you through how to send emails using APRS (Automatic Packet Reporting System) with APRSDroid and Winlink. This method is suitable for those using an APRS handheld or mobile transceiver. I’ll also provide a demonstration video that walks you through the process.

                                  What You’ll Need

                                  To get started, you’ll need the APRSDroid application, which is available for download from the Google Play Store. Ensure that you also have a Winlink account, as it’s required to send emails via APRS. Additionally, can you use any APRS handheld or mobile transceiver.

                                  Setting Up Your APRSDroid

                                  First, install APRSDroid on your Android device. Open the app and navigate to the settings to enter your callsign and other necessary details. Make sure to configure the APRS server to one that is reliable for your region.

                                  Sending Email from APRSDroid to Gmail via Winlink

                                  With APRSDroid set up and running, open the application and ensure it is properly connected to your APRS transceiver. Compose your email within APRSDroid, addressing it to your Gmail account. When you send the email, APRSDroid will transmit it over APRS, and it will be routed through Winlink to reach your Gmail inbox.

                                  Demonstration Video

                                  To make the process even clearer, I’ve prepared a demonstration video. In this video, you’ll see how to configure APRSDroid and connect it to your transceiver, how to compose and send an email using APRSDroid, and watch as the email arrives in your Gmail inbox.

                                  Conclusion

                                  Using APRSDroid or any APRS transceiver and Winlink to send emails via APRS is a fascinating way to combine amateur radio with email communication. If you have any questions or need further assistance, feel free to reach out or leave a comment below. Happy emailing via APRS!

                                  The post Demonstrating Email via APRS using APRSDroid and Winlink appeared first on HamRadio.My - Ham Radio, Fun Facts, Open Source Software, Tech Insights, Product Reviews by 9M2PJU.