Date   

setalsa for Yaesu FT-8900? #ax25 #ft-8900

Jay S
 

I am trying to use an FT-8900 and having some trouble with setup. I used the spreadsheet and got bogged down trying to use draws-manager. The manual shows data-in max input level 40mV p-p for 1200 bps and pin 5 maximum output 300 mV p-p.Spreadsheet gives PCM = -7.5, LO = -6.0 if I'm using it right.

I tried using draws-manager to set these levels. The radio transmits but the signal sounds weak/funny and never gets any response from the gateway. It can copy beacons from the gateway. I suspect there's more I need to do to make it work with the 8900. I see several users who are connected to 8900, but no details of what they had to do. This leads me to 2 questions:

- Does somebody have a working setalsa script for the FT-8900R? Or maybe confirm what settings you're using?
- I tried to set up on port udr1. The setalsa scripts all seem to assume udr0. Is there a trick I'm missing to configure udr1?

I am able to use Alinco 110 (thanks for the setalsa, Basil) on this setup with APRS and paclink-unix. I have tried plugging the 8900 into udr1 and using the Alinco settings but the results are same, even if I change the analog and digital gain in Draws manager.

Thanks,

Jay KI7JS


Re: Backups and Updates

Mike B
 

pi@draws:~/n7nix/hfprogs $ ./hf_verchk.sh -u
Update HF apps after checking version numbers.

js8call: current version: 2.1.1, installed: 2.1.1          version is current
wsjtx:   current version: 2.1.2, installed: 2.1.2          version is current
Library: libflxmlrpc IS loaded.
flxmlrpc:  current version: 0.1.4, installed: 0.1.4        version is current
fldigi:  current version: 4.1.12, installed: 4.1.12
fldigi version built (4.1.09) does not match source version (4.1.12)         version is current
flrig:  current version: 1.3.50, installed: 1.3.50        version is current
flmsg:  current version: 4.0.14, installed: 4.0.14        version is current
flamp:  current version: 2.2.05, installed: 2.2.05        version is current
fllog:  current version: 1.2.6, installed: 1.2.6        version is current
       
pi@draws:~/n7nix/hfprogs $ ./hf_verchk.sh -s
Display swap space used.
Using swap space: 245396
swap size: 1048572 1048572


Re: Backups and Updates

Basil Gunn
 

Without seeing all of your console output I can't really comment on what
went wrong in your case. I went to one of testing RPi's and did the
following & it worked successfully. It takes a while to build FLdigi &
FLrig.

I am going to guess you didn't use the latest version of hf_verchk.sh
which sets the file system swap size to something that works for the
fldigi build. It does this without requiring a reboot. From my console
output you can see that flrig & fldigi both needed updating and both
succeeded.

Send me the output of:

cd
cd n7nix/hfprogs
./hf_verchk.sh -s

This is what I did to update my HF programs

cd
cd n7nix
git pull
cd hfprogs
./hf_verchk.sh
./hf_verchk.sh -u
./hf_verchk.sh

This is my console output without the build & install output.

./hf_verchk.sh
js8call: current version: 2.1.1, installed: 2.1.1
wsjtx: current version: 2.1.2, installed: 2.1.2
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.12, installed: 4.1.09
flrig: current version: 1.3.50, installed: 1.3.49
flmsg: current version: 4.0.14, installed: 4.0.14
flamp: current version: 2.2.05, installed: 2.2.05
fllog: current version: 1.2.6, installed: 1.2.6

pi@testit2:~/n7nix/hfprogs $ ./hf_verchk.sh -u
Update HF apps after checking version numbers.

js8call: current version: 2.1.1, installed: 2.1.1
version is current
wsjtx: current version: 2.1.2, installed: 2.1.2
version is current
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
version is current
fldigi: current version: 4.1.12, installed: 4.1.09
versions are different and WILL be updated.

Install HF programs

User specified: pi
Install fldigi ver: 4.1.12

...
lots of build/install output for fldigi & flrig
...

To verify that the build & install worked.

$ ./hf_verchk.sh
js8call: current version: 2.1.1, installed: 2.1.1
wsjtx: current version: 2.1.2, installed: 2.1.2
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.12, installed: 4.1.12
flrig: current version: 1.3.50, installed: 1.3.50
flmsg: current version: 4.0.14, installed: 4.0.14
flamp: current version: 2.2.05, installed: 2.2.05
fllog: current version: 1.2.6, installed: 1.2.6

