Norton 360’s VPN sensing a Public Network LAN - but I’m in a residence with no LAN

PurpleOrange · May 4, 2026, 4:28pm

Background:

Live in a condo. Rent cable internet from a reseller that runs its service over a primary vendor’s lines.

I wire my computer through a CBN model 8000 modem to the wall. Don’t use wifi, just wired in; my preference. And, I am not using the TP Link Deco router the reseller provided because it just sets up as wifi, and I was having issues with the wifi.

Issue:

Through the Norton 306 App’s Privacy / Secure VPN / Settings / View List the VPN is sensing a public LAN with a specific name. “LAN 8A4445”. It doesn’t even look like machine language. It’s name looks like some one set it up and named it. Norton VPN is suggesting that since it is public, that I can change it to private. Which I am not going to do, because that reduces the security on something I do not recognize. I am in a condo building. There is no central LAN.
What’s going on?

bjm · May 4, 2026, 4:51pm

Nothing “mystical” is happening—this is almost certainly just how your Windows network stack (and your modem/ISP setup) is being identified and labeled, not evidence of someone else’s LAN you’re connected to.

Here’s what’s likely going on under the hood:

1) That “LAN 8A4445” name isn’t human-made

Windows will auto-generate network names when it can’t clearly identify the network. The format you’re seeing—LAN + a short hex-like string—is typical of:

a network signature / ID hash

derived from things like MAC address, gateway, or DHCP info

So while it looks like something someone named, it’s usually just Windows giving a unique label to “this specific network I’ve seen before.”

2) Why it’s showing as “Public”

Windows classifies networks as:

Public (untrusted)

Private (trusted, like your home LAN)

Because you’re:

plugged directly into a modem (CBN 8000)

not behind your own router doing NAT

…your computer is effectively sitting closer to the ISP’s network edge, not a private home LAN.

So Windows/Norton see:

“This looks like a shared or external network → treat as Public”

That’s actually the correct and safer classification.

3) Why Norton VPN is flagging it

The Norton app (Norton 360) is just reading Windows’ network profile and saying:

“Hey, this is Public. You could mark it Private.”

But in your setup:

Do NOT change it to Private

Your instinct is right—leave it as Public

4) Condo + reseller setup matters

In multi-unit buildings with a reseller:

You may be on a shared upstream infrastructure

Even if you’re wired directly, the ISP may be:

using shared segments

assigning IPs in a way that doesn’t look like a typical home router network

That can make your connection look like a “LAN” even though you don’t control it.

5) Why you’re seeing a “LAN” at all

Even with just a modem, your PC still forms a logical “local network” with:

your gateway (ISP equipment)

possibly other devices upstream (logically—not directly accessible)

Windows labels that relationship as a LAN—even if it’s not your private home network.

The key point

What you’re seeing:

is normal

is auto-generated

does NOT mean someone named a network inside your condo

One thing to double-check (worth doing)

Just to be thorough, you can confirm what Windows thinks:

Open Command Prompt

Run:
ipconfig /all
Look at:

Default Gateway

DHCP Server

IPv4 Address

If you see:

a public IP directly on your PC → you are definitely not behind a private LAN

a 192.168.x.x / 10.x.x.x / 172.16–31.x.x → there is some NAT upstream

Subtle but important security note

Right now, without using that TP-Link router:

your machine is more exposed than a typical home setup

A router (even wired-only use) gives you:

NAT firewall isolation

control over your own private LAN

cleaner network identification

You don’t have to use Wi-Fi at all—just:

disable Wi-Fi on the router

use it as a wired firewall layer

Bottom line

“LAN 8A4445” = auto-generated network ID, not a neighbor’s custom network

Public classification = correct for your setup

Norton is being generic, not insightful here

Your current topology (modem → PC) explains everything you’re seeing

macOS

What Norton is showing you is confusingly worded—but it doesn’t mean there’s a mysterious shared condo LAN you’ve joined.

What “LAN 8A4445” actually is (on macOS)

On macOS, network services (like Ethernet) get:

a service identifier

sometimes a system-generated name when no friendly name exists

