Date   

Daily Node Hacking Attempts

stn3415 <stn3415@...>
 

Any other node owners noticing their log file containing lots of
unauthorized login attempts? For at least since Aug 04, almost every
day I have noticed attempts to log in as USER GUEST, USER ADMIN, or
USER TEST. Their IP address changes every time and are
systematically using a certain range of ports. Some of the IP
addresses I've looked up are registered to Chinese domains. I'd
personally like to squelch this activity before any real damage
occurs.


Re: Node Owners Ivan Path Notice

Tony Langdon (ATC) <tlangdon@...>
 

FYI... Mississippi -- IRLP node 4596 -- W5NRU Ellisville is
not yet RF capable. The node link radio is in the shop being
programmed, and is not yet ready to install. The W5NRU
repeater on 145.23 at Ellisville is currently on EchoLink.
Plans are for this node to be EchoIRLP.

However, we are presently on the *WX_TALK* conference with
AA5SG-R EchoLink # 1545 on the 442.250 AA5SG Repeater at
Ellisville, and plan to be there for the duration of the storm.
Thanks for the update. Will be looking out for you from the wee small hours
this morning :-)


Re: Node Owners Ivan Path Notice

aa5sg
 

Danny and all...

FYI... Mississippi -- IRLP node 4596 -- W5NRU Ellisville is not yet RF
capable. The node link radio is in the shop being programmed, and is not
yet ready to install. The W5NRU repeater on 145.23 at Ellisville is
currently on EchoLink. Plans are for this node to be EchoIRLP.

However, we are presently on the *WX_TALK* conference with AA5SG-R EchoLink
# 1545 on the 442.250 AA5SG Repeater at Ellisville, and plan to be there for
the duration of the storm.

Steve, AA5SG
Ellisville Mississippi
(Serving Laurel & Hattiesburg MS)
In EM51 on I-59 about 100 miles inland.

----- Original Message -----
From: "Danny Musten" <kd4raa@yahoo.com>
To: <irlp@yahoogroups.com>
Sent: Tuesday, September 14, 2004 3:48 PM
Subject: [irlp] Node Owners Ivan Path Notice


Our net control coordinator has generated a partial list of nodes
that could be in the potential path of Ivan. We have heard from some
of these already today.

If you are (or know) the trustees of these systems or
have knowledge of other adjacent nodes in these areas,
we would appreciate you passing the word to meet us on
IRLP Reflector 9210 or Echolink WX-Talk beginning
Wednesday morning. Our VoIPWX Net will activate then.

Reflector 9206 - Listen Only


Florida
IRLP Node: 4386 Jacksonville, Florida 147.2000
IRLP Node: 4530 Tampa, Florida 444.500
IRLP Node: 4629 Pensacolda Florida 145.745 (Says the node is down
currently)
IRLP Node: 4647 Clearwater Florida (Near Tampa) 443.850
IRLP Node: 4880 Tampa Florida 443.675
IRLP Node: 7260 Spring Hill, Florida 146.560

Alabama
IRLP Node: 3890 Huntsville, Alabama (Simplex)
IRLP Node: 4560 Madison, Alabama (Simplex)
IRLP Node: 4713 Scottsboro, Alabama (Simplex)
IRLP Node: 4950 Huntsville, Alabama (446.200)
IRLP Node: 4957 Scottsboro, Alabama (146.900)
IRLP Node: 7660 Mongtgomery, Alabama (446.450)

Louisiana
IRLP Node: 3416 Houma, Louisiana (Simplex)
IRLP Node: 8250 Abbeville, Louisiana (Simplex)
IRLP Node: 4269 Thinodaux, Louisiana (444.500) Says the node is
down.
IRLP Node: 4958 Baton Rouge, Louisiana (443.100) Says the node is
down.
IRLP Node: 5720 Lafayette, Louisiana (443.150)

Mississippi
IRLP node 4596 W5NRU Ellisville

Danny KD4RAA
kd4raa at voipwx.net




--- IRLP-Owners YahooGroups List ---
Yahoo! Groups Links






Re: Apt-get support for early versions of Redhat - PLSE RE AD

Tony Langdon (ATC) <tlangdon@...>
 

I WOULD like to get some feedback to understand, are people out there
willing to help us by converting some of the source tarballs
to RPMs for the
IRLP community or do we just leave things alone and wait n
see how Dave
progresses with Fedora ? I'm not comfortable with the wait n
see approach
however there is only a limited amount of work that Geoff and
I can do and
we would need support from the IRLP community to keep it relevant.
Is www.fedoralegacy.org going to be of any use to us as a source of updates?


Apt-get support for early versions of Redhat - PLSE READ

Peter Illmayer <pete@...>
 

Gents

As posted up a few months ago, we are planning to drop support for ALL
versions of Redhat EXCEPT for 9.0 with our apt-get mirror. As you are all
aware, Redhat has dropped support of ALL versions of desktop and are now
offering a "payware" enterprise desktop for corporates.

To this end, as of the end of this month, ONLY REDHAT 9.0 will be supported
by our apt-get mirror ie: 30-Sept-2004

Now you may say, your ssh version for 9.0 is way behind on the source
version, yes we know and this is of concern. Any security updates that need
to happen, it would be up to us ourselves to create the RPM and make it
available for the IRLP community to use.

I WOULD like to get some feedback to understand, are people out there
willing to help us by converting some of the source tarballs to RPMs for the
IRLP community or do we just leave things alone and wait n see how Dave
progresses with Fedora ? I'm not comfortable with the wait n see approach
however there is only a limited amount of work that Geoff and I can do and
we would need support from the IRLP community to keep it relevant.

Your feedback is appreciated

73's Pete..vk2yx

