[arm-allstar] connect log files
doug at crompton.com
Wed Sep 16 07:55:56 EST 2015
There is no specific way to stop just a certain node from connecting other than blocking their IP or maybe putting in a fake route for that node. You can turn off all connections when you are not there. You really have to think of Allstar as a repeater system with repeater rules even if you are a simplex node. Meaning you need to monitor and have control at all times. I will admit most of us do not do that. As far a burning up a radio. Well the same thing applies. Radios should be 100% duty factor like a repeater. That means not running them on high power and using some means of external cooling. For instance many use the Alinco DRx35 radios. They will run continuously at medium power with a colling fan directed over the heatsink fins. You also always want to set hardware timeouts in the radio. I usually set them to 5 minutes.
Date: Wed, 16 Sep 2015 07:28:16 -0400
From: tukosei at gmail.com
To: arm-allstar at hamvoip.org
Subject: [arm-allstar] connect log files
The other day I had a repeater system connect to my node and tie it up for hours with constant transmissions, I think my radio finally overheated after several hours and shut down before I discovered it. How can I track this down and lock it down to prevent unauthorized systems connecting?
arm-allstar mailing list
arm-allstar at hamvoip.org
Visit the BBB and RPi2 web page - http://hamvoip.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the arm-allstar