You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2020. It is now read-only.
A user in the Discord mentioned that Rainway still UPnP forwards the Wake-On-Lan port: UDP 9. Rainway removed Wake-On-Lan support in 1.0 because it didn't work for most users. It would be a good idea to stop forwarding this port since it's not used and some users might think of it as a security risk.
The text was updated successfully, but these errors were encountered:
Agreed. In the mean time, users can use Windows Firewall to create an
inbound rule that blocks udp port 9. Will provide visual tutorial upon
request. Just mentioned me in a comment.
On Mon, Apr 22, 2019, 5:06 PM JTTM ***@***.***> wrote:
A user in the Discord mentioned that Rainway still UPnP forwards the
Wake-On-Lan port: UDP 9. Rainway removed Wake-On-Lan support in 1.0 because
it didn't work for most users. It would be a good idea to stop forwarding
this port since it's not used and some users might think of it as a
security risk.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#328>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABVT472QGKYG6T7HGPVNFQTPRYSG7ANCNFSM4HHSVWTA>
.
A user in the Discord mentioned that Rainway still UPnP forwards the Wake-On-Lan port: UDP 9. Rainway removed Wake-On-Lan support in 1.0 because it didn't work for most users. It would be a good idea to stop forwarding this port since it's not used and some users might think of it as a security risk.
The text was updated successfully, but these errors were encountered: