[App_rpt-users] Question...preventing access from web transceiver for certain callsigns...

Bryan D. Boyle bdboyle at bdboyle.com
Mon Jul 16 12:36:04 UTC 2012


On 7/15/12 9:20 PM, Kirk wrote:
> I turned that off on my nodes due to too many. Braindead nose pickers. All it takes are a few of them to spoil something good
>

Agreed.

What I did:

1. Turned off, on the mother ship, access via the web transceiver to ALL 
my publicly linked nodes: 144/220/440/900/audio console/hub (I have a 
commercial radio station broadcast console hooked into a URI to enable 
me to run nets from a decent op position...complete with a blinking "On 
Air" light over the door to my shack...:)  Hokey, I know...).

Then...since I want to be able to get into my system from elsewhere 
...just in case...

2. Left the access enabled on a node which is registered to another 
system which I take care of, but is not actually hooked up to a radio at 
this point (It's running the pseudo driver).  Also pointed my Echolink 
config to that node number.

So...I still have an entre' into the system, but, it's a) not full-time 
connected to my cluster (which is also connected to another hub) and b) 
changed the connect/disconnect *Xnodenumber sequence to make it more 
arcane.

Voila!  The Dain Bramaged drive-bys still can drive by...but, in 
essence, when the 'dummy" node is disconnected (which is most if not all 
of the time unless I need to come in via the wireline network)...don't 
even know they're there, nor is there any radio for them to key up, but, 
if I need to put up echolink during a net...I can connect that node up 
to enable access.  I know that's not what it was formally intended 
for...but, there seems to be just so many annoying, inconsiderate 
operators out there these days.  Must be the summer vacation...or the 
result of no-code licenses (***ducking*** and putting on the asbestos 
jockey shorts and cast iron cup...)

More than one way to solve the problem.

Was talking to a fellow system operator in the net I'm on...another 
option would be to somehow have a password access intercept that could 
be configured on the web transceiver...much like the old access codes we 
had to punch in back in the day for autopatch access on most 
machines...but that's another issue.

This doesn't solve the issue of drive-bys on other nodes in our network 
(and I know my fellow ops in that net are on this list...), but, at 
least I'm not contributing to the excess noise in the linked network by 
exposing my systems full time.

> Friends don't let Friends buy S*** from Clear/Clearwire.  Pass the word along Friend....

Friends also don't let Friends buy 11 Meter stuff, either...;)

73 fellow Allstarnauts.

-- 
Bryan WB0YLE
Morrisville PA
In this world, you must be oh so smart or oh so pleasant.
Well, for years I was smart. I recommend pleasant.
You may quote me.

Sent from my MacBook Pro.





More information about the App_rpt-users mailing list