IPv6 routing for a home security camera

Your security camera works on your home Wi-Fi but not when you are away, or it stops connecting after a router or VPN change. IPv6 may be part of the route, but a browser test cannot directly test the camera or its app.

First work out whether the problem is local access, the camera's remote service, or a VPN route. The VPN Leak Test can show whether your browser is using a real IPv6 address while a VPN is on. Use it as one clue, not as a camera test.

Check the camera's route safely

1. Open the VPN Leak Test in a browser on the same network as the camera. If you use a VPN, test with it on first. The test checks browser traffic for IPv4, IPv6, and WebRTC exposure. It does not inspect the camera's connection.
2. Try the camera app on your home Wi-Fi, then on your phone's cellular connection. Note which one works. Do not change router firewall or port settings yet.
3. Check the router's connected-device list for the camera. Record whether it has an IPv4 address, an IPv6 address, or both. Windows 11 shows your computer's connection under Settings › Network & internet. On macOS, open System Settings › Network. These paths show your computer's connection, not the camera's route.
4. Look in the camera app or its manual for how remote viewing works. It may use a vendor cloud service, a peer-to-peer connection, or direct access to your home network. The setup determines which route matters.

Keep the router's IPv6 firewall enabled while you investigate. Avoid adding a port-forwarding rule or turning off the firewall to see if that fixes the camera.

What the result means

The camera works on home Wi-Fi but not on cellular

The camera and phone can communicate locally, but remote access is failing. The camera may not be reaching its cloud service, or the service may not be able to establish a connection back to it. This does not by itself point to an IPv6 fault. Check the camera's online status and service settings before changing router rules.

The camera works on cellular but not on home Wi-Fi

Remote access is available, but something on your home network is getting in the way. A guest Wi-Fi network or a setting called client isolation can prevent devices on the same router from communicating with one another. Check whether your phone and camera are on the same home network, not a guest network.

The VPN Leak Test reports an IPv6 address while your VPN is on

Your browser may be reaching the internet over IPv6 outside the VPN tunnel. This says something about browser traffic, not the security camera's route. A VPN app on your phone or computer may not include other apps, and a browser VPN extension usually applies only to that browser.

The camera has IPv6 but remote viewing still fails

An IPv6 address does not guarantee that remote connections are allowed or working. The router firewall, camera firmware, DNS records, or camera service can all affect the path. A browser test cannot verify the camera's IPv6 route end to end.

The camera has no IPv6 address

That can be normal. The camera may use IPv4, or IPv6 may be disabled or unsupported. If it works reliably, there is no need to turn IPv6 on just because the router offers it.

How to fix it

1. Put your phone and camera on the same home network. Turn off guest Wi-Fi on the phone for a quick comparison. In the router settings, check for guest isolation or client isolation, which blocks communication between connected devices.
2. Allow local network access for the camera app. On iPhone, open Settings › Privacy & Security › Local Network and allow the camera app. On Android, open Settings › Apps › [camera app] › Permissions and check any nearby-device or local-network permission available on your version. Menu names vary by phone.
3. Check the camera's online status and service account. Confirm it is connected to the router, that the app is signed in to the correct account, and that remote viewing is enabled. If the camera uses a cloud service, check the manufacturer's service status and setup instructions.
4. Check router firewall and IPv6 settings without weakening them. Keep the default inbound firewall protection enabled. If the camera maker documents a specific IPv6 requirement, follow its instructions or ask its support team. Do not expose the camera directly to the internet by opening broad inbound access.
5. Test whether the VPN is involved. Temporarily disconnect the VPN on the device running the camera app, then try again. If access returns, check the VPN app's local-network or split-tunneling options. On Windows 11, Settings › Network & internet › VPN lists VPN connections. On macOS, check System Settings › VPN if your VPN appears there. The VPN provider's app may have its own controls.
6. Restart and update the camera and router. Restart both devices, then install available camera firmware and router updates. Retest on home Wi-Fi and cellular before changing more settings.

Why IPv6 does not automatically expose the camera

IPv6 devices can have globally routable addresses, unlike the private IPv4 addresses commonly used behind a router. But a public address is not the same as an open door. A correctly configured router firewall normally blocks unsolicited inbound connections. A camera app may instead make an outbound connection to a cloud service, which lets it receive remote requests without you opening a port.

The VPN Leak Test checks the browser that opens it. It cannot tell whether a camera app uses IPv6, whether the router permits its traffic, or whether the camera has a security flaw. Treat a leak result as a reason to inspect the VPN setup, not as proof that your camera is exposed.

If remote viewing still fails after checking the local network, app permissions, VPN, and camera service, contact the camera maker or router provider with the camera model and the connection details you observed. Keep the router firewall on while you wait for guidance.