-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[CF1] ip visibility update #19354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
[CF1] ip visibility update #19354
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
56 changes: 56 additions & 0 deletions
56
src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,56 @@ | ||
| --- | ||
| pcx_content_type: reference | ||
| title: IP visibility | ||
| sidebar: | ||
| order: 7 | ||
| --- | ||
|
|
||
| DEX's IP visibility gives administrators insight into three different IP types per device: | ||
|
|
||
| 1. **Device**: The private IP address of an end-user device. | ||
| 2. **ISP**: The public IP assigned by the ISP that the end-user device is being routed though. | ||
| 3. **Gateway**: The router's private IP (the router the end device is connected to.) | ||
|
|
||
| DEX's IP visibility supports both IPv6 and IPv4 addresses. | ||
|
|
||
| IP information is crucial for IT administrators to accurately troubleshoot network issues and identify user locations. IT administrators face challenges like: | ||
|
|
||
| - Pinpointing the exact location of a user experiencing issues ("AP 87 is bad.") | ||
| - Identifying network access control policy violations ("NAC Policies is not applied properly.") | ||
| - Troubleshooting firewall restrictions ("Firewall on VLAN 93 is blocking.") | ||
| - Resolving Layer 2 and DHCP related problems. | ||
| - Indirectly determining user identity and device location. | ||
|
|
||
| ## View a device's IP information | ||
|
|
||
| To view IP information for a user device: | ||
|
|
||
| 1. Log in the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. | ||
| 2. Select **Zero Trust** to go to the Zero Trust dashboard. | ||
| 3. Select **My team** > **Devices**. | ||
| 4. Select a device > **View details** > under **Details**, scroll down to **IP details**. | ||
| 5. Review the IP details for your selected device's most recent session. | ||
|
|
||
| ## View a device's IP history | ||
|
|
||
| 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: | ||
|
|
||
| 1. Log in the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. | ||
| 2. Select **Zero Trust** to go to the Zero Trust dashboard. | ||
| 3. Select **My team** > **Devices**. | ||
| 4. Select a device > **View details** > under **Details**, scroll down to **IP details**. | ||
| 5. Select **View device history**. | ||
| 6. View the device's IP history and status from the last seven days. | ||
| 7. Select a time to view more information about the device at that time. | ||
|
|
||
| Refer to [Available metrics](/cloudflare-one/insights/dex/fleet-status/#available-metrics) to review **Status** and **Mode** descriptions. | ||
|
|
||
| ## Troubleshoot with IP visbility | ||
|
|
||
| While IP visibility allows you to inspect a device's IP information, [DEX's live analytics](/cloudflare-one/insights/dex/fleet-status/#available-metrics) can help you to compare that IP data with information about 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 colo](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request). | ||
|
|
||
| To compare the selected device's IP information to the Cloudflare colo it is connected to: | ||
|
|
||
| 1. Follow the steps listed in [View IP information](#view-a-devices-ip-history) to find a device's IP information. | ||
| 2. Select **Device Monitoring** above **Device event log**. | ||
| 3. Find **Colo** in the **Device details** table to review which Cloudflare data center your selected device's egress traffic is connected to. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recommend using the standard pattern for ZT UI instructions: