Re: Headaches with direwolf + linpac
|
What does 'callsign+SSID' mean?? In my previous experience, I just knew
about callsigns, and the number at the end(e.g. n8ssw-1 usually was the
mailbox) which I always assumed was just a different radio(or service)
being operated under the same callsign.
The number at the end is referred to as the SSID. So, 'Callsign-SSIB" in your example would be: ? Callsign: N8SSW??? and SSID of 1 (or -1).
What does 'DIGI addressing' mean?
DIGI (digipeating) is directed through a couple of ways, depending on the packet software you are using. Several use what they call 'PATH' elements (most APRS applications will have settings for PATH1, PATH2, ...) In the example direwolf.conf file you will see a line of PBEACON delay=1? every=30 overlay=S symbol="digi" lat=42^37.14N long=071^20.83W power=50 height=20 gain=4 comment="Chelmsford MA" via=WIDE1-1,WIDE2-1
In this case the DIGI elements would be WIDE1-1 and WIDE2-1. To directly address a path DIGI you would set this to the CALLSIGN-SSID of the known path element you want to use.? An example for my area using a local known DIGI that I am sure I can hit from my station would be: PBEACON every=10 overlay=1 symbol="house" lat=42^09.35N long=083^46.30W comment="Saline MI Testing Ch1" via=CHLSEA, WIDE2-1
NOTE: CHLSEA has no SSID (also known as -0 zero)
Also the distinction between connected session requests and packet
digipeat requests is foreign to me.? What I always did in the past was
connect to a digipeater then connect to something else using the
interface of the digipeater. This was actually called NODE jumping in the old packet references.? A node was a connected mode between 2 station, where DIGI (digipeating was a connected mode - end-to-end).?
As an example, my connecting to W8UM through CHLSEA by each method would be something like this: DIGI? (note: commands are not literal since they would depend on the application in use)
?? C W8UM via CHLSEA The path would be that CHLSEA would hear my packet, and pass it on in the 'hopes' that W8UM could hear it. The ACK would be sent from W8UM back to my station (almost definitely through CHLSEA), but CHLSEA would only pass it along.? The 2 ends are communicating with the DIGI only passing the packet without action.
NODE? (note: CHLSEA probably doesn't really exist, but using the example of the KPC NODE if it did exist)
?? C CHLSEA-8 ?? CHLSEA would reply 'connected' to the CHLSEA node and give me a new prompt for next action ?? C W8UM ?? W8UM would reply 'connected' to the W8UM and give me a new prompt for next action
The big difference is that when W8UM replied, CHLSEA-8 would receive the packet and make sure it was 'whole' (typically through some checksum or other means) then ACK the packet back to W8UM that it was received, then pass it along to my station until ACK was received or timed out.? The NODE plays a bigger role in the passing of traffic in this setup.
I would agree with your assessment of the 2 possible reasons. If you don't know whether the station accepts 'Connects', then you will get very frustrated trying to. I'd suggest leave Direwolf in listen mode for some time with an MHEARD list collecting calls and see what callsigns you can hear direct or 'at all', then contact one of them to see about a test.
|
