Do not show OpenVPN tunnel interfaces in DHCP/DNS network scan

[cotosso]

Description

In the DHCP and DNS page, under the Scan network tab, the UI proposes OpenVPN tunnel interfaces among the networks that can be scanned.

OpenVPN tun interfaces operate at Layer 3, while the network scan is based on ARP and therefore works at Layer 2.

For this reason, scanning an OpenVPN tun interface is not meaningful and can be misleading for the user.

Steps to reproduce

1. Configure an OpenVPN tunnel using a tun interface
2. Open the DHCP and DNS page
3. Select the Scan network tab
4. Check the list of interfaces/networks available for scanning
5. Notice that the OpenVPN tunnel network is proposed

Actual behavior

OpenVPN tun interfaces are displayed as valid targets for the ARP-based network scan

Expected behavior

OpenVPN tun interfaces should not be displayed among the available networks for the ARP scan.
Only interfaces/networks where a Layer 2 ARP scan is applicable should be proposed

Components

NethSecurity 8.8.0

[Tbaile]

QA: check that the issue is not reproducibile.

Image

[m-dilorenzi]

1. OpenVPN Server tunnel configured

2. OpenVPN Client tunnel configured (both manual and imported)

3. WireGuard Server tunnel configured

4. Check that the VPN tunnels are not shown in the Network > DNS and DHCP > Scan Network section

Verified.