[isf-wifidog] (no subject)

[Ben Evans]

Hi Benoit, thanks for that.

I've managed to solve all my existing problems with install and authentication that I had mailed the list about.

Of course I have turned up a new problem, but I want to try some experiments first before putting it on the mailing list.


Cheers

Ben




-----Original Message-----
From: Benoit Grégoire [mailto:bock at step.polymtl.ca] 
Sent: 06 August 2007 06:14
To: wifidog at listes.ilesansfil.org
Cc: Ben Evans
Subject: Re: [isf-wifidog] (no subject)

On Saturday 04 August 2007, Ben Evans wrote:
> Hi there,
>
>
>
> I’ve configured a test environment with the 1260 auth server release 
> running on FC6 and wifidog client 1.1.3_rc1 running on OpenWRt on a 
> Wrap board.

Your're using the official wifidog package from sourceforge?  What version of OpenWRt?

> I get the following output from the wifidog gateway when I try and 
> connect an authenticated client through the gateway.
>
>
>
>
>
> [1264](gateway.c:473) Received connection from 192.168.1.164, spawning 
> worker thread
>
> [1673](client_list.c:108) Added a new client to linked list: IP:
> 192.168.1.164 Token: 9d22f4301e8262a79e2bf3d4c169cc3e
>
> [1673](centralserver.c:151) Auth server returned authentication code 1
>
> [1673](auth.c:218) Got ALLOWED from central server authenticating 
> token 9d22f4301e8262a79e2bf3d4c169cc3e from 192.168.1.164 at 
> 00:0E:35:07:3D:0B - adding to firewall and redirecting them to portal
>
> getsockopt failed strangely: No such file or directory
>
>
>
> At this point the client gets a redirect back to the login page.
>
>
>
> Does the “getsockopt failed strangely: No such file or directory” mean 
> that the gateway is failing to add a rule for the client because some 
> kind of kernel module or other resource is not present?

That's very possible.  Where did you get your wifigod ipk?

Note that there isn't a single getsockopt() call directly in the wifidog sources.  So the problem is probably outside wifidog, your wifidog package wasn't compiled for your openwrt, or some other error occured earlier that triggered this one. 

> I can’t see a rule for the client using iptables. Should I be able to?

Yes, with:
iptables --list --table filter;iptables --list --table mangle;iptables --list --table nat


> Does anyone have any idea how I might identify what resource is absent?

I have no idea, anyone else?


-- 
Benoit Grégoire
Technologies Coeus inc.

No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.11.6/938 - Release Date: 05/08/2007 16:16
 
  

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.11.6/938 - Release Date: 05/08/2007 16:16