Digital & Analog Ham Radio Nodes - DMR, Echolink, AllStar, YSF, NXDN, P25, M17 & More
Don't ask something that has been answered. It has negative consequences!
Συχνές ερωτήσεις
Please, the first time you connect to the server, you are required to make the relevant microphone and headphone settings in the FRN program.
Log in to the Test chat room.
In this way and using the audio replay you can make your settings so that when you connect to a normal communication room, the setup process and observations by the others can be avoided.
Another reason is to avoid distracting others from the topic of discussion.
Of course, for final micro-adjustments when you enter a normal communication room no one will refuse to help you, but with your pre-work this will be short and effective. Note that the Test room has no access restrictions.
You can post it on Forum or by e-mail:hellas.frn@gmail.com
To create a node, the admin must first be informed about joining the server, but at the same time the location of the candidate node and its usefulness in the specific location must be discussed, always taking taking into account the economy of frequencies, materials and human resources for 24-hour surveillance. Then information is given on the necessary and appropriate equipment and wiring. Admin SV0XAL-e-mail:hellas.frn@gmail. com.
In any case, permission must be given by the SV0XAL administrator, based on the feasibility of the connection.
Contact details for further actions and after approval:
XLX Peer Interlink Settings
Please contact: SV2SNH for XLX peering
email me:xlxsv2snh@gmail.com.Greetings Sakis.
Note: Currently only Module A is used for International interlinks.
Other Modules can be done on request.
Edit xlxd.interlink, add the following line:
# xlxd.interlink
XLX165 xlx165.ddns.net A
NO the HELLAS-FRN network is ONLY FOR HAMSTERS WITH AN ACTIVE LICENSE. Internationally FRN as an online program can be used for any purpose in connection with other servers EXCEPT Hellas-FRN. The connection to Hellas-FRN follows a standardized access protocol and adherence to amateur radio ethics with continuous monitoring.
The time limit between conversations is 180 seconds (3 minutes).
All transmissions must be below this threshold or they will be momentarily rejected.
The 3-minute rule with the use of μ-interfaces is applied to the transmission and reception of the web portals, to protect machines from excessive use of RF or malicious acts with "anonymous" access by RF resulting in practically beneficial employment of the frequency.
The FRN program through which the collaborated gateways are connected and which are also the target of the “well-wishers” have the following properties with which the harassment is negated at any time and this update is made for the awareness of those mentioned below.
Each gateway owner is connected to the FRN program in simplex mode and with tone sql, locked to prevent accidental access by any parasitic RF source. Anyone interested in radio amateur access can talk by RF, as long as they put in the appropriate sub-tone that is announced by each gateway.
The gateway owner monitor is not obliged to respond to anyone who ignores the access setting. And this is because without the sub-tone, any broadcast from third parties is automatically excluded from the gateway’s employment and consequently also outside the FRN network. This consequently excludes the obligation to monitor the gateway since such a broadcast does not concern the network. One could claim that the frequencies are free and that he can choose the specific frequency of the gateway to talk with his company and without an sub-tone, regardless of whether there is an internet network. However, such an act is contrary to the mutual respect between the ham radio coleages and compliance with the current band plan. FRN follows the band plan faithfully and does not use any of the many other frequencies where ham radio operators chats with their mates. On the contrary, it is harassed by adjacent frequencies, where the narrow modulation imposed by the band plan is not used, as well as by unnecessary excessive use of output power colleagues transceivers, who insist on exhausting the limits of the legal use and not the useful for coexistence in it the limited frequency space.
In cases where someone now deliberately broadcasts with the correct sub-tone, but without behaving as expected according to the amateur radio code of conduct and indeed with the intention of harassing a communication already in progress, there is a way to block it.
This is done by the intervention of the owner of the specific gateway and through the FRN program to mute it or even stop it, so that it does not receive incoming RF emissions or does not communicate at all accordingly. He is the authorized administrator of the given gateway. When the harassment stops, it restores it to full operation.
Furthermore there is additional-parallel surveillance in the same communication room by the owners of the remaining gateways, who in addition to being administrators of the gateways in a similar way to them, they have administrator rights on all other gateways as well. This makes the network flexible in terms of surveillance because it does not rely only on the owner of one gateway, but on the overlap of all the owner gateways that are in the same communication room.
Simply put and at any time if there is a problem of malicious or accidental parasitic broadcast, any authorized gateway owner, as well as any other user of the FRN program can mute his or any gateway of another colleague as an instant reaction.
This mute stops the receive, but the rest of the activity on the FRN continues without the involvement of the offending gateway alone.
Finally, the following should be mentioned: In the event that someone calls normally from RF and does not get an answer, this does not mean that the system is not monitored (after the above description), but it is very likely that the specific gateway is muted or closed. Also, monitoring is limited only to whether the gateway works as intended and does not imply that the operator monitoring it will also answer any calls. It is not a correspondent in service. But if the gateway is interfered with, then it intervenes. The supervision criterion is therefore limited whether there is corrective action in the case of misuse of the gateway.
For information, each gateway owner is not obliged to have the gateway open if it is not monitored, so he can take it out of the network, e.g., at night. So someone calling in a certain area and not getting an answer should make sure that the gateway is in operation, before concluding that it is not monitored.
Each gateway can be permanently connected to the network and appear in one of three operating states.
1. No broadcast and receive
2. No receive, but only broadcast of what it receives from the internet
3. Broadcast and receive
All of the above is for the information of the fortunately very few who are unaware of these overlapping FRN gateway support conditions and attempt, either with DTMF tones or repeated PTTs to interfere or disrupt forcibly the conversations of colleagues at that moment.
Finally, and to make it more illustrative, at the time of intentional or accidental interference, the owner of the gateway or anyone else authorized to do so, simply right-clicks on the availability of the gateway and it mutes it, while the rest of the conversations are heard. Just like that. When the problem is gone, it brings it back again simply with another click on the computer.
—Those who are connected to Hellas-FRN at that time will not understand anything and will continue to use the network normally. That is, for those who keep the program open on a 24-hour basis, there will be no problem.
—Those who usually close the program at night will notice a delay in their next connection attempt.
—They will not be able to select from the list of available servers by pressing the magnifying glass. They should type the name hellas-frn.ddns.net
—Those who are in this process will not be able to get a code.
—If they take a long time to log in, they will not be able to enter at all, since in this case it is necessary to renew the connection data with the system manager.
—For those online, if the regular hellas-frn server also goes down, the automatic transfer to the backup hellasfrn.ddns.net will not work.
Caution: Do not make any changes to your existing FRN accounts on 1 PC, nor transfer an account to another PC, because such actions require the cooperation of the system manager who is out. That is, an account that was running normally on 1 PC and you moved it to another, it won’t run there and when you return to the previous PC, it probably won’t run there either.
Usually the period of time when the system manager is down is relatively short and happens either for upgrade reasons, or for reasons of solving technical problems arising from network load or by “well-meaning” smart people who have pleasant managing to make communication systems to go out of business.
When you are listening or transmit from a digital network and you see a different callsign on the screen than that of the operator, this means that the station that is transmitting or your station is coming from the analog side of the system. Due to the fact that the analog side does not transmit encoded information, you will not see the callsign of the transmitting station. Under this way you can realize that the station is coming from the HELLAS-FRN network's side. This is considered normal.
January 27th, 2024
After 9 years of cooperation with the Original System Manager, the Hellas-FRN.net network exhausted whatever limits of goodwill and patience it had and taking seriously the efforts of colleagues who employ machines and waste personal time relying on the Greek server, decided to leave the connect to it and connect to the Alternative System Manager, for the following serious reasons concerning the Original System Manager:
1. Frequent instabilities and interruptions in its operation, as a result of which the Hellenic server remains exposed to the colleagues who have trusted it for so many years and despite the tireless and costly efforts to improve the quality of the latter's communications.
2. No information from him or any early warning of any problem with his operation, so that there is a premeditation for actions of the servers connected to him.
3. No update if any attempt is made to resolve in case it goes offline or time perspective of re-opening keeping everyone in the dark and in doubt.
4. Instability or inability to give codes when requested for clients. Refusal to provide passwords to a specific type of email without an explanation as to why.
5. No new update-improvement to the operating program provided on the computer, not even when Hellas-FRN.net sent him the translation of the program into Greek, so that in the next version it is integrated from the beginning of the installation for easy selection.
6. Incorrect data synchronization of his website with the real connection lists of servers and clients around the world. Show connection status of previous months or even six months as current.
In addition to the above and the specific decision as Hellas-FRN.net, all of us who accepted his services, want to thank him for everything he has offered us so far. As it appears that continued support is now becoming difficult for him and for reasons we do not know, we count his positive contribution so far and will continue to push his original idea - inspiration further, inviting and challenging old and new radio amateurs to engage primarily with the hobby and then with the specific way of communication, enriched recently with the bridges of digital configurations and programs.
It is made clear that it is aimed at colleagues with basic knowledge and relevant experience in using a computer connected to a transceiver, as well as the necessary concepts and understandings concerning digital communication networks. So in conclusion, for someone with zero knowledge about the subject, its training, involvement, regulation and operation, either of a client or of a gateway, despite his desire, it is mandatory to make an effort to learn himself at the beginning as an absolutely necessary condition and then to attempt the application. The notion that someone, in TWO WORDS, will explain everything to him or someone else will set everything up for him, is beyond reality, since avoiding knowledge of the subject and direct operation (especially of a gateway) requires his personal involvement with the necessary elementary knowledge. What is written on this site is the necessary information about the subject and is not a "philosophical" rambling post per subject. If it is difficult for someone to read them, he should also recognize that nothing happens automatically by itself or that someone else is not going to do the work that he has to do.
