|
| 1 | +--- |
| 2 | +pcx_content_type: reference |
| 3 | +title: IP visibility |
| 4 | +sidebar: |
| 5 | + order: 7 |
| 6 | +--- |
| 7 | + |
| 8 | +import { Render } from "~/components"; |
| 9 | + |
| 10 | +DEX's IP visibility gives administrators insight into three different IP types per device: |
| 11 | + |
| 12 | +1. **Device**: The private IP address of an end-user device. |
| 13 | +2. **ISP**: The public IP assigned by the ISP that the end-user device is being routed though. |
| 14 | +3. **Gateway**: The router's private IP (the router the end device is connected to.) |
| 15 | + |
| 16 | +:::note |
| 17 | + |
| 18 | +The ISP IP is only visible to users with the [Zero Trust PII role](/cloudflare-one/roles-permissions/#cloudflare-zero-trust-pii). |
| 19 | + |
| 20 | +::: |
| 21 | + |
| 22 | +DEX's IP visibility supports both IPv6 and IPv4 addresses. |
| 23 | + |
| 24 | +IP information is crucial for IT administrators to accurately troubleshoot network issues and identify user locations. IT administrators face challenges like: |
| 25 | + |
| 26 | +- Pinpointing the exact location of a user experiencing issues ("AP 87 is bad.") |
| 27 | +- Identifying network access control policy violations ("NAC Policies is not applied properly.") |
| 28 | +- Troubleshooting firewall restrictions ("Firewall on VLAN 93 is blocking.") |
| 29 | +- Resolving Layer 2 and DHCP related problems. |
| 30 | +- Indirectly determining user identity and device location. |
| 31 | + |
| 32 | +## View a device's IP information |
| 33 | + |
| 34 | +To view IP information for a user device: |
| 35 | + |
| 36 | +1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My team** > **Devices**. |
| 37 | +2. Select a device, then select **View details**. |
| 38 | +3. Under **Details**, scroll down to **IP details**. |
| 39 | +4. Review the IP details for your selected device's most recent session. |
| 40 | + |
| 41 | +## View a device's IP history |
| 42 | + |
| 43 | +DEX's IP visibility allows you to review an event log of a device's IP history for the last seven days. To view a device's IP history: |
| 44 | + |
| 45 | +1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My team** > **Devices**. |
| 46 | +2. Select a device > **View details** > under **Details**, scroll down to **IP details**. |
| 47 | +3. Select **View device history**. |
| 48 | +4. View the device's IP history and status from the last seven days. |
| 49 | +5. Select a time to view more information about the device at that time. |
| 50 | + |
| 51 | +Refer to [Available metrics](/cloudflare-one/insights/dex/fleet-status/#available-metrics) to review **Status** and **Mode** descriptions. |
| 52 | + |
| 53 | +## Troubleshoot with IP visbility |
| 54 | + |
| 55 | +While IP visibility allows you to inspect a device's IP information, use [DEX's live analytics](/cloudflare-one/insights/dex/fleet-status/#available-metrics) to review which Cloudflare data center the device is connected to. When traffic leaves a WARP-connected end-user device, it will hit a [Cloudflare data center](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request). |
| 56 | + |
| 57 | +To find which Cloudflare data center a device is connected to: |
| 58 | + |
| 59 | +1. Follow the steps listed in [View IP information](#view-a-devices-ip-history) to find a device's IP information. |
| 60 | +2. Select **Device Monitoring** above **Device event log**. |
| 61 | +3. Find **Colo** in the **Device details** table to review which Cloudflare data center your selected device's egress traffic is connected to. |
0 commit comments