Ticket #545 (new Bug report) — at Initial Version

Opened 13 years ago

Last modified 11 years ago

wifidog svn segfaults and crashes whole kamikaze 8.09 box

Reported by: markus@… Owned by:
Priority: normal Milestone: Not yet assigned to a Milestone
Component: Gateway Version:
Keywords: segfault kamikate Cc:

Description

i have wifidog running on an asus 500gp with kamikaze 8.09 [2.6! broadcom]. yes, i did expect problems with the broadcom wlan as mentioned on openwrt.org but there are non so far. the makefile builds wifidog from svn. build process is just fine. there is one dependency in the original Makefile which i consider to be obsolete though to iptables-mod-extra which does not exist anymore in 2.6???. wifidog is up and running. all iptables rules get applied. wifidog catches traffic perfectly. the first redirect is working too. but wifidog does not redirect - even if pretending too - the client to the success page after receiving ALLOW from the auth server. instead it crashes and the whole box restarts. any ideas?

log: Mar 18 18:36:09 192.168.30.10 wifidog[1077]: Received connection from 10.5.0.176, spawning worker thread Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Processing request from 10.5.0.176 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Calling httpdProcessRequest() for 10.5.0.176 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Locking client list Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Client list locked Mar 18 18:36:09 192.168.30.10 wifidog[1310]: New client for 10.5.0.176 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Added a new client to linked list: IP: 10.5.0.176 Token: 5590bdfc81b1cf724b84b7e89e0d411a Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Unlocking client list Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Client list unlocked Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Locking client list Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Client list locked Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Unlocking client list Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Client list unlocked Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Locking config Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Config locked Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Level 1: Calculated 1 auth servers in list Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Level 1: Resolving auth server [wifiauth.bruesselerplatz.de] Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Locking wd_gethostbyname() Mar 18 18:36:09 192.168.30.10 wifidog[1310]: wd_gethostbyname() locked Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Unlocking wd_gethostbyname() Mar 18 18:36:09 192.168.30.10 wifidog[1310]: wd_gethostbyname() unlocked Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Level 1: Resolving auth server [wifiauth.bruesselerplatz.de] succeeded = [192.168.100.6] Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Level 1: Connecting to auth server wifiauth.bruesselerplatz.de:80 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Level 1: Successfully connected to auth server wifiauth.bruesselerplatz.de:80 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Unlocking config Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Config unlocked Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Connected to auth server Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Sending HTTP request to auth server: [GET /auth/?stage=login&ip=10.5.0.176&mac=00:18:de:a5:8a :c1&token=5590bdfc81b1cf724b84b7e89e0d411a&incoming=0&outgoing=0&gw_id=AP-01 HTTP/1.0M User-Agent: WiFiDog 1.1.5M Host: wifiaut Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Reading response Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Read 246 bytes, total now 246 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: HTTP Response from Server: [HTTP/1.1 200 OKM Date: Wed, 18 Mar 2009 17:39:06 GMTM Server: Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.4 with Suhosin-PatchM X-Powered-By: PHP/5.2.4-2ubuntu5.4M Content-Length: 19M Connection: Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Auth server returned authentication code 1 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Locking client list Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Client list locked Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Got ALLOWED from central server authenticating token 5590bdfc81b1cf724b84b7e89e0d411a from 10.5.0.176 at 00:18:de:a5:8a:c1 - adding to firewall and redirecting them to portal Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Allowing 10.5.0.176 00:18:de:a5:8a:c1 with fw_connection_state 2 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Executing command: iptables -t mangle -A WiFiDog_AP-01_Outgoing -s 10.5.0.176 -m mac --mac-source 00:18:de:a5:8a:c1 -j MARK --set-mark 2 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Waiting for PID 1311 to exit Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Handler for SIGCHLD called. Trying to reap a child Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Handler for SIGCHLD reaped child PID -1 Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Process PID 1311 exited Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Executing command: iptables -t mangle -A WiFiDog_AP-01_Incoming -d 10.5.0.176 -j ACCEPT Mar 18 18:36:09 192.168.30.10 wifidog[1310]: Waiting for PID 1317 to exit Mar 18 18:36:10 192.168.30.10 wifidog[1310]: Handler for SIGCHLD called. Trying to reap a child Mar 18 18:36:10 192.168.30.10 wifidog[1310]: Handler for SIGCHLD reaped child PID -1 Mar 18 18:36:10 192.168.30.10 wifidog[1310]: Process PID 1317 exited Mar 18 18:36:10 192.168.30.10 wifidog[1310]: Redirecting client browser to  http://wifiauth.bruesselerplatz.de:80/portal/?gw_id=AP-01 <-- this is a lie - client does not get redirected. due to lives fairness these are the boxes last words before crashing Mar 18 18:36:45 192.168.30.10 wifidog[1076]: Reading configuration file '/etc/wifidog.conf' Mar 18 18:36:45 192.168.30.10 wifidog[1076]: Parsing token: GatewayID, value: AP-01 Mar 18 18:36:45 192.168.30.10 wifidog[1076]: Parsing token: GatewayInterface?, value: wlan0

Note: See TracTickets for help on using tickets.