Ubuntu-fr

j3r3my

Coova chilli et page de login

Bonjour à tous,
je fais pour l'instant tourné un coova chilli avec portail captif,tous est fonctionnelle, en voulant l'ameliorer je viens de me rendre compte que mes page web se trouvais dans le fichier /etc/chilli/www or j'aimerai pouvoir faire dans un futur proche, une separation par vlan mais avec des pages de login differentes pour chaque vlan, est ce quelqu'un aurait une idée de comment faire ? Car je pensais passer par differents fichier web sur le serveur apache mais vu que tous les fichier code source du portail viennent du même endroit, cela me parait difficile maintenant.

VOici le code du fichier de conf de coova

# -*- mode:127.0.0.1ript; -*-
#
#   Coova-Chilli Default Configurations. 
#   To customize, copy this file to /etc/chilli/config
#   and edit to your liking. This is included in shell scripts
#   that configure chilli and related programs before file 'config'. 


###
#   Local Network Configurations
# 

HS_WANIF=eth1            # WAN Interface toward the Internet
HS_LANIF=eth0              # Subscriber Interface for client devices
HS_NETWORK=10.10.4.0       # HotSpot Network (must include HS_UAMLISTEN)
HS_NETMASK=255.255.255.0   # HotSpot Network Netmask
HS_UAMLISTEN=10.10.4.254           # HotSpot IP Address (on subscriber network)
HS_UAMPORT=3990            # HotSpot UAM Port (on subscriber network)
HS_UAMUIPORT=4990          # HotSpot UAM "UI" Port (on subscriber network, for embedded portal)

# HS_DYNIP=
# HS_DYNIP_MASK=255.255.255.0
# HS_STATIP=
# HS_STATIP_MASK=255.255.255.0
# HS_DNS_DOMAIN=

# OpenDNS Servers
HS_DNS1=208.67.222.222
HS_DNS2=208.67.220.220

###
#   HotSpot settings for simple Captive Portal
#
HS_NASID=nas01
HS_RADIUS=127.0.0.1
HS_RADIUS2=127.0.0.1
HS_UAMALLOW=10.10.4.0/24
HS_RADSECRET=radsecret    # Set to be your RADIUS shared secret
HS_UAMSECRET=uamsecret    # Set to be your UAM secret
HS_UAMALIASNAME=chilli

#   The server to be used in combination with HS_UAMFORMAT to 
#   create the final chilli 'uamserver' url configuration.
HS_UAMSERVER=$HS_UAMLISTEN

#   Use HS_UAMFORMAT to define the actual captive portal url.
#   Shell variable replacement takes place when evaluated, so here
#   HS_UAMSERVER is escaped and later replaced by the pre-defined 
#   HS_UAMSERVER to form the actual "--uamserver" option in chilli.
HS_UAMFORMAT=http://\$HS_UAMLISTEN:\$HS_UAMUIPORT/www/login.chi

#   Same principal goes for HS_UAMHOMEPAGE.
HS_UAMHOMEPAGE=http://\$HS_UAMLISTEN:\$HS_UAMPORT/www/coova.html

#   This option will be configured to be the WISPr LoginURL as well
#   as provide "uamService" to the ChilliController. The UAM Service is
#   described in: http://www.coova.org/CoovaChilli/UAMService
#
#Permet d’aller rechercher chez un utilisateur ses informations de connexion et #donc lui donner la possibilité de passer d’un AP à un autre sans avoir besoin  #d’avoir à se connecter au portail captif
HS_UAMSERVICE=https://10.10.4.254/cgi-bin/hotspotlogin.cgi

###
#   Firewall issues
#
# Uncomment the following to add ports to the allowed local ports list
# The up.sh script will allow these local ports to be used, while the default
# is to block all unwanted traffic to the tun/tap. 
#
HS_TCP_PORTS="80 443 1812 1813 22 3799"

###
#   Standard configurations
#
HS_MODE=hotspot
HS_TYPE=chillispot
HS_RADAUTH=1812
HS_RADACCT=1813
HS_COAPORT=3799

##
#   Post-Auth proxy settings
#
# HS_POSTAUTH_PROXY=<host or ip>
# HS_POSTAUTH_PROXYPORT=<port>

#   Directory specifying where internal web pages can be served
#   by chilli with url /www/<file name>. Only extentions like .html
#   .jpg, .gif, .png, .js are allowed. See below for using .chi as a
#   CGI extension.
#HS_WWWDIR=/etc/chilli/www
HS_WWWDIR=/var/www/hotspot
#   Using this option assumes 'haserl' is installed per-default
#   but, and CGI type program can ran from wwwsh to process requests
#   to chilli with url /www/filename.chi
HS_WWWBIN=/etc/chilli/wwwsh

#   Some configurations used in certain user interfaces
#
HS_PROVIDER=Coova
HS_PROVIDER_LINK=http://www.coova.org/


###
#   WISPr RADIUS Attribute support
#

HS_LOC_NAME="My HotSpot"           # WISPr Location Name and used in portal

#   WISPr settings (to form a proper WISPr-Location-Id)
# HS_LOC_NETWORK="My Network"      # Network name
# HS_LOC_AC=408                    # Phone area code
# HS_LOC_CC=1                      # Phone country code
# HS_LOC_ISOCC=US                  # ISO Country code

# Embedded miniportal
# HS_REG_MODE="tos" # or self, other
# HS_RAD_PROTO="pap" # or mschapv2, chap
# HS_USE_MAP=on
                                                                                                                 

Pour faire ceci suis je obliger d'utiliser un autre authentificateur comme Dynamic Login Pages ?

Dernière modification par j3r3my (Le 11/05/2015, à 16:10)