OPENWRT Linux Portal Implementation supports HTTPS

Brief introduction

The application of portal in OpenWrt is mainly WiFiDog and CoovaChilli. The following describes the implementation principles of the two applications respectively.

Introduction to the principle of wifidog implementation

Redirect HTTP requests to the WiFiDog Web server by using the redirection rules of the iptables NAT table.

The Web service then sends an HTTP 302 redirect to the portal home page for portal popup functionality. When client authentication

After passing, increase the cancellation of the client punch rules to achieve portal authentication through the normal Internet function.

advantages : Efficient, easy to expand.

disadvantage : HTTPS redirection is not supported at this stage.

Introduction to the implementation principle of CoovaChilli

CoovaChilli by taking over all the data of the WiFi interface, the portal home page is returned when an HTTP request is found for the client that is not authenticated, and other requests are discarded. The request is forwarded when the client authentication passes. This allows for portal functionality.

Advantages : Accurate data packet control is achieved.

Disadvantage : The performance impact is large, the HTTPS is not supported temporarily.

Introduction of the above two types of portal implementation procedures, in fact, there is no use of eggs. Today I would like to introduce you to a new portal implementation, which should be a wifidog upgrade extension, but simpler than WiFiDog.

This article is from the "record Little Harvest Growth" blog, please be sure to keep this source http://gofly.blog.51cto.com/4344767/1689815

OPENWRT Linux Portal Implementation supports HTTPS