Hotel guests get an address and can resolve the portal name. The browser never opens the portal. The pre-authentication filter allows DHCP and DNS only. What is missing from that filter?
Select an answer to reveal the explanation.
Short Explanation
The guest can ask where the portal is and still cannot walk there. Your filter allows the question and blocks the building. Add the portal address, because DNS already did its job.
Full Explanation
A pre-authentication filter has to permit the few things a guest needs before login. DHCP and DNS are working, which is why the guest has an address and can resolve the portal name. The browser still cannot open the portal because the portal address itself is not permitted. Add that address. The SSID name is not an entry in the filter, and DNS is already allowed, so the SSID is not what is missing. A channel number does not permit a portal. The filter is an IP policy, not a radio policy. An RF tag selects radio profiles. The filter does not read it to learn a portal address. The guest can resolve the name because DNS is permitted. The browser still needs the portal address itself opened in the filter. Exam caveat: if the portal name resolves to several addresses, permit the ones clients actually receive. One missing address looks exactly like this ticket. Operational check: add the portal address, reload the redirect on a test guest, and confirm the portal loads before any other access is allowed.