Norton 360 is simply surfacing that identifier and labeling it as a “LAN.” The 8A4445 part is almost certainly a hex-style ID, not something a human named.

So think of it as:

“This specific network interface + network signature”
—not an actual, user-created LAN.

Why it says “Public”

Same principle as on Windows, but handled by macOS:

macOS treats a network as “untrusted” when:

you’re directly connected to upstream infrastructure

there’s no clearly defined private router boundary

Since you are:

plugged into a modem (CBN 8000)

not behind your own router

your Mac is effectively sitting on what looks like an external/shared network, even inside your condo.

So Norton interprets that as:

“Public network → be cautious”

That’s correct behavior.

Why this happens in your specific setup

Your topology is:
Wall jack → ISP/reseller network → modem → your Mac
Without a router in between:

there’s no private LAN created by you

your device is part of a provider-managed network segment

Even if you can’t see other devices, the system still treats it like:

“not a private, trusted home network”

Important: This does NOT mean

There’s a condo-wide LAN you’re unknowingly on

Someone named a network “LAN 8A4445”

You’re being bridged into neighbors’ devices

It’s just a label + classification, not a discovery of other users.

Should you change it to “Private”?

No—you’re right not to.

Leaving it as Public:

keeps stricter firewall behavior

avoids trust assumptions about a network you don’t control

The subtle security reality (worth knowing)

Right now, your setup lacks something most home networks have:

a router doing NAT/firewalling

Even if you never use Wi-Fi, a router gives you:

isolation from the ISP’s layer

a clearly defined private LAN

fewer “public network” flags from security tools

You could:

use that TP-Link Deco

disable Wi-Fi entirely

use it purely as a wired firewall/router

Bottom line

“LAN 8A4445” = auto-generated network identifier

“Public” = correct classification for your direct-to-modem setup

Norton isn’t detecting a hidden LAN—it’s just labeling your connection

AI sourced content may make mistakes
Caveat: I’m not Mac

PurpleOrange · May 4, 2026, 4:59pm

Thank-you very much for taking the time to explain. You effort is very much appreciated.

Crikey, just got a 403 error trying to hit “Reply”. Trying again.

bjm · May 4, 2026, 5:01pm

macOS

What you’re seeing as “LAN 8A4445” is not a separate or shared condo network, and it’s not something another user named.

In Norton 360 on macOS, that label is simply an internal identifier for your current network connection. The “8A4445” portion is most likely derived from hardware or network parameters (for example, part of a MAC address or a system-generated ID), which is why it looks semi-random but still readable.

The key detail in your setup is this:

You are connected directly to your modem / wall connection and not using a router

Because of that:

Your computer is not on a private home LAN

It is effectively connected to your ISP/reseller’s upstream network

macOS treats that type of connection as untrusted (Public)

Norton is simply reflecting that and giving it a generic “LAN” label.

So to address your concerns directly:

This does not indicate a shared condo LAN

It does not mean you’re connected to neighbors’ devices

The name was not manually created by someone

Leaving it set as Public is the correct and safer choice

If you were to place a router between your modem and computer (even with Wi-Fi disabled), your system would then sit behind a true private LAN, and this would likely appear differently.

AI sourced content may make mistakes
Caveat: I’m not Mac

SoulAsylum · May 5, 2026, 1:00am

All: ANOTHER generalized AI response states the following on this issue. Just posting as a coin flip for review:

AI Overview

Based on network identification patterns, LAN 8A4445 likely refers to a Locally Administered Address (LAA) or a randomized, virtualized hardware address on a Local Area Network. It is not a manufacturer-burned-in MAC address, but one assigned by software. [1, 2]

Here is the breakdown of what this means on a Mac:

What is a “LAN 8A4445” Address?

Locally Administered Address (LAA): This indicates that a software program or network administrator has overwritten the original hardware address of the network interface card (NIC).

Virtual Interface: It is commonly associated with Virtual Machines (like VMware, Parallels), Virtual Private Networks (VPNs), or Docker containers.

Private Wi-Fi/Randomization: Modern macOS versions use randomized MAC addresses to prevent tracking. [1, 2, 3, 4, 5]

