Wireguard public IP check: Fail silently if IP cannot be resolved

[Tbaile]

Steps to reproduce

• Configure NethSecurity wihtout DNSs.
• Attempt to install or configure a new Wireguard instance.

Expected behavior

• If NethSecurity cannot determine its public IP during Wireguard configuration (e.g., due to DNS resolution failure), it should fail silently or provide a non-blocking warning. The process should not show an error or block installation.

Actual behavior

• When the firewall cannot resolve resolver1.opendns.com to determine its public IP, an error is shown, even if the rest of the configuration is valid and DNS settings eventually work after editing resolv.conf.
• This may occur even when public DNS like 8.8.8.8 is correctly set, causing confusion during setup.
• The process should be more robust: if unable to detect the public IP via DNS, it should continue and only log a warning or fail gracefully.

Components

• ns-api <= 3.4.0

See also

https://community.nethserver.org/t/wireguard-error-on-nethsecurity-8-7-1/26641/12

[Tbaile]

The issue is present even with OpenVPN, since the function outputs to stdout and the go daemon picks it up and fails to decode it.

Culprit: https://github.com/NethServer/python3-nethsec/blob/a2c084a3cde743d4b4cd8a81a43136dd3150f621/src/nethsec/ovpn/__init__.py#L66

https://helpdesk.nethesis.it/a/tickets/196898

[Jhonraushan]

Hey, when Nethsecurity release a Wireguard Road Warrior features ??