[App_rpt-users] The 'nuclear' option

Scott Thomas scott at ab2g.net
Fri Feb 10 16:58:02 EST 2012

I've been told my ideas are pretty crazy...
How about changing the Pl frequency randomly and sending the changing freq.
of the Pl tone in morse code?
On Feb 10, 2012 12:39 PM, "Bryan D. Boyle" <bdboyle at bdboyle.com> wrote:

> Well...running a system is always a journey, not a destination.
> Anyway, being in the metro area out here in one of the original 13
> colonies...we get more than our share of lids, drive-bys, and other
> bottom-feeders who seem to like to do things like sit there and randomly
> key up machines (hey, Ma, looky at this!  I press one button and 13
> transmitters turn on!), spout colorful anglo-saxon metaphors, play DJ with
> bad music occasionally....or just act like alpha hotels on our systems,
> either individually or when we're connected to a reflector. It's just a
> feature of being wedged in between NYC (no comment...) and PHL (city of
> brotherly love with an obscene lethal crime rate...).
> Anyway...looking for thoughts on having, in a network of machines, a
> 'nuclear' option to
> 1. shut them out, at least for a while
> 2. minimize the fun (on their part...)
> 3. return some sanity, at least until they tire and slither off to bother
> some other machine (sorry...the next freq up doesn't have the
> technology...and it's my ticket that's transmitted as the ID...)
> So...thinking about this.  Quickest solution I came up with, but it
> requires an asterisk restart ("service asterisk restart" from the shell)
> would be to change the input PL, leaving the output PL (our coord bodies
> out here like to see bi-directional PLs...) in place.  Most mobiles and HTs
> can scan for the output PL...but, unless the lid is more than an appliance
> operator, they probably wouldn't be able to figure out how to scan the
> input (at least most of the time, I'll grant you that some probably
> would...but would the effort be worth it?)
> Yeah, this means that you have to have 2 stored settings in your mobile or
> HT for each participating machine on the same network.  And, if they're
> closer to the antenna than you are...capture effect would come into play,
> etc if they key up under/over you.  But, I'm looking at the low hanging
> fruit (in the spirit of not letting the perfect become the enemy of the
> good...).
> Is anyone else dealing with this problem (other than going on bunny hunts
> with a supply of sewing needles and a set of flush cutters?) or thought
> about what to do?
> Just spitballing.
> --
> Bryan
> 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.
> ______________________________**_________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/**mailman/listinfo/app_rpt-users<http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20120210/1dd2069f/attachment.html>

More information about the App_rpt-users mailing list