Skip to content

Does not re-establish connection, but says it has... #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
f33d13ack opened this issue Nov 25, 2022 · 3 comments · Fixed by #64
Closed

Does not re-establish connection, but says it has... #63

f33d13ack opened this issue Nov 25, 2022 · 3 comments · Fixed by #64
Labels
bug Something isn't working

Comments

@f33d13ack
Copy link

f33d13ack commented Nov 25, 2022

This is the first version I've ever downloaded of the Windows NUT Client, so I'm a new, here.
I've currently been using an older, WinNUT 2.0.0.4a, for the last few years, which is installed as a service.

v2.2.8359.21169, Windows 10 Pro, 21H2 Build 19044.2251

If I disconnect or disable the ethernet adapter and reconnect it again, or when my VPN starts if the NUT already had an established connection,
Then, once the NUT tries to re-establish connection, and says that it HAS re-established connection... it really hasn't, and the yellow reconnection icon stays yellow (top left corner of Pic1), and also the gauges stay frozen (Pic1), and if I try to get the UPS variable at this time, it throws back an error (Pic2).
I've also tested a power failure and it does not respond, unless I click to Reconnect manually, then the power failure will trigger.

If I click to Reconnect the connection after the VPN is connected... it's fine,
If I disconnect the VPN... it's also fine, as long as I don't disconnect the ethernet connection,
If I restart the VPN... it shows the yellow reconnect icon, says it's established, but again.. it actually hasn't.

Pic1
Screenshot 2022-11-24 175902

Pic2
Screenshot 2022-11-24 180647

@gbakeman gbakeman added the bug Something isn't working label Nov 28, 2022
@gbakeman gbakeman added this to the 2.2 Stable Release milestone Nov 28, 2022
@gbakeman gbakeman linked a pull request Nov 28, 2022 that will close this issue
@gbakeman
Copy link
Contributor

Hi @f33d13ack ,

Thank you for the report. I think there may be several bugs at play here. One is that the UI was not properly synchronized with the state of the UPS when the connection is lost. Two is that a variable was left in an error state when the connection was broken. I was just testing WinNUT now and able to reproduce the issues you reported. I think I have the two primary bugs fixed now. Please download the latest debug build here and extract/run it in a temporary location, and let me know if you can still reproduce the issues here. If so, please upload a log.

@f33d13ack
Copy link
Author

f33d13ack commented Nov 30, 2022

WinNUT-Client-debugbuild-v2.2.8367.36037

Hi @gbakeman ,

Thank you! This build seems to be working as intended. I'm unable to reproduce the issue.

Question though, in the event that the network adapter bugs out and disconnects, which sometimes happens on UDP or TCP protocols in my VPN, is there a way you can add an option in WinNUT, to try to reestablish the connection indefinitely, maybe silently in the background, like every 5 or 10 seconds, rather than only 30 attempts? If I disconnect the network adapter, let WinNUT try 30 times, then reenable the adapter, I have to manually reconnect. It seems like each try only lasts a second or two, so if I'm not around on the odd occasion this might occur, it's not going to restart unless it's within those 30 attempts. Just a thought.

@gbakeman
Copy link
Contributor

Glad to hear it, thank you for reporting back!

is there a way you can add an option in WinNUT, to try to reestablish the connection indefinitely

That's a good idea, I don't see why that shouldn't be an option. I'll make a separate issue for that and see what I can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants