[isf-wifidog] (no subject)
ben at benevans.demon.co.uk
Sam 4 Aou 08:23:43 EDT 2007
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.
I get the following output from the wifidog gateway when I try and connect
an authenticated client through the gateway.
(gateway.c:473) Received connection from 192.168.1.164, spawning
(client_list.c:108) Added a new client to linked list: IP:
192.168.1.164 Token: 9d22f4301e8262a79e2bf3d4c169cc3e
(centralserver.c:151) Auth server returned authentication code 1
(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?
I can’t see a rule for the client using iptables. Should I be able to?
Does anyone have any idea how I might identify what resource is absent?
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.11.4/935 - Release Date: 03/08/2007
-------------- next part --------------
An HTML attachment was scrubbed...
Plus d'informations sur la liste de diffusion WiFiDog