© Hellas-FRN.net

Connections shown as active are not valid. It is information that has not been updated for at least one year.

Instructions Change System Manager in Program FRN Due to the recent decision to change the connection of the Hellas-FRN server from the Primary System Administrator to Alternate for reasons already published, it is necessary to reset the FRN user program in order to be able to access the network. There are two ways for someone to act: 1. To download the program recommended by the Alternative System Administrator in Java format and fill in his details, so he can then request a code and connect to the global FRN network. Then make registration on the site hellas-frn.net so that, since he is a radio amateur, he can be given access to the Greek server. 2. To appropriately modify the program of the Initial System Manager used until now, choosing one of the following two ways: First way is to add two lines to the FRN Client.ini file located at This PC> Main Disk (C:) > Program Files (x86) > FreeRadioNetwork > FRNClient. You will open it with notepad, make the addition and save it in the same place in the program. The text of the two lines is as follows: Second way is to use the FRN_Switch application, which once installed and running on your computer, does the same recording as the first way without you searching and writing to a file. IMPORTANT: The initial FRN Client program will must be closed BEFORE you modify the FRN .ini with the FRN_Switch program, otherwise that modification will not be saved permanently, because the original FRN Client program always saves the current view of the FRN ini file from working memory to the drive at the end every program! This means that changes made in parallel via FRN_Switch are lost again... The modifications are read and accepted by the FRN program. Client only if you observe the execution sequence of the program. The compressed fileFRN_Switch_Setup.zip you get it from HERE. You unzip it and inside the resulting folder you find the executable file with the same name. There is no security issue for viruses. Install where the program suggests and as shown in the following photos: Here it should be known something that has been left unexplained and essentially becomes a mistake. In the above way and having let the program have installed the files automatically, basically when you run the same program multiple times on the same computer with different accounts, then the FRN Client .ini files are not all installed in the usual place in program files (Program Files X86) as shown above, but also in LOCAL APPDATA which will be difficult for you to find, because they belong to the hidden files and need a special search. This is done on newer Win10/11 operating systems. That is, you will also have a secondary .ini file that you did not know existed and you can find it if you search on the way C:\Users\"your user name"\AppData\Local\VirtualStore\ProgramFiles(X86)\FreeRadioNetwork\FRN Client\Secondary.ini The best way to avoid such hassle is to have FRN Client installed directly to the hard disk e.g. to have the path: C:\FRN\FRNClient Upon completion of the above actions and having chosen to run the FRN_Switch program you will have this image. NOTE: If you do NOT have it and you see an error message it is because you are missing some DLL files which cannot be executed. This is due to lack of the required "VC++ Redistributable Packages" on the Windows in question you are using. To solve the issue go to the FRN_Switch installation folder and find the files named vcredist. You install and the problem is fixed. File path C:\Program Files (x86)\FreeRadioNetwork DE\FRN_Switch Then notice that you have an option for FRNClient and FRNServer. Select FRNClient and press Search FRN Ini Files at the top right. As you understand its purpose is to search and present the .ini FRN files you already have on your computer. The search result will be presented to you as in the images. Normally it will have one entry for you (the first one) and is usually what it finds in the programs folder. If "Deep Search" is not selected, the program prefers to search the drive paths specified by certain system environment variables and are the relative standard paths where FRN Client Ini files can be found. Instead, the Deep Search option is intended, for example, for FRN users who have not saved the original FRN client in their standard program paths. With "Deep Search", the selected drive can be FULLY searched for FRN ini files. Here in the example the search was initially done without the deep search and presented only the first line. Then deep search was selected and searched again and presented two records because it looked at the same time in other places (hidden) of the C drive and found a secondary .ini file. Notice that it has the files checked as belonging to Old FRN EU. (Original System Manager). Click right on New FRN DE (Alternate System Manager) so that the options are transferred, as shown in the second image. Double check that no FRN programs are running and press Save to save the changes. After that, the program has gone and made entries in the .ini files so that they now work with the Alternative System Manager. More details from the creator of the FRN_Switch program HERE Select the reading language at the top of the page. Run the client program and tap the magnifying glass at the top. If everything is done correctly you will see all the servers that are connected in the Alternative System Manager. Notice that the hellas-frn.ddns.net server is listed in this list and the backup server hellasfrn.ddns.net below it. In this state of the program if you request a code the request will be sent to Alternative now System Manager and from you will receive the code by email. If you had a code before May 1, 2023 and you request again, you will most likely get the same one again, since the Alternate System Manager kept the same database as the Original. Press login and use FRN as before. Welcome back to our team!....

