[isf-wifidog] Connection to Auth_server

Lun 9 Oct 05:53:49 EDT 2006

Thanks for the reply, yes it´s true, no one yet has answered me!!!!
I think my wifidog.conf file it´s ok, it looks like this:
Can you tell me if it´s all ok?
Thanks.

********************************************************************************************************
# WiFiDog Configuration file

# Parameter: 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 the clients
# If none is supplied, the mac address of the GW interface will be used,
# without the : separators

# GatewayID default
GatewayID gw01

# Parameter: ExternalInterface
# Default: NONE
# Optional
#
# Set this to the external interface.  Typically vlan1 for OpenWrt, and eth0 or ppp0 otherwise

ExternalInterface eth1

# Parameter: GatewayInterface
# Default: NONE
# Mandatory
#
# Set this to the internal interface.    Typically br0 for OpenWrt, and eth1 otherwise

#GatewayInterface eth1         #----------Alterado dia 12-09-2006
GatewayInterface eth2          #----------Alterado dia 12-09-2006
# Parameter: GatewayAddress
# Default: Find it from GatewayInterface
# Optional
#
# Set this to the internal IP address of the gateway

# GatewayAddress 192.168.1.1
GatewayAddress 10.192.129.181   #----------Alterado dia 12-09-2006
# Parameter: AuthServer
# Default: NONE
# Mandatory, repeatable
#
# This allows you to configure your auth server(s).  Each one will be tried in order, untill one responds.
# Set this to the hostname or IP of your auth server(s), the path where
# WiFiDog-auth resides in and the port it listens on.
#AuthServer {
#       Hostname      (Mandatory; Default: NONE)
#       SSLAvailable  (Optional; Default: no; Possible values: yes, no)
#       SSLPort 443   (Optional; Default: 443)
#       HTTPPort 80   (Optional; Default: 80)
#       Path wifidog/ (Optional; Default: /wifidog/ Note:  The path must be both prefixed and suffixed by /.  Use a single / for server root.)
#}

AuthServer {
    Hostname 10.192.128.77
    SSLAvailable no
    Path /wifidog/
}# Parameter: GatewayPort
# Default: 2060
# Optional
GatewayPort 2060           #--------------- Alterado dia 12-09-2006
# Listen on this port
# GatewayPort 2060

# Parameter: HTTPDName
# Default: WiFiDog
# Optional
#
# Define what name the HTTPD server will respond
# HTTPDName WiFiDog

# Parameter: HTTPDMaxConn
# Default: 10
# Optional
#
# How many sockets to listen to
# HTTPDMaxConn 10

# Parameter: CheckInterval
# Default: 60
# Optional
#
# How many seconds should we wait between timeout checks
CheckInterval 60

# Parameter: ClientTimeout
# Default: 5
# Optional
#
# Set this to the desired of number of CheckInterval of inactivity before a client is logged out
# The timeout will be INTERVAL * TIMEOUT
ClientTimeout 5

# Parameter: TrustedMACList
# Default: none
# Optional
## Parameter: FirewallRuleSet
# Default: none
# Mandatory
#
# Groups a number of FirewallRule statements together.

# Parameter: FirewallRule
# Default: none
#
# Define one firewall rule in a rule set.

# Rule Set: global
#
# Used for rules to be applied to all other rulesets except locked.
# This is the default config for the Teliphone service.

# Rule Set: validating-users
#
# Used for new users validating their account
FirewallRuleSet validating-users {
    FirewallRule allow to 0.0.0.0/0
}

# Rule Set: known-users
#
# Used for normal validated users.
FirewallRuleSet known-users {
    FirewallRule allow to 0.0.0.0/0
}

# Rule Set: unknown-users
#
# Used for unvalidated users, this is the ruleset that gets redirected.
#
# XXX The redirect code adds the Default DROP clause.

# Rule Set: locked-users
#
# Used for users that have been locked out.
FirewallRuleSet locked-users {
    FirewallRule block to 0.0.0.0/0

# Comma separated list of MAC addresses who are allowed to pass
# through without authentication
#TrustedMACList 00:00:DE:AD:BE:AF,00:00:C0:1D:F0:0D

"/etc/wifidog.conf" 173L, 4315C    

-----Mensagem original-----
De: Alexandre Carmel-Veilleux [mailto:acveilleux at gmail.com] 
Enviada: segunda-feira, 9 de Outubro de 2006 2:46
Para: WiFiDog Captive Portal; CASTANHEIRA, Nuno Osvaldo
Assunto: Re: [isf-wifidog] Connection to Auth_server

Hello,

I don't know if anyone's answered you. Is the auth server properly configured in the wifidog.conf? Including the Path with both a leading and trailing /? Is the HTTPPort set? The gateway doesn't speak SSL and only uses HTTPPort.

Did you try enabling one of the default ISF auth server?

Alex

On 9/27/06, CASTANHEIRA, Nuno Osvaldo <nocastanheira at refertelecom.pt> wrote:
>
>
> Hi,
> Sorry for my english, but i try do the best.
> I have finihed the instalation of the wifidog-gateway, made some tests 
> without the auth_server and it worked fine.
> After that i have installed my auth_server.
> The gateway can´t connect to the auth_server, from the gateway i can 
> reach the auth_server (tested with ping), but when i run (wifidog -f 
> -d 7) command i get this error:
>
> [7][Wed Sep 27 11:53:49 2006][20078](centralserver.c:254) Level 1: 
> Marking auth server [My_Auth_server] as bad and trying next if 
> possible [7][Wed Sep 27 11:53:49 2006][20078](centralserver.c:210) Level 2:
> Calculated 1 auth servers in list
> [7][Wed Sep 27 11:53:49 2006][20078](centralserver.c:170) Unlocking 
> config [7][Wed Sep 27 11:53:49 2006][20078](centralserver.c:170) 
> Config unlocked [3][Wed Sep 27 11:53:49 
> 2006][20078](centralserver.c:173) Failed to connect to any of the auth 
> servers
>
> Can anyone Help.
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
>