Use this article when a guest device joins the SSID and receives an IP address, but names are not resolved or websites do not load, before or after sign-in.
Which case applies?
- The portal does not open, and DNS fails before sign-in: steps 1, 3, and 4.
- The sign-in succeeds, but there is no Internet access: steps 1, 2, 3, and 4.
Prerequisites
- Access to the Cisco Meraki dashboard, including the MX security appliance if one is used
- Access to Cloudi-Fi's admin console
- A device that works and a device that fails, connected to the same SSID, for comparison
1. Compare a working client and a failing client
- In the Meraki dashboard, go to "Network-wide" > "Monitor" > "Clients" and open each client.
- Note the IP address, the VLAN, and the group policy applied to each one.
- Check that both receive an address in the expected guest subnet. Without a valid guest address, fix DHCP and the VLAN before the portal.
- Connect a device with a new MAC address, for example by changing the private Wi-Fi address setting of the device, and compare the behavior.
A test that works after turning off the private Wi-Fi address does not prove that this setting is the cause. Continue with the next steps.
2. Check the group policy and the MX firewall
A rule that is correct at the SSID level can be overridden by the policy of the MX security appliance.
- Go to "Security & SD-WAN" > "Configure" > "Firewall" and check the rules for the guest subnet. The order of the rules matters.
- Go to "Network-wide" > "Configure" > "Group policies". Check that the policy intended for guests exists, and that it is applied to the guest clients after sign-in.
- Check that the guest policy allows the flows in the table below.
| Source | Destination | Port | Protocol | Action | Comment |
| Guest subnet | Any | 80 | TCP | Allow | HTTP traffic |
| Guest subnet | Any | 443 | TCP | Allow | HTTPS traffic |
| Guest subnet | Any | 53 | UDP/TCP | Allow | DNS resolution |
| * | * | * | * | Deny | To be adjusted according to your needs |
The example above is only to show an example. Configure the Group Policy according to your network security policies.
3. Test DNS from the failing device
From a laptop connected to the guest SSID, open a terminal or a command prompt and run:
nslookup login.cloudi-fi.net
Then run the same test with another DNS server, for example:
nslookup login.cloudi-fi.net 8.8.8.8
Read the results:
- No answer, or a timeout. The DNS requests do not reach a server, or the answers do not come back. Check the DNS rule in step 2 and the path to the DNS servers.
- A negative answer, such as "non-existent domain". The server is reached, but does not know the name. Check which DNS servers the guest DHCP scope distributes.
- An IP address is returned, but websites still fail to load. DNS works. The issue is with HTTP or HTTPS traffic. Check the firewall rules for ports 80 and 443 in step 2.
Do the test at a precise time. Cloudi-Fi support needs the time to find the same requests in the logs.
4. Apply a limited correction and retest
- Allow only the flows that guests need, in the guest policy. Do not open additional ports on the basis of a single observed packet.
- Disconnect the test device, then connect again to start a new session.
- Complete the sign-in, and open two websites allowed for guests.
The correction is complete when DNS answers, the portal opens, the client is authorized, and Internet access works. Apply changes to production through the change procedure of the organization, and note the previous values first.
Contact your support
If the issue remains, contact the Cloudi-Fi support team and share the following information:
- The name of the location and of the SSID
- The IP address, the VLAN, the group policy, and the MAC address of the failing client and of a working client
- The date and time of the test, with the time zone
- The results of the
nslookupcommands - The firewall rules and group policy applied to the guest subnet