Why is it appearing on your Mac?

Security Feature: Your Mac (or iPhone) may be using a private, randomized address to connect to a Wi-Fi network.

VPN/Network Software: If you use VPN services, specifically global-protect or corporate VPNs, they often create virtual adapters with these types of addresses.

Virtual Machine (VM): You are likely running software that virtualizes networking, such as Docker, VMware, or Parallels, which requires its own unique MAC address for the virtual network bridge. [1, 2, 3, 4]

How to check/fix it on Mac

If this address is causing network conflicts (e.g., “self-assigned IP” errors), you can check the status of your network: [1]

Go to Apple Menu > System Settings > Network.

Select your network service (Wi-Fi or Ethernet).

Click Details > Hardware to see the actual MAC address assigned to that interface. [1, 2]

If it is caused by private address randomization on a trusted home network, you can disable it in the Wi-Fi settings for that specific network. [1]

Regards,
SA

bjm · May 8, 2026, 7:42pm

Hello @PurpleOrange
Care to share your progress

PurpleOrange · May 12, 2026, 8:41pm

Thankyou. I set up the router and am running through that instead of directly through the modem. Norton 360 only identifies the router network name now. I don’t know if it solved anything or not beyond the router. I did just discover a bank account was locked down by their Fraud team, due to failed repeat hacking attempts 5 days before my above post. I’d been having a lot of device issues.

Have installed, reinstalled, reset and set up the router again and things appear fine with the exception of Norton Private browser asking me to allow it to connect to bluetooth again today. (I was getting this before with out the router set up as well, but am now running through the router) I don’t believe Norton Private Browser has capacity to connect to bluetooth, so the pop-up message doesnt make sense.

t

bjm · May 12, 2026, 8:46pm

PurpleOrange:

Thankyou. I set up the router and am running through that instead of directly through the modem. Norton 360 only identifies the router network name now. I don’t know if it solved anything or not beyond the router. I did just discover a bank account was locked down by their Fraud team, due to failed repeat hacking attempts 5 days before my above post. I’d been having a lot of device issues.

Have installed, reinstalled, reset and set up the router again and things appear fine with the exception of Norton Private browser asking me to allow it to connect to Bluetooth again today. (I was getting this before with out the router set up as well, but am now running through the router) I don’t believe Norton Private Browser has capacity to connect to Bluetooth, so the pop-up message doesn’t make sense.

Hello @PurpleOrange
Care to share a screen capture. “Norton Private Browser asking me to allow it to connect to Bluetooth”

__________________________________________________________________
===============================================================

I checked my Norton Private Browser and could not find a dedicated Bluetooth settings entry either under Additional Permissions or by searching for “Bluetooth” in Settings.

However, Additional Permissions does include entries such as Motion Sensors, USB Devices, MIDI Devices, and HID Devices, which indicates Norton Private Browser still exposes several Chromium hardware/device permission categories.

Since Norton Private Browser is Chromium-based, it may still support standard Chromium Web Bluetooth permission prompts even if Norton does not expose a dedicated Bluetooth settings page in the browser UI.

In some Chromium-derived browsers, Bluetooth permissions are handled dynamically when a website requests access and may rely partly on Windows Bluetooth/privacy controls rather than a permanent browser toggle within the browser itself.

So, a Bluetooth permission prompt alone is not necessarily suspicious, especially if it occurred while visiting a website or web app that interacts with hardware devices such as audio equipment, phones, printers, or smart devices.

The condo may provide:

a building-managed Ethernet/LAN wall jack

…and originally the user may have connected:

modem/device → directly to wall LAN

Then later added:

their own router between the wall jack and devices

That would give them:

their own NAT layer

their own Wi-Fi network name (SSID)

their own local firewall segmentation

better isolation from the broader condo/building network

So when the user says:

“Norton 360 only identifies the router network name now”

…that fits with:

Norton now seeing the user’s private router network instead of the upstream condo/building network.

That router change does improve local network isolation/security in many shared-building environments.

