|
|
|
UER Store
|
|
sweet UER decals:
|
|
|
Mark Very Noble Donor
Location: South Carolina Gender: Male Total Likes: 16 likes
What is a lion, king of the savannah, when hes at the south pole?
| | | FRS safegaurd. < on 1/9/2004 5:03 PM > | Reply with Quote
| | | I'll start off by saying I have owned more FRS radios in my life then I care to think about... ever. After being tailed by someone else and dealing with your typical rabel on the waves I have come up with some basic concepts to protect your transmitions. Also take my use of FRS as to mean FRS GRMS freqs unless otherwise noted. Topics are disscused in 1, 1a, 2 and responses to topics are coresponded with a R1 R2 etc.
1. Never pic a frequency that is easy to remeber. Most FRS radios work off the 1-14 channel concept. Before private codes everyone worked on these 14 channels and much like CB radios the channels were overun with all sorts of converstations. Basicly that ment every redneck poser who didnt own a CB owned FRS. Obvious channel selections then occur. channels 1,2,5,7,10,and I believe 14 were most trafficed. Being in a enviroment of tourists I have a big problem with that. 1a. Privacy channels which came later in my efforts added a new dimension to security. Privacy channels allows someone to easily disapear in the 128 possiblites. Note that the same problem you see with 14 channels now is compounded by privacy channels. I have noticed easy to rember numbers always were chosen. (channels designated [main channel].[Privacy channel]) 1.11 1.23 2.34 12.12 3.33 etc. Obviously in low traffic areas this is not a concern as much. It is even less a concern if you are using a privacy codes. However on the highway etc this becomes more congested and may allow for a concern citizen to scan you out. L 1b. No matter what you do urban enviroments will have people who scan freqancys with scanners. There is no viable way to prevent this with FRS freqs. However some preventive maintance can help solve this problem. R1. Basicly there are two ways to prevent this problem. Never use commanly used freqancys. Also listen in your area for other traffic before you turn on begin your conversation. Simple as it sounds in high traffic areas this may become difficult R1a. Basicly the best tactic out there to prevent snoopers is frequany hoping. There are two main problems with this. One is preventing confusion among your team with what freq they should be on. Two knowing when to move. Basicly manual freqancy hoping prevents the casual observer from picking up your conversations. Two basic concepts work the best for freqancy hoping. One is to keep a preplanned list of channels for everyone. Then use a codeword to hop to the next freq or if third parties enter your channel imediatly move. SOP (standard operating proccedures) will have to be defined by your team. Second is to have a mathmatical system. We suggest picking the first 3-4 frequencys randomly then have a odd numbered additon or subtraction so you will eventually hit every channel. Example 1- 1.32 2-5.25 3-2.03 4. (+5.+7) or (-3.-9) to the last freq. Although subtraction is the most difficult it is the safest as people have a hard time with it in general. R1b. Since we have no possible way of preventing people from listening in it is imparitive to prevent the casual concerned citizen from listening to a converastion and understanding it. Always use call signs. Never use actually descriptive names of areas if possible. For instance never say, "I am fifty feet away from the old hospital sign." This requires what is called bullseyes. Basicly a bullseye is a pre determined spot or rally point. You can create multiple bulleye's designate them by numbers. Remeber to keep them simple and dont have to many. more to come. Will be writing about when to begin countermessures
| "If the threat level goes up its probably because of me." "I am looking for a girl who enjoys headbutting beltbuckles" |
| |
This thread is in a public category, and can't be made private. |
|
All content and images copyright © 2002-2024 UER.CA and respective creators. Graphical Design by Crossfire.
To contact webmaster, or click to email with problems or other questions about this site:
UER CONTACT
View Terms of Service |
View Privacy Policy |
Server colocation provided by Beanfield
This page was generated for you in 109 milliseconds. Since June 23, 2002, a total of 739828411 pages have been generated.
|
|