How to Prevent an Access Point from Being Marked as Having an Internet Connection

In Auvik, Access Points (APs) can sometimes appear to have an Internet connection when they actually do not. This typically occurs if Auvik detects a default route to a public IP address on the device. This article explains why this happens, how to prevent it, and limitations to be aware of.

Why Does This Happen?

Auvik determines Internet connectivity by checking for a default route to a public IP. If the following route is seen:

Then Auvik will map this as an Internet connection on the network map. This route is usually retrieved via SNMP or Login (CLI). Once detected, the AP will appear:

• On the network topology map with a globe icon.

• Under All Internet Connections on the Home Dashboard.

How to Prevent This

Option 1: Prevent Auvik from Discovering the Route

a) SNMP-Sourced Routes
If the route is returned via SNMP:

• Identify the OID supplying the default route.

• For SNMPv3, create a view that excludes this OID to restrict access.

b) Login (CLI) Sourced Routes
If the default route comes from CLI:

• Modify the CLI user profile to prevent execution of commands like show ip route.

Note: This approach depends on vendor support and may interfere with Auvik’s ability to log in and collect other data.

Option 2: Manual Deletion
If the route is already detected:

• Navigate to the All Internet Connections section on the dashboard.

• Manually delete the connection.

Option 3: Unmanage the Device
If the device doesn’t need full monitoring:

• Set the device as Unmanaged in Auvik.

• This stops SNMP polling and CLI login while retaining basic connectivity (e.g., ping).

Limitations

• SNMPv2 lacks granular access control; use SNMPv3 to limit specific OIDs.

• CLI limitations vary by vendor and could block Auvik’s login entirely.

• Unmanaging a device stops most monitoring functionality.

Preventing a device from appearing as Internet-connected requires either filtering the data Auvik can access or modifying how the device responds to queries. SNMPv3 and vendor CLI profiles offer the most control, but always consider operational impacts before applying restrictions.