Previously, for an incoming node connection that was done as permanent from the far end, if I were to disconnect that node from the near end, the node would remain disconnected.
However, one of our users is noticing that now when we initiate the permanent disconnect via allmon3 web interface in the same scenario above, the far end node will re-connect in a short number of seconds.
What is the expected behavior? The idea is if we disconnect a node, it should remain that way (which is what used to happen I thought).
Out of curiosity, do you know if that happens with remote ASL3 nodes, or HamVoIP? I noticed the same behavior specifically with HamVoIP nodes.
There is a difference in how HamVoIP, based on old app_rpt code and protocol, handles disconnects, which is something that KC1FSZ and I ran into when debugging his ampersand-asl parrot server.
Previously, for an incoming node connection that was done as permanent from the far end, if I were to disconnect that node from the near end, the node would remain disconnected.
However, one of our users is noticing that now when we initiate the permanent disconnect via allmon3 web interface in the same scenario above, the far end node will re-connect in a short number of seconds.
What is the expected behavior? The idea is if we disconnect a node, it should remain that way (which is what used to happen I thought).
I can tell you there's no issues with disconnecting between two ASL3 nodes. If you have Node 1 connect permanently to Node 2, and then Node 2 sends either a ilink 1 or link 11 (disconnect and permanent disconnect respectively) Node 1's connection stays down. So this isn't a generalized problem with ASL.
Do you happen to know if the end has a cron job or a timer or something that's forcing the reconnection? That's what I've seen before - some people following misguided information online about always forcing a reconnection outside of app_rpt.
I have full access the hamvoip node mentioned, and many others that connect that run hamvoip, and several others that are ASL3 nodes. I haven't tried this on all of them, but batting 3 for 3 at the moment hmm.
So, to be clear, you have HamVOIP nodes that are making permanent connections (ilink 13) to a node running ASL3. Then from the ASL3 you're sending a disconnect (what kind?). The link to the HamVOIP node drops and then the HamVOIP node is reconnecting?
I send permanent disconnects. I swear in the past this would kick them off and stay off until we reconnect manually...another control operator on our hub mentioned the disconnects were not working but had in the past.
So you have other ASL3 nodes that are making a permanent connection to your hub, you're sending permanent disconnect to them, and then ASL3 nodes are rejoining? What version?
You arerunning 3.10.5 which has known issues with the disconnect not being sent properly, Like I said earlier this has already been addressed in the current beta.
|