--
Open WebMail Project (http://openwebmail.org)

---------- Original Message -----------
From: "Danny Musten" <kd4raa@yahoo.com>
To: irlp@yahoogroups.com
Sent: Tue, 14 Sep 2004 20:48:54 -0000
Subject: [irlp] Node Owners Ivan Path Notice

Our net control coordinator has generated a partial list of nodes
that could be in the potential path of Ivan. We have heard from some
of these already today.

If you are (or know) the trustees of these systems or
have knowledge of other adjacent nodes in these areas,
we would appreciate you passing the word to meet us on
IRLP Reflector 9210 or Echolink WX-Talk beginning
Wednesday morning. Our VoIPWX Net will activate then.

Reflector 9206 - Listen Only

Florida
IRLP Node: 4386 Jacksonville, Florida 147.2000
IRLP Node: 4530 Tampa, Florida 444.500
IRLP Node: 4629 Pensacolda Florida 145.745 (Says the node is down
currently)
IRLP Node: 4647 Clearwater Florida (Near Tampa) 443.850
IRLP Node: 4880 Tampa Florida 443.675
IRLP Node: 7260 Spring Hill, Florida 146.560

Alabama
IRLP Node: 3890 Huntsville, Alabama (Simplex)
IRLP Node: 4560 Madison, Alabama (Simplex)
IRLP Node: 4713 Scottsboro, Alabama (Simplex)
IRLP Node: 4950 Huntsville, Alabama (446.200)
IRLP Node: 4957 Scottsboro, Alabama (146.900)
IRLP Node: 7660 Mongtgomery, Alabama (446.450)

Louisiana
IRLP Node: 3416 Houma, Louisiana (Simplex)
IRLP Node: 8250 Abbeville, Louisiana (Simplex)
IRLP Node: 4269 Thinodaux, Louisiana (444.500) Says the node is
down.
IRLP Node: 4958 Baton Rouge, Louisiana (443.100) Says the node is
down.
IRLP Node: 5720 Lafayette, Louisiana (443.150)

Mississippi
IRLP node 4596 W5NRU Ellisville

Danny KD4RAA
kd4raa at voipwx.net

------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/ELTolB/TM
--------------------------------------------------------------------~->

--- IRLP-Owners YahooGroups List ---
Yahoo! Groups Links


------- End of Original Message -------


Node Owners Ivan Path Notice

Danny Musten <kd4raa@...>
 

Our net control coordinator has generated a partial list of nodes
that could be in the potential path of Ivan. We have heard from some
of these already today.

If you are (or know) the trustees of these systems or
have knowledge of other adjacent nodes in these areas,
we would appreciate you passing the word to meet us on
IRLP Reflector 9210 or Echolink WX-Talk beginning
Wednesday morning. Our VoIPWX Net will activate then.

Reflector 9206 - Listen Only


Florida
IRLP Node: 4386 Jacksonville, Florida 147.2000
IRLP Node: 4530 Tampa, Florida 444.500
IRLP Node: 4629 Pensacolda Florida 145.745 (Says the node is down
currently)
IRLP Node: 4647 Clearwater Florida (Near Tampa) 443.850
IRLP Node: 4880 Tampa Florida 443.675
IRLP Node: 7260 Spring Hill, Florida 146.560

Alabama
IRLP Node: 3890 Huntsville, Alabama (Simplex)
IRLP Node: 4560 Madison, Alabama (Simplex)
IRLP Node: 4713 Scottsboro, Alabama (Simplex)
IRLP Node: 4950 Huntsville, Alabama (446.200)
IRLP Node: 4957 Scottsboro, Alabama (146.900)
IRLP Node: 7660 Mongtgomery, Alabama (446.450)

Louisiana
IRLP Node: 3416 Houma, Louisiana (Simplex)
IRLP Node: 8250 Abbeville, Louisiana (Simplex)
IRLP Node: 4269 Thinodaux, Louisiana (444.500) Says the node is
down.
IRLP Node: 4958 Baton Rouge, Louisiana (443.100) Says the node is
down.
IRLP Node: 5720 Lafayette, Louisiana (443.150)

Mississippi
IRLP node 4596 W5NRU Ellisville

Danny KD4RAA
kd4raa at voipwx.net


Re: incoming audio problems

Dan Worley <danworley@...>
 

does the static IP address on the node computer match the address that
the router is forwarding to?

-----Original Message-----
From: ve7bas [mailto:ve7bas@rac.ca]
Sent: Tuesday, September 14, 2004 9:55 AM
To: irlp@yahoogroups.com
Subject: [irlp] incoming audio problems

I need help in troubleshooting my node. I changed my ip from dynamic
to static and since that day I am not getting any incoming audio.
I can connect to a station, the outgoing audio is ok but i cannot
hear anybody coming back. I have run the troubleshooting scripts and
it passed the test. No changes in the router with the port
forwarding. I have an echoirlp system and the echolink side is
working fine.

any ideas!!!!

Pedro
Ve7bas
irlp node #1207
echolink node# 69477




--- IRLP-Owners YahooGroups List ---
Yahoo! Groups Links


Re: incoming audio problems

David Cameron - IRLP
 

Check to make sure that neither your echolink or your IRLP are using
the DMZ of the router.

On your port forwarding page, also make sure that the ports 2074-2093
are forwarded for UDP, and NOT TCP. (although "both" works as well)

As for the packets showing on the Ref9200 monitor... Wow!? That is
really weird, as they are not even formatted packets. I hope they
arent being "reflected" :) May have to do some testing.

Amazing what you can learn when you are not paying attention. I would
be interested to know what they show up as on the debug mode of the
reflector software.

Dave Cameron
VE7LTD

--- In irlp@yahoogroups.com, "Dave Gingrich" <gingrich2@d...> wrote:

On Tue, September 14, 2004 12:23 pm, Jim WW4M said:
--- In irlp@yahoogroups.com, "Dan Worley" <danworley@c...> wrote:
does the static IP address on the node computer match the address
that
the router is forwarding to?
I've determined his IP address and port forwarding are correct
for at
least ports 15425-15427. Does the troubleshoot-irlp script detect
whether audio ports 2074-2093 are properly for UDP, or would an
improper setting for TCP pass the test?
No, troubleshoot-irlp properly tests for inbound and outbound UDP
as well.
The script sends small test packets to/from Ref9200. I see every
node
buzz across 9200 on the reflector console. It doesn't key anything
up,
but the reflector monitor sees 'em all, :) ...and no, I don't
care,
although I admit it caught me off guard the first time I noticed
the port
scan.

-Dave K9DC


Re: incoming audio problems

Dave Gingrich <gingrich2@...>
 

On Tue, September 14, 2004 12:23 pm, Jim WW4M said:
--- In irlp@yahoogroups.com, "Dan Worley" <danworley@c...> wrote:
does the static IP address on the node computer match the address
that
the router is forwarding to?
I've determined his IP address and port forwarding are correct for at
least ports 15425-15427. Does the troubleshoot-irlp script detect
whether audio ports 2074-2093 are properly for UDP, or would an
improper setting for TCP pass the test?
No, troubleshoot-irlp properly tests for inbound and outbound UDP as well.
The script sends small test packets to/from Ref9200. I see every node
buzz across 9200 on the reflector console. It doesn't key anything up,
but the reflector monitor sees 'em all, :) ...and no, I don't care,
although I admit it caught me off guard the first time I noticed the port
scan.

-Dave K9DC


Re: incoming audio problems

Jim WW4M <ww4m@...>
 

--- In irlp@yahoogroups.com, "Dan Worley" <danworley@c...> wrote:
does the static IP address on the node computer match the address
that
the router is forwarding to?
I've determined his IP address and port forwarding are correct for at
least ports 15425-15427. Does the troubleshoot-irlp script detect
whether audio ports 2074-2093 are properly for UDP, or would an
improper setting for TCP pass the test?

Jim WW4M

-----Original Message-----
From: ve7bas [mailto:ve7bas@r...]
Sent: Tuesday, September 14, 2004 9:55 AM
To: irlp@yahoogroups.com
Subject: [irlp] incoming audio problems

I need help in troubleshooting my node. I changed my ip from dynamic
to static and since that day I am not getting any incoming audio.
I can connect to a station, the outgoing audio is ok but i cannot
hear anybody coming back. I have run the troubleshooting scripts and
it passed the test. No changes in the router with the port
forwarding. I have an echoirlp system and the echolink side is
working fine.

any ideas!!!!

Pedro
Ve7bas
irlp node #1207
echolink node# 69477




--- IRLP-Owners YahooGroups List ---
Yahoo! Groups Links


incoming audio problems

ve7bas <ve7bas@...>
 

I need help in troubleshooting my node. I changed my ip from dynamic
to static and since that day I am not getting any incoming audio.
I can connect to a station, the outgoing audio is ok but i cannot
hear anybody coming back. I have run the troubleshooting scripts and
it passed the test. No changes in the router with the port
forwarding. I have an echoirlp system and the echolink side is
working fine.

any ideas!!!!

Pedro
Ve7bas
irlp node #1207
echolink node# 69477


Re: Configuring GE Master II repeater CTCSS output tone

Henry Hamblin <wb4ivb@...>
 

Greg,

Rx Mute is a decode function of the Comm-Spec Board.

The purpose of the RX Mute is to mute the receiver audio until the decoder receives the proper CTCSS. When the decode circuit receives the proper CTCSS, it changes states to "Unmute" the receive audio. There is a jumper on the Comm-Spec board (JU-7 on the TS-64) that allows you to configure the the RX Mute circuit so that it either grounds or ungrounds the receiver mute circuit to pass audio.

Henry
WB4IVB

----- Original Message -----
From: Gregory Rehm
To: irlp@yahoogroups.com
Sent: Tuesday, September 14, 2004 12:11 AM
Subject: Re: [irlp] Configuring GE Master II repeater CTCSS output tone


Wow! Thanks for the great explaination. This confirms we going the right
direction. I think that when we did the original setup, that's how we did
the hook up. Or, at least, that's what we intended to do. We're using an
SS-64 encoder as the repeater already had a decoder (don't know what it is).
We might have got the wrong line. We are successfully supressing repeater
ID but not repeater tail.

Is the white "Rx Mute" wire part of encode or decode? The problem could be
on the Rx side of the repeater.

Greg
KD7RCG
Node 3276

----- Original Message -----
From: "Henry Hamblin" <wb4ivb@charter.net>
To: <irlp@yahoogroups.com>
Sent: Sunday, September 12, 2004 7:10 PM
Subject: Re: [irlp] Configuring GE Master II repeater CTCSS output tone


>
> Greg,
>
> The concept is to let the Mastr II RUS (Receiver Unsquelched Switch) on
the Mastr II IFAS Board Pin 8 control the Comm-Spec board so that the
Comm-Spec Encode function is only present when an RUS signal is present.
Don't confuse RUS with CAS.
>
> Assuming you have the Comm-Spec board decode side wired correctly, the
Mastr II RUS (positive voltage) will only be present when a on-frequency
signal with the correct tone is present. Depending on which model Comm-Spec
board you have............the TS-64 for example, has an Orange wire that
must be grounded in order for the "Encode" to function. You could use the
RUS signal via an NPN transistor/10K resistor circuit to ground the Orange
wire. Connect RUS to the base of a 2N2222 via a 10K resistor (for current
limiting). Ground the Emitter. Connect the orange wire to the Collector.
When RUS is present forward bias is applied to the base, grounding the
Orange wire via the Emitter-Collector. Before doing this, to make sure the
Comm-Spec Decode section is wired correctly as mentioned above, measure the
voltage at RUS on the IFAS board. You should only see a Positive voltage
when an on-frequency signal with the correct CTCSS is present. If you see a
positive voltage without a CTCSS, then the Decode side is not wired
correctly. The White wire on the TS-64 is "Rx Mute", and the mute circuit
must be functioning correctly for RUS to work as described.
>
> Henry
> WB4IVB



--- IRLP-Owners YahooGroups List ---


Yahoo! Groups Sponsor
ADVERTISEMENT





------------------------------------------------------------------------------
Yahoo! Groups Links

a.. To visit your group on the web, go to:
http://groups.yahoo.com/group/irlp/

b.. To unsubscribe from this group, send an email to:
irlp-unsubscribe@yahoogroups.com

c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


Re: unable to receive echo ref

Dave Gingrich <gingrich2@...>
 

On Sep 14, 2004, at 0:19, Tony Langdon (ATC) wrote:
7740 does not key to transmit from the echo ref or other
nodes.
Have you run the irlp_troubleshoot script? Also, are you running DHCP
_behind_ the router?
Actually, the command is 'troubleshoot-irlp' But it will most likely point out the problem.

As Tony suggested, your node computer is probably behind a router, and configured to use DHCP to get an IP address. In your case, with the reboot of everything, the computer probably came up on an IP address different than where your port forwarding points. Nodes behind port forwarding routers should be configured with a static address so this doesn't happen.


=============================
Dave K9DC, stn4730, Ref9200
Indianapolis, Indiana USA
=============================


Re: which audio cards support synth?

Alan Bowker <abowker@...>
 

Run "sndconfig".

I had the same problem with the AWE64.

Alan
WA6DNR
Node 8410

--- In irlp@yahoogroups.com, WJ2W <wj2w_jordan@y...> wrote:
Hello. I have been loosing my battle with SCCW for quite a while.
Got it to "almost" work but instead of sending CW it sent "clicks"
Pretty sure my card doesn't support the synth.
I use an AWE64 ISA card.
Can anyone recommend some good (synth. compatible) sound cards
that support the synth. needed for SCCW ID script?

Thanks

Jordan Moser WJ2W



---------------------------------
Do you Yahoo!?
Shop for Back-to-School deals on Yahoo! Shopping.


Re: unable to receive echo ref

Tony Langdon (ATC) <tlangdon@...>
 

I don't know what may be wrong but maybe someone could
give me a hand. We just came through some storms and our
node 7740 does not key to transmit from the echo ref or other
nodes. This is what I checked so far, in etc hosts the IP is
correct rebooted a few times with no luck. I then did a
rc.irlp and watched the boot. all ok then I shut it down,
waited a few minutes then watched the boot, all checked OK So
this is what happens It keys the link transmitter and IDs
(plays wave file) OK I can connect and disconnect to refs and
nodes OK. but when they transmit to me the link transmitter
does not key but I can see by the flashing lights on the
router that it is receiving the audio. I can connect to 9990
and transmit, then again I can see the router blinking as the
echo is played but the transmitter does not key. I then
rebooted the modem (ADSL with a static ip) and rebooted the
router. Still nothing. This is an odd one I have not seen
before. Let me know if you might have any ideas.
Have you run the irlp_troubleshoot script? Also, are you running DHCP
_behind_ the router?


Re: unable to receive echo ref

Robert WE4B <hamradio@...>
 

Hi all,
I don't know what may be wrong but maybe someone could
give me a hand. We just came through some storms and our
node 7740 does not key to transmit from the echo ref or other nodes.
This is what I checked so far,
in etc hosts the IP is correct
rebooted a few times with no luck.
I then did a rc.irlp and watched the boot. all ok
then I shut it down, waited a few minutes then watched
the boot, all checked OK
So this is what happens
It keys the link transmitter and IDs (plays wave file) OK
I can connect and disconnect to refs and nodes OK.
but when they transmit to me the link transmitter does not key
but I can see by the flashing lights on the router that it is
receiving the audio.
I can connect to 9990 and transmit, then again I can see the
router blinking as the echo is played but the transmitter
does not key.
I then rebooted the modem (ADSL with a static ip) and
rebooted the router. Still nothing. This is an odd one I have not seen
before. Let me know if you might have any ideas.

Robert WE4B Node 7740


Re: Configuring GE Master II repeater CTCSS output tone

kd7rcg
 

Wow! Thanks for the great explaination. This confirms we going the right
direction. I think that when we did the original setup, that's how we did
the hook up. Or, at least, that's what we intended to do. We're using an
SS-64 encoder as the repeater already had a decoder (don't know what it is).
We might have got the wrong line. We are successfully supressing repeater
ID but not repeater tail.

Is the white "Rx Mute" wire part of encode or decode? The problem could be
on the Rx side of the repeater.

Greg
KD7RCG
Node 3276

----- Original Message -----
From: "Henry Hamblin" <wb4ivb@charter.net>
To: <irlp@yahoogroups.com>
Sent: Sunday, September 12, 2004 7:10 PM
Subject: Re: [irlp] Configuring GE Master II repeater CTCSS output tone



Greg,

The concept is to let the Mastr II RUS (Receiver Unsquelched Switch) on
the Mastr II IFAS Board Pin 8 control the Comm-Spec board so that the
Comm-Spec Encode function is only present when an RUS signal is present.
Don't confuse RUS with CAS.

Assuming you have the Comm-Spec board decode side wired correctly, the
Mastr II RUS (positive voltage) will only be present when a on-frequency
signal with the correct tone is present. Depending on which model Comm-Spec
board you have............the TS-64 for example, has an Orange wire that
must be grounded in order for the "Encode" to function. You could use the
RUS signal via an NPN transistor/10K resistor circuit to ground the Orange
wire. Connect RUS to the base of a 2N2222 via a 10K resistor (for current
limiting). Ground the Emitter. Connect the orange wire to the Collector.
When RUS is present forward bias is applied to the base, grounding the
Orange wire via the Emitter-Collector. Before doing this, to make sure the
Comm-Spec Decode section is wired correctly as mentioned above, measure the
voltage at RUS on the IFAS board. You should only see a Positive voltage
when an on-frequency signal with the correct CTCSS is present. If you see a
positive voltage without a CTCSS, then the Decode side is not wired
correctly. The White wire on the TS-64 is "Rx Mute", and the mute circuit
must be functioning correctly for RUS to work as described.

Henry
WB4IVB


Re: Configuring GE Master II repeater CTCSS output tone

kd7rcg
 

We're using the SS-64 Encoder on the output. There was an existing decoder
(don't know what) on the input side prior to our IRLP project. Checking to
see if the tone coming in from input transmissions is coming out the
transmit side is definitely going on our things-to-look-at-list.

Greg
KD7RCG
Node 3276

----- Original Message -----
From: "Klaus Rung" <k_rung@yahoo.com>
To: <irlp@yahoogroups.com>
Sent: Monday, September 13, 2004 5:55 AM
Subject: Re: [irlp] Configuring GE Master II repeater CTCSS output tone


Depends on which model CommSpec decoder you are using.

Is it a TS-32 or TS-64?

If the tone is present on the repeater tail then I bet
it is not working correctly for cutting out the ident
either. You were not very specific on how you wired
the cos gating to the decoder.

Also, are you using two decoders? One for ctcss and
another for tx encode? If you already have a ctcss
decoder working correctly and it was tied to the
transmitter just put a relay into the tone line that
is gated from the rx cos and away you go. Another
issue is your receiver audio must be filtered through
your ctcss decoder to strip off the tone otherwise it
will go from the receiver into the transmitter input
and add to the second decoder that is wired to the
transmitter. In other words you need a high pass
filter in the rx audio line going to your transmitter.

If it is a TS-32 make sure the decoder is transmitting
a tone continuously whether it is keyed or not. You
may have to tie a line low to do this. Next put a
normally open relay contact into the tone line wire
going to the transmitter. This will key the tone very
quickly and shut it off very quickly and should work
very well. I have a number of repeaters using that
method for a few years now very reliably. A very
simple to impliment fix.

Make sure you run pulsecheck after you have everything
wired and adjust the timing accordingly. You will find
the second number will end up to be 150 if you have
things wired correctly.

Setting up tone gating this way is not repeater brand
specific and is the same on any repeater system.

Klaus
ve3kr

--- kd7rcg <greg@turnpoint.net> wrote:

Hi All,

On node 3276, Bellingham, WA, we are trying to use a
Comspec CTCSS
encoder to put a tone on the repeater output that
follows the
repeater input so that the repeater tail and CW ID
won't be heard by
the link radio used by the node. We use a CTCSS
tone squelch on the
node link receiver.

It seems to be working fine for suppessing the CW
ID, but the tone
is present during the repeater tail.

How and where have any GE Master II repeater folk
been hooking in
tone decoders on your systems? What specific
connections are you
making?

Thanks,

Greg - KD7RCG
Node 3276
Bellingham, WA

P.S. Thanks to Dave, K9DC, for keeping us on the
right track.


=====
Best regards,Klaus Rung, VE3KR http://www.qsl.net/ve3kr




__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail



--- IRLP-Owners YahooGroups List ---
Yahoo! Groups Links






Re: 9206 activity?

Tony Langdon (ATC) <tlangdon@...>
 

www.voipwx.net for details but the net was stood down
yesterday after IVAN passed the Caymans. It will not restart
until there is another direct threat.

Too bad CO8 land is not taken into consideration as the
Western end is right in the path.
The reason Cuba isn't taken into account is that there are no VoIP nodes
there, so the likelyhood of reports is very low. HF is the medium to
service that area.


Re: Configuring GE Master II repeater CTCSS output tone

Nate Duehr <nate@...>
 

ve7ltd wrote:

I know this may sound dumb, but has anyone looked on a scope what a TS-32 looks like on the output when you toggle the power to the board on and off?

I use a selectone encoder (with the infinately variable frequency pot) and I find that just powering the whole unit on and off works fine for me. I switch the power on with the +5 volts from the tone decoder board.

Dave Cameron
I wouldn't do this with the Comm-Spec boards, because you'd lose the "reverse burst" / "squelch tail elimination" feature they have.

If you use their PTT line, they continue encoding for a slight time after the line is "unkeyed" and they do one of the two types of phase shift recognized by modern commercial gear from any manufacturer as an indication to close their audio circuits.

For most Amateur gear, it wouldn't matter, as for some reason the ham manufacturers have never seemed to catch on in their design meetings that the rest of the FM 2-way world started doing this in the 70's, but for those of us running modified commerical gear (or in many cases, just reprogrammed commercial gear with no mods), it makes things sound sooo much better.

It's also a good way to get quick, but quiet, performance out of link turnaround times for link radios.

Nate WY0X