Mike B <kf5dey@gmail.com> writes:

This topic prompted me to do a software update again...

I got this in the middle of it...

fldigi: current version: 4.1.12, installed 4.1.12
fldigi version built (4.1.09) does not match source version (4.1.12)

is this an issue? Do I just ignore it? how do I get rid of the message?


Re: Backups and Updates

Mike B
 

This topic prompted me to do a software update again...

I got this in the middle of it...

fldigi: current version: 4.1.12, installed 4.1.12
fldigi version built (4.1.09) does not match source version (4.1.12)

is this an issue?  Do I just ignore it? how do I get rid of the message?


Re: DRAWS Pi HAT and GPS module for sale - $100

Ronald Clark
 

I got a DRAWs kit on backorder, waiting patiently.

KF7UVH 


-------- Original message --------
From: Bryan Hoyer <bhhoyer@...>
Date: 4/30/20 10:33 AM (GMT-08:00)
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] DRAWS Pi HAT and GPS module for sale - $100

We’re in process now will have an update Monday

On Apr 29, 2020, at 8:38 PM, Chui K9CHU <chui.muro@...> wrote:

:thumbs-up:

Same question...and dibs too.

:)

I have one on back order...

73 de K9CHU

On Wed, Apr 22, 2020, 10:01 PM Bob <625446forwork@...> wrote:
What version board is it and is it still available? Thx Bob




Re: DRAWS Pi HAT and GPS module for sale - $100

 

We’re in process now will have an update Monday

On Apr 29, 2020, at 8:38 PM, Chui K9CHU <chui.muro@...> wrote:

:thumbs-up:

Same question...and dibs too.

:)

I have one on back order...

73 de K9CHU

On Wed, Apr 22, 2020, 10:01 PM Bob <625446forwork@...> wrote:
What version board is it and is it still available? Thx Bob




Re: DRAWS Pi HAT and GPS module for sale - $100

Chui K9CHU
 

:thumbs-up:

Same question...and dibs too.

:)

I have one on back order...

73 de K9CHU

On Wed, Apr 22, 2020, 10:01 PM Bob <625446forwork@...> wrote:
What version board is it and is it still available? Thx Bob


Re: Routing to RMS gateway via digipeater with axparms? #ax25

Basil Gunn
 

This is a paclink-unix question.
Answer:

wl2kax25 -c <someRMSGateway> <someDigipeater>
wl2kax25 -c WC7EC-10 KH7RFI-7

If there are no other dash args other than -c you do not need to include it.
This will work as well.

wl2kax25 <someRMSGateway> <someDigipeater>
wl2kax25 WC7EC-10 KH7RFI-7

/Basil n7nix

Jay S <jaystagnone@gmail.com> writes:

I need to route my email through a digipeater (KH7RFI-7) to reach an
RMS gateway (WC7EC-10). I tried the following:

sudo axparms -route add> udr0 WC7EC-10 KF7RFI-7

I then created an email in mutt, and used the
command:

wl2kax25 -c WC7EC-10

