开云体育

Hello Darryl,

I had written the following reply but then I replied to your second email as I thought it might be a misconfiguration.? Anyway.. I held on to this email instead of deleting it and I'm glad I did.? So onward..

here is a copy of the non-working connection if someone can help:

Ok.. let's go through this packet by packet:

[0L 20:27] W8DSB>N8RDF,LRK:(SABM cmd, p=1)

GOOD:? your initiating "SABM" via a digipeater (LRK)

?Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?__|||||__

[0.4 20:27] W8DSB>N8RDF,W8LRK-5*:(SABM cmd, p=1)

GOOD: You hear your packet from the digipeater (noticed it identifying itself not as LRK but as W8LRK-5.? That's legal

Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?__||||||_

[0.4 20:27] N8RDF>W8DSB,W8LRK-5*:(RR cmd, n(r)=0, p=1)

BAD:? You didn't hear the "UA" packet via the digipeater yet.? You're system will have to retry the connection

Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?___|||||_

[0.5 20:27] N8RDF>W8DSB,W8LRK-5*:(UA res, f=1)

BAD: Here is the missing "UA" frame coming expected from the digipeater but it's coming out of order!? Are you consistently seeing this behavior?? Do you know who runs this digipeater?? If it continues doing this, it might need a reboot

Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?___||||__

[0.4 20:27] N8RDF>W8DSB,W8LRK-5*:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)Open source Winlink client - getpat.io<0x0d>

GOOD: Assuming the Linux AX.25 stack thinks the connection is open, you're sending a payload packet.? To confirm the status of the stack, you can run the netstat command (found in the in the net-tools package) in terminal window:

netstat -A ax25 -an
--
Active AX.25 sockets
Dest?????? Source???? Device? State??????? Vr/Vs??? Send-Q? Recv-Q
*????????? KI6ZHD-3?? ax0???? LISTENING??? 000/000? 0?????? 0????
*????????? KI6ZHD-2?? ax0???? LISTENING??? 000/000? 0?????? 0????
*????????? KI6ZHD-1?? ax0???? LISTENING??? 000/000? 0?????? 0????
*????????? KI6ZHD-0?? ax0???? LISTENING??? 000/000? 0?????? 0
--

Here is an example with an established connection
--
Dest?????? Source???? Device? State??????? Vr/Vs??? Send-Q? Recv-Q
AA6WK-0??? KI6ZHD-1?? ax0???? ESTABLISHED? 000/000? 0?????? 0????
*????????? KI6ZHD-3?? ax0???? LISTENING??? 000/000? 0?????? 0????
*????????? KI6ZHD-2?? ax0???? LISTENING??? 000/000? 0?????? 0????
*????????? KI6ZHD-1?? ax0???? LISTENING??? 000/000? 0?????? 0????
*????????? KI6ZHD-0?? ax0???? LISTENING??? 000/000? 0?????? 0
--

Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?__|||||__

[0.4 20:27] N8RDF>W8DSB,W8LRK-5*:(I cmd, n(s)=1, n(r)=0, p=1, pid=0xf0);FW: N8RDF<0x0d>[Pat-0.10.0-B2FHMG$]<0x0d>; W8DSB DE N8RDF (EN82cn)><0x0d>

GOOD, you've received a good payload packet from the remote station

Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?__||||||_

[0.4 20:27] N8RDF>W8DSB,W8LRK-5*:(RR cmd, n(r)=0, p=1)

[0L 20:27] W8DSB>N8RDF,LRK:(SABM cmd, p=1)

Is this a copy/paste issue?? Why is your station sending another SABM connection request?!? Is this a new connection?? We didn't see the previous connection get terminated first.? It's critical that you send the complete output *accurately* for us to have any chance to help you here.

Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?__|||||__

[0.4 20:27] W8DSB>N8RDF,W8LRK-5*:(SABM cmd, p=1)

Assuming this is a new connection attempt, this looks GOOD

Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?__|||||__

[0.4 20:28] N8RDF>W8DSB,W8LRK-5*:(UA res, f=1)

GOOD:? initial connection complete

Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?___|||||_

[0.5 20:28] N8RDF>W8DSB,W8LRK-5*:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)Open source Winlink client - getpat.io<0x0d>

GOOD: you've received a payload packet from the remote station

Digipeater W8LRK-5 audio level = 49(15/9)? ?[NONE]? ?__|||||__

[0.4 20:28] N8RDF>W8DSB,W8LRK-5*:(I cmd, n(s)=1, n(r)=0, p=1, pid=0xf0);FW: N8RDF<0x0d>[Pat-0.10.0-B2FHMG$]<0x0d>; W8DSB DE N8RDF (EN82cn)><0x0d>

GOOD: you've received a second payload packet from the remote station

So what happens after this?? Does the remote station keep retrying some specific packet?? Maybe your station keeps retrying something?? Please include those packets as well.


--David
KI6ZHD