开云体育

I'm wanting to setup a portable digipeater for when I'm at a park and want to go for a hike. I will transmit APRS from my Yaesu FT5 and have the Raspberry Pi / radio in the car digipeat it with a better antenna and a little more power than the HT. Is there a way in Direwolf to only digipeat packets to/from the callsign on my HT? I tried "DIGIPEAT 0 0 ^WIDE1-1$ ^WIDE1-1$" which works fine when I transmit with a path of WIDE1-1,WIDE2-1 on the HT. However, it also digipeats anyone else who is in earshot of my radio which I don't want since it would interfere with other digipeaters. When I had a Kenwood D710, I was able to do this no problem but I haven't figured it out on Direwolf. Any ideas? Thanks!

Stan - K9SWX

Very flexible packet filtering is possible.?
You could easily allow digipeating of packets only with your callsign as the source or message addressee.
It is explained in the User Guide.

73,
John WB2OSZ

Simple way to do it: don't use the standard WIDE1-1 and WIDE2-2 digipeat aliases. You can make up any alias you want (and use the New-N paradigm if you want), and only originating stations that specify your digipeat alias will be digipeated by your digi.

For example, Bob Bruninga WB4APR (SK) proposed state-wide digi aliases, so gerrymandered states like Maryland could cover their whole state without blanketing 10 states away in all directions. The MD7-7 alias would only be recognized by digipeaters in Maryland, so digipeaters over the state line in Pennsylvania, West Virginia, Virginia, and Delaware would not carry on.

So, for your case, let's create a digipeat alias of MINE1-1. That would be the first digi alias on your HT, and the _only_ digipeat alias recognized by the car radio setup. So your car digi would ignore everyone else using WIDE1-1 or WIDE2-2. Or you don't even need to make up an alias; just specify the callsign-SSID of your digi (ala old-style connected-mode packet) and digipeat through it that way.

So, assuming your HT's callsign-SSID is K9SWX-7 and the car is K9SWX-9, your HT digi path would be K9SWX-9,WIDE2-2.

The only problem of this is, since your digi won't recognize anyone else, it won't forward anything _to_ your HT from anyone else.

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of Stan Olson <k9swx@...>
Sent: Sunday, March 3, 2024 1:24 AM
To: [email protected]
Subject: [direwolf] Digipeat specific callsign?

I'm wanting to setup a portable digipeater for when I'm at a park and want to go for a hike. I will transmit APRS from my Yaesu FT5 and have the Raspberry Pi / radio in the car digipeat it with a better antenna and a little more power than the HT. Is there a way in Direwolf to only digipeat packets to/from the callsign on my HT? I tried "DIGIPEAT 0 0 ^WIDE1-1$ ^WIDE1-1$" which works fine when I transmit with a path of WIDE1-1,WIDE2-1 on the HT. However, it also digipeats anyone else who is in earshot of my radio which I don't want since it would interfere with other digipeaters. When I had a Kenwood D710, I was able to do this no problem but I haven't figured it out on Direwolf. Any ideas? Thanks!

Stan - K9SWX

Thanks for the info. I tried putting in "DIGIPEAT 0 0 ^K9SWX-1$" in direwolf and setting my path in the HT to K9SWX-1,WIDE2-2 but it did not digipeat it. Do I need something else in direwolf to recognize the call from the HT to digipeat it?

Digging a bit deeper, this other option using a filter looks like it is working.

DIGIPEAT 0 0 ^WIDE1-1$ ^WIDE1-1$
FILTER 0 0 b/K9SWX/K9SWX-*

Does that look right? I used WIDE1-1,WIDE2-1 in my HT's path. So far I haven't seen any other WIDE1-1 packets other than my own get digipeated through my radio. I'm not sure if I would receive messages from other parties with that filter though. I tried sending myself a message via APRS.FI with a different SSID and it wasn't digipeated. I saw it show up from the local digipeater down the road but my test digi did not digipeat it.