At the same time I am monitoring with
listen -s in another term window. It appears that I am still trying to
connect directly to the gateway, not via the digipeater. udr0: fm
KI7JS to WC7EC-10 ctl SABM+ (repeated 7 times, then "connection timed
out" from wl2kax25)

What am I doing wrong? I suspect the route command is wrong. Or maybe I should reboot or restart ax25?

FWIW I can use the same system to connect to another gateway
directly. I can also drive to a place I can reach wc7ec and it works
OK. I can also see beacons from KF7RFI when monitoring with listen -a.

Thanks,
Jay KI7JS


Routing to RMS gateway via digipeater with axparms? #ax25

Jay S
 

I need to route my email through a digipeater (KH7RFI-7) to reach an RMS gateway (WC7EC-10). I tried the following:
    sudo axparms -route add udr0 WC7EC-10 KF7RFI-7
I then created an email in mutt, and used the command:
    wl2kax25 -c WC7EC-10
At the same time I am monitoring with listen -s in another term window. It appears that I am still trying to connect directly to the gateway, not via the digipeater.
    udr0: fm KI7JS to WC7EC-10 ctl SABM+ (repeated 7 times, then "connection timed out" from wl2kax25)

What am I doing wrong? I suspect the route command is wrong. Or maybe I should reboot or restart ax25?

FWIW I can use the same system to connect to another gateway directly. I can also drive to a place I can reach wc7ec and it works OK. I can also
see beacons from KF7RFI when monitoring with listen -a. 

Thanks,
Jay KI7JS


Re: mheard not working. Help debugging? #draws #ax25

Jay S
 

Mheard is working now on my draws system.

I had fixed the duplicate call sign in /etc/ax25/axports. However I had not rebooted. Alternatively I could have restarted ax25 service by running ax25-stop and ax25-start. Once I rebooted I got the output below.

To summarize, the original issue was that I saw no output or error message from mheard even though it was obvious that ax25 packets were being received. The problem was caused by a duplicate ssid in /etc/ax25/axports. It was fixed by editing /etc/ax25/axports and changing the second ssid (on line 6) to something different and then restarting ax25 or rebooting. The offending lines were:
    udr0        KI7JS-10            9600    255     2       Winlink port
    udr1        KI7JS-10             9600    255     2       Direwolf port  (I had to change this to KI7JS-11 to fix it)

Thanks for the help, Basil!

Jay KI7JS

pi@drawspi1:~ $ mheard
Callsign   Port    Packets   Last Heard
JUNIPR     udr0          3   2020-04-25 09:25:10
N7AWM      udr0          4   2020-04-25 09:25:00
DIXIE-1    udr0          2   2020-04-25 09:24:43
KM7LJ      udr0          2   2020-04-25 09:24:24
TROUT      udr0          1   2020-04-25 09:24:18


Re: mheard not working. Help debugging? #draws #ax25

Basil Gunn
 

You are using the default alsa settings which most likely will NOT work
for you. You need to determine your alsa settings so that your deviation is
set properly. Also which ham-made parts cable are you using?

When you have time post your output from the listen command:
use listen -a

also console output of both:

ax25-status
ax25-status -d

You previously stated you used listen -d c
In the version of listen I am using '-d' is not a valid argument.
$ listen -v
listen: 2.0.1

Thanks,
/Basil

Jay S <jaystagnone@gmail.com> writes:

Thanks!

OK, I changed the second ki7js-10 to ki7js-11. I am using the left connector, hooked up through a ham-made-parts cable to an old Alinco 110.

Here's the script output:

pi@drawspi1:~/n7nix/debug $ ./ax25-showcfg.sh

=== Display kissparms & ax25dev-parms
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
== kissparms from /etc/ax25/ax25-upd
$KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
$KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
$KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
$KISSPARMS -p ${PORTNAME_2} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
$KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY

===== ax.25 config
Found directory: /proc/sys/net/ax25/ax0
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000

Found directory: /proc/sys/net/ax25/ax1
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000

===== ALSA Controls for Radio Transmit =====
LO Driver Gain L:[-6.00dB] R:[-6.00dB]
PCM L:[-25.00dB] R:[-25.00dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]

===== ALSA Controls for Radio Receive =====
ADC Level L:[0.00dB] R:[0.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[10 kOhm]
CM L:[10 kOhm] R:[10 kOhm]

===== Port baudrate
DireWolf: udr0 speed: 1200, udr1 speed: 1200
AX.25: udr0 speed: 1200, udr1 speed: 1200

===== axports
udr0 KI7JS-10 9600 255 2 Winlink port
udr1 KI7JS-11 9600 255 2 Direwolf port

===== ax25d.conf
[KI7JS-10 VIA udr0]
NOCALL * * * * * * L
default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[KI7JS VIA udr0]
NOCALL * * * * * * L
default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

===== wl2k.conf
paclink-unix ax25 port: ax25port=udr0

pi@drawspi1:~/n7nix/debug $ mheard
Callsign Port Packets Last Heard
pi@drawspi1:~/n7nix/debug $ mheard


Re: mheard not working. Help debugging? #draws #ax25

Jay S
 

Thanks!

OK, I changed the second ki7js-10 to ki7js-11. I am using the left connector, hooked up through a ham-made-parts cable to an old Alinco 110. 

Here's the script output:

pi@drawspi1:~/n7nix/debug $ ./ax25-showcfg.sh
 
 === Display kissparms & ax25dev-parms
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
 == kissparms from /etc/ax25/ax25-upd
        $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_2} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
        $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
 
 ===== ax.25 config
Found directory: /proc/sys/net/ax25/ax0
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000
 
Found directory: /proc/sys/net/ax25/ax1
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000
 
 
 ===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-25.00dB]    R:[-25.00dB]
DAC Playback PT L:[P3]          R:[P3]
LO Playback CM  [Full Chip]
 
 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[0.00dB]      R:[0.00dB]
IN1             L:[Off]         R:[Off]
IN2             L:[10 kOhm]     R:[10 kOhm]
CM              L:[10 kOhm]     R:[10 kOhm]
 
===== Port baudrate
DireWolf: udr0 speed: 1200, udr1 speed: 1200
AX.25:    udr0 speed: 1200, udr1 speed: 1200
 
===== axports
udr0        KI7JS-10            9600    255     2       Winlink port
udr1        KI7JS-11             9600    255     2       Direwolf port
 
 ===== ax25d.conf
[KI7JS-10 VIA udr0]
NOCALL   * * * * * *  L
default  * * * * * *  - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[KI7JS VIA udr0]
NOCALL   * * * * * *  L
default  * * * * * *  - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
 
 ===== wl2k.conf
paclink-unix ax25 port: ax25port=udr0

pi@drawspi1:~/n7nix/debug $ mheard
Callsign   Port    Packets   Last Heard
pi@drawspi1:~/n7nix/debug $ mheard
 
 


Re: mheard not working. Help debugging? #draws #ax25

Basil Gunn
 

Can anyone suggest a few troubleshooting steps I can take? Thanks.
Look at file: /etc/ax25/axports and fix your duplicate call sign
problem.
Which DRAWS connector are you using? Left connector corresponds to
device udr0.

Tune your radio to the 2M APRS frequency, 144.390 so you will have
traffic.

Run this script and copy the console output in an email.
cd
cd n7nix/debug
./ax25-showcfg.sh

/Basil n7nix


Jay S <jaystagnone@gmail.com> writes:

Mheard prints nothing except a header with "Callsign Port Packets Last
heard". There are no error messages. I looked
at/var/ax25/mheard/mheard.dat and it is a zero-length file.

I think ax25 is otherwise working. I can use beacon or listen on the
APRS frequency, and see packets coming in. I can send APRS beacons
from another radio and see them displayed with listen -d c. I get a
message as follows when I run listen: "axconfig: duplicate callsign
KI7JS-10 in line 6 of axports file" but it shows traffic coming in
from the radio.

Can anyone suggest a few troubleshooting steps I can take? Thanks.


mheard not working. Help debugging? #draws #ax25

Jay S
 

Mheard prints nothing except a header with "Callsign   Port   Packets    Last heard". There are no error messages. I looked at /var/ax25/mheard/mheard.dat and it is a zero-length file.

I think ax25 is otherwise working. I can use beacon or listen on the APRS frequency, and see packets coming in. I can send APRS beacons from another radio and see them displayed with listen -d c. I get a message as follows when I run listen: "axconfig: duplicate callsign KI7JS-10 in line 6 of axports file" but it shows traffic coming in from the radio.

Can anyone suggest a few troubleshooting steps I can take? Thanks.


Re: DRAWS Pi HAT and GPS module for sale - $100

Bob
 

What version board is it and is it still available? Thx Bob


Re: N1MM network mode, Field Day and TCP/IP over AX.25

David M
 

The current ARRL Field Day rules don't support a Class A club group outside of a 1000 foot diameter circle. 


Re: N1MM network mode, Field Day and TCP/IP over AX.25

Eric Grumling
 

>Does this sound like HAMwan @ 9600 baud?
>What am I missing?

That's basically what I'd like to try. We're a little too spread out and too many hills to effectively build a pure HSMM-MESH style network but maybe have elements of that too. Pretty much anything that will work. I know most of the members have 9600 baud capable radios, many have an extra Raspberry Pi (or 4) and some have 3 GHz data radios. Between all that we should be able to cobble together some sort of WAN. I'm also looking at 900 MHz telemetry radios (56Kbps) borrowed from the drone world, but that might be even more difficult since I think they're set up for point to point and limited to 1 Watt LOS.