But even with that added context, the Bluetooth prompt still does not strongly point to neighbor intrusion. It still sounds more consistent with:

Chromium hardware permission behavior

a website-triggered device request

or Windows/browser device APIs

rather than:

LAN compromise through the condo network itself.

For a Chromium-based browser like Norton Private Browser to show a Bluetooth-related permission request, the system would normally need:

Bluetooth hardware on the computer/device
either:

built-in Bluetooth

or a USB Bluetooth adapter

and usually:

Bluetooth enabled in Windows/device settings

However, the browser prompt can sometimes appear:

before an actual device is selected

merely because a website requested access to nearby Bluetooth devices

So:

the existence of the prompt does not necessarily mean a device connected

but it does suggest the system/browser believes Bluetooth capability exists or is accessible.

Also important:

Nearby Bluetooth devices are extremely common now:

phones

earbuds

TVs

watches

printers

keyboards

cars

smart home devices

So if the user’s PC has Bluetooth enabled, Chromium can potentially enumerate/request access to nearby Bluetooth-capable devices after a site request — even in a condo environment full of neighboring devices.

That still would not imply the neighbors are connecting into the user’s system.

I think part of the confusion is simply that most people do not expect a web browser to reference Bluetooth at all.

However, modern Chromium-based browsers can interact with various hardware/device APIs, including USB devices, HID devices, MIDI devices, sensors, cameras, microphones, and Bluetooth-related requests initiated by websites or web apps.

I checked my own Norton Private Browser installation and could not find a dedicated Bluetooth settings page, but Additional Permissions does include several hardware/device categories. So the browser appearing to reference Bluetooth is not necessarily abnormal by itself.

That does not automatically indicate a security breach or unauthorized access. A Bluetooth permission prompt is more commonly tied to a website or web app requesting device access through standard Chromium functionality.

Without seeing the exact popup, there’s a decent chance the user interpreted a:

Windows Bluetooth/device permission dialog
or

Chromium permission prompt

as being “from Norton Private Browser” simply because the browser was open when it appeared.

That would especially make sense because:

you could not find a dedicated Bluetooth UI in Norton Private Browser

Chromium browsers often rely on underlying Windows Bluetooth/device services

Windows commonly brokers hardware permissions for applications

So the chain may have been:

Website/web app requests Bluetooth-capable device access

Chromium/Norton Private Browser passes request to Windows APIs

Windows surfaces the permission dialog

User associates popup with Norton Private Browser

That is a very plausible interpretation of the situation.

=============================================

The prompt may visually appear associated with Norton Private Browser because:

the request originated from the browser

the browser window was active

the permission dialog references the application requesting access

…but the actual permission handling may still be performed by:

Chromium APIs

Windows Bluetooth services

Windows device-permission infrastructure

So from a user perspective, it can feel like:

“Norton Private Browser is asking for Bluetooth.”

…even though technically it may be:

“Windows is processing a Bluetooth/device permission request initiated by the browser.”

That’s why these prompts can blur together for users:

browser UI

Windows permission layer

hardware/device APIs

They often appear as one integrated experience rather than clearly separated components.

Were the user to access a smart device via their browser. Their browser would appear to act as a gate keeper.

In that scenario, the browser acts as a kind of intermediary or “gatekeeper” between:

the website/web app
and

the local hardware/device APIs exposed by the operating system.

A simplified flow looks like this:

You visit a smart-device website/web app
Example:

smart lights

headphones

router setup portal

smartwatch manager

The site requests device access
Using Chromium APIs such as:

Web Bluetooth

WebUSB

HID

MIDI

The browser intercepts the request
Norton Private Browser (through Chromium) acts as the permission gatekeeper.

Windows handles underlying hardware communication
Windows may then surface:

permission prompts

pairing dialogs

device-selection windows

You approve or deny access

So from the user perspective:

“The browser is asking to use Bluetooth.”

Which is basically true operationally — even though the browser is leveraging Windows Bluetooth infrastructure underneath.

AI sourced content may make mistakes

Norton 360’s VPN sensing a Public Network LAN - but I’m in a residence with no LAN

Announcements