4g wireless router captive portal​

4g wireless router captive portal is a software implementation that prevents clients from accessing the network until user authentication is established. You can set up authentication to allow guest and authenticated user access. Before granting access, the database of the authenticated user must be authenticated.

The authentication server supports both HTTP and HTTPS web connections. In addition, you can configure the captive portal to use an optional HTTP port (supporting HTTP proxy networks). If this additional port is configured, it is exclusively for captive portal use. Note that this optional port is an additional port beyond the standard HTTP port 80, which is currently used for all other web traffic.

The captive portal of the wired interface allows the client directly connected to the switch to be authenticated using the captive portal mechanism before granting the client access to the network. When the wired physical port is enabled for the captive portal, set the port to cap-portal-enabled so that all traffic from the unauthenticated client to the port except for ARP, DHCP, DNS, and NETBIOS packets Will be deleted. The switch forwards these packets so that unauthenticated clients can obtain an IP address and resolve the host name or domain name. Data traffic from an authenticated client passes through, and rules do not apply to these packets.

All HTTP / HTTPS packets from unauthenticated clients are directed to the CPU on the switch for all ports enabled for captive portals. When an unauthenticated client opens a web browser and attempts to connect to the network, the captive portal redirects all HTTP/HTTPS traffic from the unauthenticated client to the authentication server on the switch. Captive portal web pages are sent back to unauthenticated clients. The client can authenticate. If the client authenticates successfully, the client is granted access to the port.

You can enable captive portal on all physical ports on the switch. It does not support VLAN interfaces, loopback interfaces, or logical interfaces. Captive portal functions use MAC-aaddress-based authentication instead of port-based authentication. This means that all clients connected to the captive portal interface must be authenticated to access the network.

Clients connected to the captive portal interface have three states; unknown, unauthenticated, and authenticated.

Unknown. In an unknown state, the captive portal does not redirect HTTP/S traffic to the switch, but instead asks the switch client if it is authenticated.

Not authenticated. Captive portals direct HTTP/S communication to the switch so that clients can use the switch for authentication.

Authentication. After successful authentication, the client will be in an authenticated state. In this state, all traffic from the client is forwarded through the switch.

Captive portal configuration provides network administrators with control over authentication and authentication, assignment of interfaces, client sessions, and Web page customization.

You can create multiple captive portal configuration instances. Each captive portal configuration contains various flags and definitions that control client access and customize the content of user authentication web pages. Captive portal configuration can be applied to one or more interfaces. The interface can only be a physical port on the switch. Software versions 8.0 and later can include up to 10 captive portal configurations.

All captive portal configurations are managed using the CLI, web interface, and SNMP with one exception; to customize captive portal web pages, you must use the web interface.