Construction derived from the ready-made μ-Interaspi version, only here the specifics for Allstalink Gateway operation have been integrated. A switch is located on the back of the device for operation as ASL Gateway or DEFAULT Gateway. The choice changes a lot in its internal mode of operation, but in both cases it uses the built-in raspberry instead of a separate PC to run the program. The Allstalink program with everything else you can integrate as described in videos elsewhere on this site, utilizes the capabilities of a radio gateway with a simple transceiver and links this wireless communication with the other side with a digital network. It goes without saying that Allstalink mediates this through bridging with echolink and DVSwitch. It goes without saying that even if the transceiver does not work, connected or not, the rest operates as an AllStaLink Node in the global network with whatever interfaces you will have to other analog or digital networks. Simply, the transceiver passes all this activity over the air for analog communication and via RF. The following project is in the process of being formatted as a device and not as a construction, i.e. whether or not it works with bare boards in the air and cables everywhere. The circuits have already been tested, they performed correctly and now it's time for the aesthetic side of the effort. The built-in raspberry can also be what someone already has and simply be placed in the specific position with the remaining internal connections on the pins according to the instructions. In short, the raspberry is placed inside with the program already installed on its SD card and then the power supply, SQL (COS) and PTT are connected with ready-made standbys. In order not to lose the monitor capability, there is also an HDMI output for monitoring and programming. The rest is left to the user's imagination as to what more he can do with it. It is NOT for a hotspot with room range. It is for a normal long-range gateway (as far as the RF of a mobile FM transceiver goes) and incorporates all these protections for RF, galvanic isolation, etc.). More information with the progress of the device formatting and accordingly with the interest that will arise (if any) from some.

The AllStarLink network availability is over 99,99% . Over the past four years, AllStarLink has seen phenomenal growth. Four years ago, around 2,000 nodes were connecting to our servers at the same time. Now we are seeing over 10.000 nodes. With a generous grant from ARDC, last year we released ASL 3. It is the first new client in 15 years for AllStarLink. ASL 3 has been re-engineered to run on Asterisk 22 LTS with the latest Debian 12 Linux release and modern hardware. This is a major update for current customers running Asterisk Version 1.4. The new release incorporates over 15 years of Asterisk bug fixes, significant security improvements and enhancements. The update required extensive modification of "app_rpt", the Asterisk application that is Allstar. Many memory leaks have been addressed, modules now load or refresh more reliably, and many bugs have been fixed. All of this contributes to improved stability and uptime. We recommend that all AllStarLink users upgrade their devices, PCs, and Raspberry Pis to use the latest version of ASL 3. Over 3,700 nodes have already been upgraded and are currently using ASL 3. This includes nodes using Raspberry Pi 3, 4, or 5 (many of which were running Hamvoip), x86_64/AMD computers, and cloud nodes, Kits4Hams SHARI boxes, Node-Ventures ClearNodes, Repeater Builder, and Hotspot Radios. To learn more, read the ASL3 Handbook or join the AllStarLink Community. If you are using a hotspot device, we recommend that you contact the hardware manufacturer for specific upgrade instructions. Use the link below for a live view of Allstar Link connections Worldwide. The greatest concentration is observed in the USA (mainly) and England. The rest of the countries are slowly following this global way of communication that does not eliminate either the existing analog P/D and analog communication, nor the digital one, due to the interconnection capability. With the help of this suitable but not difficult connections, everything is now possible. https://stats.allstarlink.org/maps/allstarUSAMap.html AllStarLink is a network of Amateur Radio repeaters, remote base stations and hot spots accessible to each other via Voice over Internet Protocol. AllStarLink runs on a dedicated computer (including the Rasperry Pi) that you host at your home, radio site or computer center. It is based on the open source Asterisk PBX running our app_rpt application. App_rpt makes Asterisk a powerful system capable of controlling one or more radios. It provides linking of these radio "nodes" to other systems of similar construction anywhere in the world via VoIP. AllStarLink's primary use is as a dedicated computer node wired to your repeater or radio. Connections from Echolink, other VoIP clients and telephone calls are supported. ALL STAR LINK worldwide users