Upload some version of truss compiled for FreeBSD 4.x (e.g.
http://m0n0.ch/wall/downloads/truss) through exec.php, mark it as
executable and run it on the PID of the captive portal mini_httpd
process (i.e. /path/to/truss -o /tmp/truss.log -p <mini_httpd-pid> &).
Another thing to try would be to kill the captive portal mini_httpd,
upload the mini_httpd that comes with 1.2b3 (pull it out of
rootfs-1.2b3, usr/local/bin/mini_httpd), rename the existing
mini_httpd to something else, copy the uploaded mini_httpd to the
original location (/usr/local/bin/mini_httpd), make sure it's marked
as executable, and hit "save" on the captive portal page to make it
Jonathan De Graeve
jonathan dot de dot graeve at imelda dot be
----- Original Message -----
From: "Burkhart, John T." <JOHN dot T dot BURKHART at saic dot com>
To: <mk at neon1 dot net>
Cc: <m0n0wall dash dev at lists dot m0n0 dot ch>; <jonathan dot de dot graeve at imelda dot be>
Sent: Thursday, June 09, 2005 10:16 PM
Subject: RE: [m0n0wall-dev] Unstable mini_httpd for captive portal
> -----Original Message-----
> From: Burkhart, John T.
> To: 'mk at neon1 dot net '
> Cc: 'm0n0wall dash dev at lists dot m0n0 dot ch '; 'jonathan dot de dot graeve at imelda dot be '
> Sent: 6/9/2005 1:11 PM
> Subject: RE: [m0n0wall-dev] Unstable mini_httpd for captive portal
> Sorry but there is not a truss binary available on the cd iso rendering
> and there appears to be no error checking for this.
> So, I took a look at the processes running on the system (notes and
> outputs are enclosed). <speculation> I suspect that the system is
> getting confused because of port 8000 still being on? </speculation>
> Also, I have not seen this behavior in the HTTP login mode.
> The only other speculation I have is that this may be happening after an
> authentication TIMEOUT. I may be way off base and will go down that
> path if I need to.
> Do you have truss hidden in a directory somewhere or a renamed binary?