-
Notifications
You must be signed in to change notification settings - Fork 637
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
GUACAMOLE-1686: Make WOL functionality capable of testing connectivity to the server. #470
Conversation
9dbf171
to
d870460
Compare
d870460
to
00307b3
Compare
00307b3
to
1a86f0e
Compare
1a86f0e
to
8e2c677
Compare
3cdc2df
to
618201b
Compare
Thanks for the PR. I gave it a try after merging it with master but can't seem to get my VNC connection to work as designed. It seems as though the guacd thread stops immediately after sending the WoL packet, possibly after calling
If I set wol-wake-time to 0 which (which bypasses the call to |
Just a quick update -- the segfault comes from |
Thanks, @kohrar! I suspect that after I converted the |
618201b
to
1f26e94
Compare
Apparently I had already fixed this in my git code, but not pushed it 🤦. Should be fixed, now. |
For RDP connection "guac_socket_tcp_connect" don't work. Function "guac_wol_wake_and_wait" allways wait "wait_time" seconds. I found error. Function guac_itoa for port number "3389" return 338. Correct text for guac_itoa: int guac_itoa(char* restrict dest, unsigned int integer) {
} |
1f26e94
to
e2e56fb
Compare
…nd_wait function.
e2e56fb
to
e214ad4
Compare
@jmuehlner Any further changes that need to be made on this one? |
I don't have any other changes.
С наилучшими пожеланиями,
Николай В.Степин
Директор информационной службы
ООО "Декор"
<http://www.evroplast.ru/> www.evroplast.ru
***@***.***> ***@***.***
+7(495) 789-6270 д.3108
Post hoc, non est propter hoc.
From: Virtually Nick ***@***.***
Sent: Wednesday, May 22, 2024 5:01 AM
To: apache/guacamole-server
Cc: NickVStepin; Comment
Subject: Re: [apache/guacamole-server] GUACAMOLE-1686: Make WOL functionality capable of testing connectivity to the server. (PR #470)
@jmuehlner <https://github.com/jmuehlner> Any further changes that need to be made on this one?
—
Reply to this email directly, view it on GitHub <#470 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMQZH7YYYEP33K3QPH7H26DZDP37LAVCNFSM6AAAAABBF2OEDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRTG4ZTINBZG4> .
You are receiving this because you commented. <https://github.com/notifications/beacon/AMQZH725DCTIGQ3UVFFED7DZDP37LA5CNFSM6AAAAABBF2OEDKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT6SWO6C.gif> Message ID: ***@***.***>
|
Nope, looks reasonable to me. |
This PR adds to the Wake-on-LAN functionality, implementing a new function that checks the connection to the destination server both before sending the WOL packet and, again, after sending the packet. If the host responds before sending the WOL packet, there is no need to actually send the WOL packet. If the packet does get sent, then the function will attempt to connect, then wait for the specified time period and then re-try the connection.
As a by-product of this implementation, I've also added a couple of other things: