Bypassing Specific SSIDs

Jamf Protect Documentation

Solution
Application
Content Type
Technical Documentation
Utilities & Services
ft:locale
en-US

The most common reason for bypassing specific SSIDs is when dealing with networks that have a captive portal not following WISPr standards. Such networks are frequently encountered in the airline industry.

When a network does not adhere to WISPr, it often leads to Apple devices being unable to display the captive portal page, which is essential for establishing an internet connection through that network. The root cause of this issue lies in the use of Jamf DNS servers instead of the DNS provided by the local network. Typically, only the local DNS server can provide the IP address of the captive portal.

To prevent the use of the Jamf DNS server on a specific WiFi network, you can configure an SSID bypass. With SSID bypass enabled, the device uses the local DNS server for hostname resolution instead of Jamf servers. However, it is important to note that this effectively disables all web protection functionality while the device is connected to this SSID.

The following is an example configuration for bypassing a specific SSIDs:
<array>
	<dict>
		<key>Action</key>
		<string>Disconnect</string>
		<key>SSIDMatch</key>
		<array>
			<string>AlaskaWiFi.com</string>
			<string>BA Wi-Fi</string>
			<string>BAWi-Fi</string>
			<string>deltawifi.com</string>
			<string>DeltaWiFi.com</string>
			<string>EurostarTrainsWiFi</string>
		</array>
	</dict>
	<dict>
		<key>Action</key>
		<string>Connect</string>
	</dict>
</array>
This configuration allows you to specify certain SSIDs for which you want to disconnect from the Jamf DNS server and use the local DNS server instead.