配置的OpenWrt提供HTTP认证 [英] Configure OpenWrt to provide HTTP authentication

问题描述

我需要配置一个智邦科技MR3201A接入点运行的OpenWrt。

我希望它提供一个开放的WiFi使用HTTP认证的网页上，用户必须提供用户名和放大器;密码能够访问互联网之前。

有一个现有的包（ http://downloads.openwrt.org/snapshots /主干/ ar71xx /包/ ），使这个？

解决方案

  

的这可能是一个老帖子一点点，但想通它可能是其他任何人搜索有用的：的

有一些强制网络门户解决方案在那里，最好的解决方案取决于你的灵活性，定制和技术要求。

强制网络门户解决方案：

1. Chillispot ：使用后端用户管理和跟踪半径数据库第2层的解决方案。的警告：的这个项目可能已经死了。目前还没有真正一直在这个项目中很多工作多年。这会导致下一个项目。


2. CoovaChilli ：建在Chillispot的顶部有几个改进和补充。包括WISPr支持，等等。通过jhonkola提到CoovaAP主要用于强制网络门户解决方案。


3. PepperSpot ：另一个Chillispot叉。对IPv6协议的支持，无线保护接入（WPA）。此外Radius服务器后端。


4. NoCat ：的一系列项目来创建一个强制网络门户解决方案一样，提供简单的设置和免费的公共互联网。


5. WiFiDog ：最初从NoCatSplash和NoCatAuth，Wifidog分叉提供了一个简单的包，没有UCI基于配置文件。用户可以进行管理，并通过网关控制和勾搭成任何自定义的用户管理。该解决方案创建一个自定义的集中用户管理系统。你可以建立自己的登录页面，用户管理系统，或者使用自己的门户系统。


6. NoDogSplah ：从NoCat另一种方法，旨在报价强制网络门户解决方案，本地路由器/网关和简单的设置，用户的带宽控制和基本身份验证/初始页面。

我个人使用一个高度定制wifidog包和authserver已经从地上爬起来为我们的公司改组。我们能够每个用户和池带宽控制，自定义用户会计数据，WISPr支持添加（从家伙在打补丁时Coova，他们再也不会举办这个补丁）。目前我们正在努力挂钩鱿鱼的支持。我们去与Wifidog，因为它是非常容易定制和使用iptables而不是chillispots二层的解决方案在三层跑去。但是，最好的解决方案取决于时间，精力和灵活性，你想的金额。

参考文献：<一href=\"http://wiki.openwrt.org/doc/howto/wireless.hotspot\"><$c$c>http://wiki.openwrt.org/doc/howto/wireless.hotspot

I need to configure an "Accton MR3201A" access point running OpenWrt.

I want it to provide an open WiFi with an HTTP authentication webpage on which users must provide a username & password before being able to access the internet.

Is there an existing package (http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/) that allows this ?

解决方案

This may be a little bit of an old post, but figured it might be helpful for anyone else searching:

There are a few captive portal solutions out there and the best solution depends on your flexibility, customization, and technology requirements.

Captive Portal Solutions:

1. Chillispot: Layer 2 solution using a radius database for the backend user management and tracking. WARNING: This project may be dead. There hasn't really been much work on this project for years. Which leads to the next project.
2. CoovaChilli: Built on top of Chillispot with several improvements and additions. Includes WISPr support, and much more. Main captive portal solution used in CoovaAP mentioned by jhonkola.
3. PepperSpot: Another Chillispot fork. Support for IPv6 protocol, Wireless Protected Access (WPA). Also radius server backend.
4. NoCat: A series of projects to create a captive portal like solution offering simple setup and free public internet.
5. WiFiDog: Originally forked from NoCatSplash and NoCatAuth, Wifidog offers a simple package and none uci based configuration file. Users can be managed and controlled through the gateway and hooked into any custom user management. This solution creates a custom central user management system. You can build your own login page and user management system or use their own portal system.
6. NoDogSplah: Another alternative from NoCat which aims to offer captive portal solutions local to the router/gateway and a simplistic setup, user bandwidth control and basic auth/splash page.

I personally use a highly customized wifidog package and authserver which has been revamped from the ground up for our company. We were able to add per user and pooling bandwidth controls, custom user accounting data, WISPr support (patch from guys over at Coova, they do not host this patch anymore). And we're currently working on hooking squid support. We went with Wifidog as it was much easier to customize and ran at layer3 using iptables as opposed to chillispots layer2 solutions. But the best solution depends on the amount of time, effort and flexibility you would like.

References: http://wiki.openwrt.org/doc/howto/wireless.hotspot

这篇关于配置的OpenWrt提供HTTP认证的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！