[isf-wifidog] Client captured but no access to login page.
Scott Tully
scott.tully at gmail.com
Ven 25 Fév 11:15:45 EST 2005
Hi Philippe - thanks for the fast reply!
On Fri, 25 Feb 2005 10:38:50 -0500, Philippe April
<isf_lists at philippeapril.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Scott,
>
> I'm sure we can help you out :)
>
> I'm pretty sure it's just misconfiguration in the config file.
>
> 1. By looking at your iptables rules, you seem to have uncommented all 3
> entries for auth servers but left ours.
>
> If you want to test, I recommend you leave only your auth server otherwise if the
> pings are not succesful it might try to switch to ours and use different
> databases :)
Yes, this is one of the many configurations i have tried. I switched
back to just using my server.... thanks
>
> 2. Hopefully you're using the code of our authentication server, even
> though there's no tarball release yet (our mistake)?
>
Yes, got it from cvs. The biggest problem i had was figuringout
postgresql... i'm a mysql guy ;-)
> 3. Is your webserver listening on port 443 (HTTPS)? otherwise HTTPS has to
> be disabled in the wifidog config for the AuthServer entry.
>
No, i have it listening on port 80... I have the server configured as
"SSLAvailable no" in wifidog.conf... see complete wifidog.conf below.
> 4. Make sure the GatewayInterface + GatewayAddress and ExternalInterface
> are right. This leads to weird issues (like the one you're having).
Everythng looks good here... eth0, eth1 and 10.10.10.1 is my internal
ip. again see below...
>
> To help with that, I suggest you download our latest CVS version, you'll
> only need to specify the GatewayInterface and it will detect the rest
> and there are other good improvements.
>
> So take a look at all of this and let us know. Of course WiFiDog is in
> constant development (especially the authentication server) and we'll
> standardize the release process soon so you can have tarballs to
> download next time :)
>
> Let us know!
>
> - --
> Philippe April
> GnuPG: http://key.philippeapril.com/
> Skype ID: mousetrap
>
Thanks phillipe i will try the latest cvs... and let you know how
that goes. I have pasted the contents of my wifidog.conf file
below.... let me know if anything looks wrong.
Scott
# $Header: /cvsroot/wifidog/wifidog/wifidog.conf,
# WiFiDog Configuration file
# Parm: GatewayID
# Default: default
# Optional but essential for monitoring purposes
#
# Set this to the template ID on the auth server
# this is used to give a customized login page to
# If none is supplied, the default login page wil
GatewayID default
# Parm: ExternalInterface
# Default: NONE
# Mandatory
#
# Set this to the external interface. Typically
ExternalInterface eth0
# Parm: GatewayInterface
# Default: NONE
# Mandatory
#
# Set this to the internal interface. Typicall
GatewayInterface eth1
# Parm: GatewayAddress
# Default: NONE
# Mandatory
#
# Set this to the internal IP address of the gate
GatewayAddress 10.10.10.1
# Parm: AuthServMaxTries
# Default: 1
# Optional
#
# Sets the number of auth servers the gateway wil
# this number should be equal to the number of Au
# configuration but it should probably not exceed
# AuthServMaxTries 3
# Parm: AuthServer
# Default: NONE
# Mandatory
#
# Set this to the hostname or IP of your auth ser
# WiFiDog-auth resides and optionally as a secon
# listens on.
#AuthServer {
# Hostname (Mandatory; Default: NONE)
# SSLAvailable (Optional; Default: no; Pos
# SSLPort 443 (Optional; Default: 443)
# HTTPPort 80 (Optional; Default: 80)
# Path wifidog/ (Optional; Default: /wifido
#}
AuthServer {
Hostname 192.168.1.76
SSLAvailable no
Path /wifidog/
}
#AuthServer {
# Hostname auth2.ilesansfil.org
# SSLAvailable yes
# Path /
#}
#
#AuthServer {
# Hostname auth3.ilesansfil.org
# SSLAvailable yes
# Path /
#}
# Parm: Daemon
# Default: 1
# Optional
#
# Set this to true if you want to run as a daemon
# Daemon 1
# Parm: GatewayPort
# Default: 2060
# Optional
#
# Listen on this port
# GatewayPort 2060
# Parm: HTTPDName
# Default: WiFiDog
# Optional
#
# Define what name the HTTPD server will respond
# HTTPDName WiFiDog
# Parm: HTTPDMaxConn
# Default: 10
# Optional
#
# How many sockets to listen to
# HTTPDMaxConn 10
# Parm: CheckInterval
# Default: 60
# Optional
#
# How many seconds should we wait between timeout
CheckInterval 60
# Parm: ClientTimeout
# Default: 5
# Optional
#
# Set this to the desired of number of CheckInter
# The timeout will be INTERVAL * TIMEOUT
ClientTimeout 5
Plus d'informations sur la liste de diffusion WiFiDog