[isf-wifidog] failed to connect to any auth servers

Clifford clifford at hdn.net
Lun 4 Aou 20:40:06 EDT 2008


I believe this is not a config error as much as it is a name resolution
error. I see this when I run wifidog in the foreground:

7][Mon Aug  4 17:30:57 2008][29323](util.c:143) Unlocking wd_gethostbyname()
[7][Mon Aug  4 17:30:57 2008][29323](util.c:143) wd_gethostbyname() unlocked
[7][Mon Aug  4 17:30:57 2008][29323](centralserver.c:250) Level 1: Resolving
auth server [127.0.0.1 ] failed


[7][Mon Aug  4 17:33:57 2008][29323](centralserver.c:242) Level 1: Resolving
auth server [127.0.0.1 ]
[7][Mon Aug  4 17:33:57 2008][29323](util.c:137) Locking wd_gethostbyname()
[7][Mon Aug  4 17:33:57 2008][29323](util.c:137) wd_gethostbyname() locked
[7][Mon Aug  4 17:33:57 2008][29323](util.c:143) Unlocking
wd_gethostbyname()
[7][Mon Aug  4 17:33:57 2008][29323](util.c:143) wd_gethostbyname() unlocked
[7][Mon Aug  4 17:33:57 2008][29323](centralserver.c:250) Level 1: Resolving
auth server [127.0.0.1 ] failed
[7][Mon Aug  4 17:33:57 2008][29323](centralserver.c:253) Level 1: Resolving
popular server [www.google.com]
[7][Mon Aug  4 17:33:57 2008][29323](util.c:137) Locking wd_gethostbyname()
[7][Mon Aug  4 17:33:57 2008][29323](util.c:137) wd_gethostbyname() locked
[7][Mon Aug  4 17:33:57 2008][29323](util.c:152) Unlocking
wd_gethostbyname()
[7][Mon Aug  4 17:33:57 2008][29323](util.c:152) wd_gethostbyname() unlocked
[7][Mon Aug  4 17:33:57 2008][29323](centralserver.c:256) Level 1: Resolving
popular server [www.google.com] succeeded = [74.125.19.104]
[7][Mon Aug  4 17:33:57 2008][29323](centralserver.c:276) Level 1: Marking
auth server [127.0.0.1 ] as bad and trying next if possible


The localhost entry definitely exists in /etc/hosts but it seems the
resolver routine wants to use the DNS srever that is specified in
/etc/resolv.conf ??? Is this correct behavior? Is there a work around for
this? It seems that since it can not resolve that name it doesn't try to
connect to the listening auth server which is bound to a socket on
localhost.

Cliff

On Mon, Aug 4, 2008 at 8:17 PM, Don Druce <dondruce at sympatico.ca> wrote:

>  Hi
>
> I think that you did.   Read your original message or check your config
> file.
> I put the 192.168.1.100 there in my reply.
>
>
>
> Clifford wrote:
>
> You wrote "Try a host name of 192.168.1.100" which is exactly what I have
> in my config file ??? Did I miss something?
>
> Thanks
> C.
>
> On Mon, Aug 4, 2008 at 7:41 PM, Don Druce <dondruce at sympatico.ca> wrote:
>
>> Try a host name of 192.168.1.100
>>
>> I am not an expert in any sense of the word, but I am running a Captive
>> Server at home,
>>
>> I do not know what you mean by I am running wifidog and wifidog auth on
>> the same box - I created my Captive Server on a seperate box, and then
>> simply connected that box to my LAN.  I flashed my Linksys router, pointed
>> it to the IP address I used on my box.  All worked as planned - after a few
>> growing pains of course :-))
>>
>>
>> Clifford wrote:
>>
>>  Hi Guys,
>> Sorry for the overactive posting but I am trying to get wifidog as a
>> captive portal solution up and running and keep running into problems. I am
>> running wifidog and wifidog auth on the same box. Basically the APs will
>> talk to this main box for their DHCP and authentication. I see everything
>> start up just fine but then I get the following error messages on the
>> console and in syslog:
>>
>> messages-20080803:Jul 30 20:02:08 wifidog wifidog[8949]: Creating web
>> server on 192.168.1.100:2060
>> messages-20080803:Jul 30 20:02:08 wifidog wifidog[8949]: Failed to connect
>> to any of the auth servers
>>
>> The relevant part of /usr/local/etc/wifidog.conf looks like the following:
>>
>> AuthServer {
>>      Hostname 192.168.1.100 <http://192.168.1.100:2060>
>>     SSLAvailable no
>>     Path /var/www/wifidog-auth
>> }
>>
>>
>> The path certainly exists and contain all of the wifidog-auth files. Could
>> someone shed some light on this for me. I did a google search on this error
>> message and came up empty and there doesn't seem to be too much more to go
>> on in the logs. Thanks in advance.
>>
>> Clifford
>>
>>  ------------------------------
>>
>> _______________________________________________
>> WiFiDog mailing listWiFiDog at listes.ilesansfil.orghttp://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>
>> ------------------------------
>>
>> No virus found in this incoming message.
>> Checked by AVG.
>> Version: 7.5.524 / Virus Database: 270.5.10/1587 - Release Date: 8/2/2008 5:30 PM
>>
>>
>>
>>
>> _______________________________________________
>> WiFiDog mailing list
>> WiFiDog at listes.ilesansfil.org
>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>
>
>  ------------------------------
>
> _______________________________________________
> WiFiDog mailing listWiFiDog at listes.ilesansfil.orghttp://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
> ------------------------------
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.5.10/1587 - Release Date: 8/2/2008 5:30 PM
>
>
>
>
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listes.ilesansfil.org/pipermail/wifidog/attachments/20080804/89a659d6/attachment.htm 


Plus d'informations sur la liste de diffusion WiFiDog