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
When configuring wireguard as a server the wireguard port is not opened so a user has to go to the firewall page and open for example 58120. It would be better if we did this out of the box, but as the dialog is for configuring a client/server we don't want to always open the wireguard port.
Note that routing masquerading might need to be enabled firewall-cmd --permanent --zone=public --add-masquerade. Which the Firewall page might not support showing / setting. (This needs research) .
The text was updated successfully, but these errors were encountered:
Page: "Network"
When configuring wireguard as a server the wireguard port is not opened so a user has to go to the firewall page and open for example 58120. It would be better if we did this out of the box, but as the dialog is for configuring a client/server we don't want to always open the wireguard port.
Note that routing masquerading might need to be enabled
firewall-cmd --permanent --zone=public --add-masquerade
. Which the Firewall page might not support showing / setting. (This needs research) .The text was updated successfully, but these errors were encountered: