Troubleshoot routing issues

The tables in this section provide details about how

BlackBerry Access

routes traffic depending on whether a manual proxy or proxy autoconfiguration (PAC) is used. You can use this information to troubleshoot browsing issues related to traffic routing.

The table does not describe the situation where a target URL is configured to be blocked by either the

BlackBerry Dynamics

Connectivity Profile or the PAC file because the URL is always blocked no matter which other configurations are in place.

Legend

No proxy:
The proxy server is not specified in the

BlackBerry Access

app configuration.

Manual proxy:
A web proxy server is manually specified in the

BlackBerry Access

app configuration. When a web proxy is specified in this way,

BlackBerry Access

attempts to route all traffic through the web proxy.

PAC:
A PAC file is specified in the

BlackBerry Access

app configuration. When a PAC is configured,

BlackBerry Access

follows the rules specified in the PAC to determine whether to send traffic through the web proxy. Specifies the result of the PAC file check against the target host (DIRECT, PROXY, BLOCK, NATIVE).

Host route = BBP:
The specified target URL is configured to route through a

BlackBerry Proxy

cluster based on the

BlackBerry Dynamics

Connectivity Profile. This URL is explicitly defined, or is under the Default Route or an Allowed domains rule.

Host route = DIRECT:
The specified target URL is configured to route directly based on the

BlackBerry Dynamics

Connectivity Profile. This URL is explicitly defined or is under the Default Route.

Web Proxy Route = BBP:
The proxy server's URL is configured to route through a

BlackBerry Proxy

cluster based on the

BlackBerry Dynamics

Connectivity Profile. This URL is explicitly defined, or is under the Default Route or an Allowed domains rule.

Web proxy route = DIRECT:
The proxy server's URL is configured to route directly based on the

BlackBerry Dynamics

Connectivity Profile. This URL is explicitly defined or is under the Default Route.

	Strict tunnel on	Strict tunnel off
No proxy Host route = BBP	BlackBerry Access routes traffic through the BlackBerry Proxy cluster.	BlackBerry Access routes traffic through the BlackBerry Proxy cluster.
No proxy Host route = DIRECT	The host is blocked because of strict tunnel.	BlackBerry Access routes traffic directly to the host.
Manual proxy Host route = BBP Web proxy route = BBP	BlackBerry Access routes traffic though the BlackBerry Proxy cluster and then through the web proxy.	BlackBerry Access routes traffic though the BlackBerry Proxy cluster and then through the web proxy.
Manual proxy Host route = DIRECT Web proxy route = BBP	BlackBerry Access routes traffic though the BlackBerry Proxy cluster and then through the web proxy.	BlackBerry Access routes traffic though the BlackBerry Proxy cluster and then through the web proxy. Even though the host does not resolve in the BlackBerry Dynamics Connectivity Profile, the web proxy does resolve. Therefore all traffic through the web proxy goes through the BlackBerry Proxy cluster.
Manual proxy Host route = BBP Web proxy route = DIRECT	The web proxy server is blocked because of strict tunnel.	BlackBerry Access routes traffic directly to the web proxy and then to the host. Even though the host resolves in the BlackBerry Dynamics Connectivity Profile, because the web proxy configured as DIRECT, all traffic through that web proxy is direct.
Manual proxy Host route = DIRECT Web proxy route = DIRECT	Both the host and the web proxy server are blocked because of strict tunnel.	BlackBerry Access routes traffic directly to the web proxy and then to the host.
PAC returns DIRECT Host route = BBP	The host is blocked because of strict tunnel.	BlackBerry Access routes traffic directly to the host.
PAC returns PROXY Host route = BBP Web proxy route = BBP	BlackBerry Access routes traffic though the BlackBerry Proxy cluster and then through the web proxy.	BlackBerry Access routes traffic though the BlackBerry Proxy cluster and then through the web proxy. Even though the host does not resolve in the BlackBerry Dynamics Connectivity Profile, the web proxy does resolve. Therefore all traffic through the web proxy goes through the BlackBerry Proxy cluster.
PAC returns PROXY Host route = DIRECT Web proxy route = BBP	BlackBerry Access routes traffic though the BlackBerry Proxy cluster and then through the web proxy.	BlackBerry Access routes traffic directly to the web proxy and then to the host. Even though the host resolves in the BlackBerry Dynamics Connectivity Profile, because the web proxy configured as DIRECT, all traffic through that web proxy is direct.
PAC returns PROXY Host route = BBP Web proxy route = DIRECT	The web proxy is blocked because of strict tunnel.	BlackBerry Access routes traffic directly to the web proxy and then to the host.
PAC returns PROXY Host route = DIRECT Web proxy route = DIRECT	The host is blocked because of strict tunnel.	BlackBerry Access routes traffic directly to the web proxy and then to the host.

Behavior of myIPAddress and DNSResolve

Depending on the routing configuration, the DNS resolution and the source IP address will differ. The following table describes which endpoint makes the DNS calls and which endpoint is considered the source IP address when connecting to a target host.

	DNSResolve during PAC computation	DNSResolve for socket connection	MyIPAddress for PAC
Host route = BBP Strict tunnel = On	The BlackBerry Proxy resolves the IP address of the host.	The BlackBerry Proxy resolves the IP address of the host.	The IP address of the BlackBerry Proxy is used.
Host route = BBP Strict tunnel = Off	The BlackBerry Proxy resolves the IP address of the host.	The BlackBerry Proxy resolves the IP address of the host.	The IP address of the BlackBerry Proxy is used.
Host route = DIRECT Strict tunnel = On	The BlackBerry Proxy resolves the IP address of the host.	DNSResolve is blocked or there is no DNS resolution.	The IP address of the BlackBerry Proxy is used.
Host route = DIRECT Strict tunnel = Off	The BlackBerry Proxy resolves the IP address of the host.	The device resolves the IP address of the host.	The IP address of the device is used.

Section:

Troubleshooting