Re: N1MM network mode, Field Day and TCP/IP over AX.25

Eric Grumling
 

There's some discussion about modifying the rules for this year due to the unprecedented situation. In a normal year the club has 3 stations + GOTA/Satellite and schedules operators to run 24X7. I think the idea being floated is that we'd operate under the club call for a scheduled time from our personal station, so this might all be more trouble than it's worth. But just trying to see what's possible since I've been asked to handle the network piece of things.


Re: N1MM network mode, Field Day and TCP/IP over AX.25

Andrew P.
 

Wouldn't that kind of networking violate the Field Day rules requiring all stations be within a 1000-foot circle?


-------- Original message --------
From: Eric Grumling <eric@...>
Date: 4/19/20 14:36 (GMT-05:00)
To: udrc@nw-digital-radio.groups.io
Subject: [draws and udrc] N1MM network mode, Field Day and TCP/IP over AX.25

Our club is looking at different options for this year's Field Day since we have no intention of collecting at our usual 3A campsite. Most of us will probably be operating from home using our own callsigns, but there's some discussion of using N1MM's network mode and forming a multi-user multi-station group using the club call. I'm pretty well versed in networking N1MM on a LAN, and can probably get a VPN set up (to simplify setup for non-network savvy members) for everyone to use. However it might be interesting to see what might be possible using all radio instead of Internet and VPN tunnels. The club repeater sites are connected via a 3GHz WAN that could also be utilized if members have direct LOS with the repeater sites (not many do). 

With that in mind, what is the possibility of running 9600 baud TCP/IP using a Raspberry Pi and UDRC/soundcard modem? That way we could keep things all radio and maybe get some infrastructure built for longer term projects. I'll have to see how much network traffic is generated by N1MM of course, but the idea would be similar to a Cradlepoint style cellular modem, where the logging PC could join a WiFi hotspot or Ethernet port on the Pi, which would then act like a router. Would JNOS or Direwolf do this? Ideally I'd build a standard image for the club, and probably build a few stations too. Club members who want to join the network would need to supply a 70 CM radio with 9600 baud input and we'd probably have to set nodes at the repeater sites.

Good idea or waste of time?


Re: N1MM network mode, Field Day and TCP/IP over AX.25

Basil Gunn
 

With that in mind, what is the possibility of running 9600 baud TCP/IP
using a Raspberry Pi and UDRC/soundcard modem?
Yes lately we have been testing the 9600 baud packet part a great deal &
it works very well.

the logging PC could join a WiFi hotspot or Ethernet port on the Pi,
which would then act like a router. Would JNOS or Direwolf do this?
Since the udrc/DRAWS has is enumerated as network devices (AX0 & AX1) it
should be possible. I am not interested in using JNOS.

I'll start playing with this in my copious amounts of socially separated
time. :)

What exactly is your criteria for success. Ping'ing each station? Fill
in your vision a little more.

Does this sound like HAMwan @ 9600 baud?
What am I missing?

/Basil n7nix


Eric Grumling <eric@grumling.com> writes:

Our club is looking at different options for this year's Field Day since we have no intention of collecting at our usual 3A campsite. Most of us will probably be operating from home using our own callsigns, but there's some discussion of using N1MM's network mode and forming a multi-user multi-station group using the club call. I'm pretty well versed in networking N1MM on a LAN, and can probably get a VPN set up (to simplify setup for non-network savvy members) for everyone to use. However it might be interesting to see what might be possible using all radio instead of Internet and VPN tunnels. The club repeater sites are connected via a 3GHz WAN that could also be utilized if members have direct LOS with the repeater sites (not many do).

With that in mind, what is the possibility of running 9600 baud TCP/IP using a Raspberry Pi and UDRC/soundcard modem? That way we could keep things all radio and maybe get some infrastructure built for longer term projects. I'll have to see how much network traffic is generated by N1MM of course, but the idea would be similar to a Cradlepoint style cellular modem, where the logging PC could join a WiFi hotspot or Ethernet port on the Pi, which would then act like a router. Would JNOS or Direwolf do this? Ideally I'd build a standard image for the club, and probably build a few stations too. Club members who want to join the network would need to supply a 70 CM radio with 9600 baud input and we'd probably have to set nodes at the repeater sites.

Good idea or waste of time?

601 - 620 of 5335