|
Just for clarification, QnetGateway does not hammer its relinking attempts. Its very conservative. Their servers are likely getting hit with more malicious traffic every second than the 50 second relink attempt that QnetGateway will make, but I don¡¯t know that for sure either (I only know what QuadNet¡¯s servers see for malicious attempts). Anyways, this is from the OPERATING file from QnetGateway regarding the relinking code: ? By default, if the target is unavailable or becomes unavailable, QnetLink will attempt to re-link approximately every 50 seconds, at least until an unlinking command is sent. You will hear status of the connection attempt about every 50 seconds. If the target sends an unlink request, QnetLink will honor the request and not attempt to relink until another linking command is given. This automatic re-linking can be disabled with: ? module_x_auto_link=false ? in your configuration file, qn.cfg. Here the "x" is the module, "a", "b" or "c". This variable can be set in the qnconfig if executing in expert mode: ? ./qnconfig expert ? Colby ? ? From: [email protected] <[email protected]> On Behalf Of John F Davis
Sent: Friday, December 4, 2020 18:20 To: [email protected] Subject: [QnetGateway] What does Qnetgateway do if it gets a "Reflector busy" response when it tries to connect... ? This is from Terry (N8LN)...? and a related question is there any way to change the re-connect attempt time delay? I did get blocked for a bit on REF030 due to "hammering" with just the one "hotspot" (Qnet) active when my ISP acted up ..? twice? This is what Terry said for the record, a second connection attempt to reflector 001 or 030 is not automatically or immediately blocked. It is denied automatically. Then if it keeps trying to reconnect, gets denied, tries again over and over. The software on the hotspot should delay additional connection attempts after receiving a busy packet. It¡¯s like a person banging on your door and won¡¯t stop if you don¡¯t answer. Multiply this 30 or 40 devices and you can see the amount of unnecessary traffic/overhead generated. If the end user realizes what they have done (because their 2nd device is not connecting), and they stop trying, all is well. If it continues banging at the door, it gets blocked. Typically I receive a notification and make every attempt to notify the end user of the issue and possible solutions. Once they acknowledge the issue they are unblocked. Unfortunately I am not always able to find an e-mail address, the address is no longer valid or I receive no reply back. Remember the folks who built and pay for the operation of these busy reflectors, hosted in data centers still have jobs and lives. We are all voluntarily maintaining and administering the system to keep it operational and stable for all at no cost to the end users. The purpose of the blocks are to keep the system stable and available. I have a difficult time taking seriously the complaints of a very few. Most use the system responsibly and have no problems. -Terry N8LN ? In both cases I only had one hotspot active or one on REF030 (The other if active woudl have been elsewhere 089) ? |
