Testing some APRS paths here and we've noted a weird digipeating
problem. I don't think it's linux particular but I'm not 100% sure.

I can talk directly to a standard standalone digipeater called
VK3RPP-1. On the other side of town is VK3JFK, a digipeater with
an alias of WIDE with callsign substiution enabled, and another digipeater,
VK3JFK-1, with the same alias.

If I send packets via:

VK3RPP-1 VK3JFK VK3JFK-1 VK3RPP-1 it works (packet gets all the way),
VK3RPP-1 VK3JFK WIDE VK3RPP-1 it works,
VK3RPP-1 VK3JFK-1 WIDE VK3RPP-1 it works, but
VK3RPP-1 WIDE VK3JFK-1 VK3RPP-1 doesn't work (doesn't return), nor
VK3RPP-1 WIDE VK3JFK VK3RPP-1 doesn't work, nor
VK3RPP-1 WIDE WIDE VK3RPP-1.

So anywhere that I have WIDE second doesn't work. It appears that
the digipeaters do key the radio though. We don't yet know if they
actually modulate the signal. JFK and JFK-1 are both running
PacComm 5.0 TNC firmware [I think].

Anyone seen anything like this before? A couple of other stations
have used these WIDE repeaters and they work OK (and obviously they
both do in some paths -- as above). Very strange.

My local station here is running the linux AX.25 stack. (Kernel 2.2.12.)
VK3RPP-1 is running X1J4 or whatever it's called. Local packets were
generated with 'beacon'.

thanks
Hamish VK3SB
-- 
Hamish Moffatt       Mobile: +61 412 011 176     [EMAIL PROTECTED]
Rising Software Australia Pty. Ltd.    http://www.risingsoftware.com/
Phone: +61 3 9894 4788    Fax: +61 3 9894 3362    USA: 1 888 667 7839

Reply via email to