-
|
after connecting to COOL via KJOHN, I'm unable to establish a new direct connection to COOL, even after clearing the "Via:" field, it still tries to connect via KJOHN? In fact, I cannot only clear the Via field, I'm unable to change it, it continues to use KJOHN even if I set it to KBERR. Opening a second tab and making a new connection via KBERR, also uses KJOHN still. I need to quit the app to reset the "via" field? curiously, |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
Is that connection a vanilla AX.25 session or a NETROM session? Technically speaking, COOL is a NETROM ALIAS yet KJOHN is a Ka-Node which is only supports AX.25 (no NETROM). |
Beta Was this translation helpful? Give feedback.
-
|
COOL supports both ax25/repeating and netrom, so i'm not sure how to answer that. network and transport layers. I guess the better question is "how do I change the routing" in the connection dialogue? it always uses the first route i chose. |
Beta Was this translation helpful? Give feedback.
-
|
I'm guessing you're using Paracon together with Direwolf as your AGWPE server. There is a known issue with Direwolf where it does not clean up properly after a connection is made and then closed via AGWPE, leading to exactly the kind of behaviour you're seeing. You can read about the gory details in this comment if you're interested. I am currently working on a patch for Direwolf to resolve this, so hopefully it will be fixed soon. In the meantime, unfortunately, the only workaround is to quit and restart Paracon (or Direwolf). When an AGWPE client, like Paracon, goes away entirely, Direwolf does clean up all connection data associated with that client, but currently that's the only time it will clean it up. |
Beta Was this translation helpful? Give feedback.
-
that's exactly right, confirmed, thank you! |
Beta Was this translation helpful? Give feedback.
-
|
A patch to resolve this issue is now in the Direwolf source tree. If you build your own Direwolf from source, you can pick up the latest code from the dev branch and rebuild, and you should no longer need to restart Paracon to change the Via field. |
Beta Was this translation helpful? Give feedback.
-
|
fantastic - thanks! (and thanks to John). Everyone needs to recompile direwolf with Debian Trixie anyhow (they trashed the gpio API ... again) |
Beta Was this translation helpful? Give feedback.
-
|
For those who prefer not to build their own, Direwolf 1.8 Beta is now available. |
Beta Was this translation helpful? Give feedback.
I'm guessing you're using Paracon together with Direwolf as your AGWPE server. There is a known issue with Direwolf where it does not clean up properly after a connection is made and then closed via AGWPE, leading to exactly the kind of behaviour you're seeing. You can read about the gory details in this comment if you're interested.
I am currently working on a patch for Direwolf to resolve this, so hopefully it will be fixed soon. In the meantime, unfortunately, the only workaround is to quit and restart Paracon (or Direwolf). When an AGWPE client, like Paracon, goes away entirely, Direwolf does clean up all connection data associated with that client, but currently that's the only time …