The Packet Radio
“
2 N 1
”
Handbook
by
Buck Rogers
K4ABT
Section 1
;
Packet Radio “The Basics
”
Section 2
;
The X1J4 System Node Operator’s (SNO) Handbook
ILLUSTRATION SECTION Charts & Node Drawings
TheNET
X1J4 System Node Operators Handbook
__ Page 52
APPENDIX “D”
The
Access Connect Limiting
(ACL) command is a useful feature of the X-1J+ nodes. It enables the sysop to set node
backbones to allow only access by other backbone nodes and the sysop’s call(s).
In other instances, the ACL feature may be used to restrain an offending station to a node, or network of nodes by invoking
the feature of the X-1J+ node.
At some point in time we are all faced with a situation that calls for action on the part of the X-1J node sysop to invoke the
Access Connect Limiting (ACL) command. Please try to resolve any conflict with any network or node offender before
turning to the use of the ACL to exclude his or her access to the node or network.
In one case, a BBS sysop who had just moved to the area from a distant State was hoping to establish another BBS so the
area users would have a means to handle local traffic. He began operation of his node on 145.770 the nationwide
Emergency and keyboard to keyboard frequency. He was informed of the purpose of the frequency of 145.770 MHz, and
without additional dialog, he moved his BBS to another LAN frequency.
In another case, an unscrupulous operator set up operation on the frequency and proceeded to use the system for DX
spotting during an ongoing weather-watch activity. After all else had failed did we invoke the ACL feature and excluded
his node, callsigns, and SSID’s from the network.
This won't be the last time this problem surfaces in any network.
TACT & DIPLOMACY:
If you find that you as a sysop are confronted with a similar situation, try first to remedy the situation with a kindness
approach. A bit of tact and diplomacy goes a long way.
If it appears that no reconcilable solution can be found then let the rest of the sysops know of your plight.
A deluge of letters from the sysops to the offender may help change his/her attitude toward your network. Where
emergency communications are concerned an act of malicious mischief is frowned on by both the ARRL and the FCC.
If all efforts for resolve fail, then remember that we have the ACL feature in the X1J+ code. ACL is a feature that we don't
care to implement (and please don’t abuse it) unless it is absolutely your last recourse.
The ACL feature is activated by first setting the mask ON. To do so, enter the sysops command mode using your node
password. To set the “mask”; Send the following command to the node:
ACL & 127
Your next entry is to set (ACL) the offending call sign:
ACL [offending CALL sign] +
+ 127
The offending node or station is history. The "127" sees to it that the call and/or any SSID of the offending call is denied
access to your node.
To remove the call from the ACL list, use the minus sign in the ACL string instead of the Plus (+) sign i.e.
ACL [CALL] -- 127
The user of the call sign now has all node privileges restored.
