Gateway
The users device's tunnels are terminated on the Gateways. Here cz-vpnd@x handles the majority of the traffic (NGiNX handles HTTP up), cz-sessiond controls the user's session; cz-gonamed or cz-dnsfwd resolves the resource names in Entitlements.
To list tun device |
|
Capture traffic on a tun device, for example tun3 |
|
View DNS forwarder details |
Shows the current status of the DNS Forwarder. This will include: IPV4 stats
Here it is possible to see each the matched domains listed. These are 'matched' being resolved and the resulting IP address. |
View name resolver details |
Then enter
Provides all the names subscribed to named along with the time it was sent, time it was updated, time it was received and results. And there are some useful specific named commands:
|
View user session details |
|
View vpnd details |
|
View NGiNX details (HTTP up Action type) |
This will perform an http GET - the results will confirm NGiNX is operating as expected and will list the URIs in the [ ] for the specified for the user. * Trying 127.0.0.1..... |
Portal
The Portal uses the AppGate ZTNA Client under the covers. Since they are buried within an appliance, a set of troubleshooting tools are available to help diagnose any user access issues that might arise.
Webd is the daemon that controls the session usage within the Portal. To get to the webd admin console: |
Then enter:
The sessions list will return entries like: ShortID: uzczjd212f ClientID: 9000 SrcIP: 213.65.218.114 Dn: CN=566bd8c512384c70df714fe0f13ad7bd,CN=name.name,OU=AppGate-IdP LoggedIn: true |
To see the specific client logs for a user's session. |
ClientID can be obtained from the session list. |
To check on the DNS settings being applied to each user use: |
(Because this is a view of a live cache the results can be a bit unpredictable - so you may need to run this a few times to capture the information you are interested in.) |
For a general overview of the Portal's Clients and the related memory consumption use: |
|


