Juniper JUNOS OS 10.4 - FOR EX REV 1 Manual page 2929

Meaning
Purpose
Action
Troubleshooting
Problem
Solution
Related
Documentation
Copyright © 2010, Juniper Networks, Inc.
Configured CP session timeout: 3600 seconds
Server timeout: 15 seconds
The output confirms that captive portal is configured on interface ge-0/0/10 with the
default settings for number of retries, quiet period, CP session timeout, and server timeout.
Verify That Captive Portal Is Working Correctly
Verify that captive portal is working on the switch.
Connect a client to interface ge-0/0/10. From the client, open a Web browser and request
a webpage. The captive portal login page that you designed should be displayed. After
you enter your login information and are authenticated against the RADIUS server, the
Web browser should display either the page you requested or the post-authentication
URL that you configured.
To troubleshoot captive portal, perform these tasks:
Troubleshooting Captive Portal
The switch does not return the captive portal login page when a user connected to a
captive portal interface on the switch requests a Web page.
You can examine the ARP, DHCP, HTTPS, and DNS counters—if one or more of these
counters are not incrementing, this provides an indication of where the problem lies. For
example, if the client cannot get an IP address, you might check the switch interface to
determine whether the DHCP counter is incrementing—if the counter increments, the
DHCP packet was received by the switch.
user@switch> show captive-portal firewall ge-0/0/10.0
ge-0/0/10.0
Filter name: dot1x_ge-0/0/10
Counters:
Name
dot1x_ge-0/0/10_CP_arp
dot1x_ge-0/0/10_CP_dhcp
dot1x_ge-0/0/10_CP_http
dot1x_ge-0/0/10_CP_https
dot1x_ge-0/0/10_CP_t_dns
dot1x_ge-0/0/10_CP_u_dns
Configuring Captive Portal Authentication (CLI Procedure) on page 2848Configuring
Designing a Captive Portal Authentication Login Page on an EX Series Switch on page 2850
Chapter 88: Examples: Access Control Configuration
Bytes Packets
7616 119
0
0
0
0
0
0
0
0
0
0
2825