<div dir="ltr">It appears to start just fine with that. Is the web status page on port 2060?<br><br>Thanks<br>Clifford<br><br><div class="gmail_quote">On Tue, Jul 29, 2008 at 3:18 PM, acv <<a href="mailto:acv@miniguru.ca">acv@miniguru.ca</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Yeah, you'll have to set that variable every time you run wifidog. Kind<br>
of a pain.<br>
<br>
Alex<br>
<br>
On Tue, Jul 29, 2008 at 03:13:05PM -0400, Clifford Thurber wrote:<br>
> Date: Tue, 29 Jul 2008 15:13:05 -0400<br>
<div><div></div><div class="Wj3C7c">> From: "Clifford Thurber" <<a href="mailto:clifford@hdn.net">clifford@hdn.net</a>><br>
> To: "WiFiDog Captive Portal" <<a href="mailto:wifidog@listes.ilesansfil.org">wifidog@listes.ilesansfil.org</a>><br>
> Subject: Re: [isf-wifidog] output<br>
><br>
> Ok. So set that variable and then restart wifidog?<br>
><br>
> On Tue, Jul 29, 2008 at 3:11 PM, acv <<a href="mailto:acv@miniguru.ca">acv@miniguru.ca</a>> wrote:<br>
><br>
> > Well, I'm at work right now so I don't have access to a box where<br>
> > I can trash the firewall at will. If you can provide me a temp account with<br>
> > root, I might be able to debug this now, otherwise it will have to wait.<br>
> ><br>
> > Work around is to disable error checking in glibc:<br>
> ><br>
> > In BASH:<br>
> ><br>
> > export MALLOC_CHECK_=0<br>
> ><br>
> > In CSH:<br>
> ><br>
> > setenv MALLOC_CHECK_=0<br>
> ><br>
> > Alex<br>
> ><br>
> > On Tue, Jul 29, 2008 at 02:36:24PM -0400, Clifford Thurber wrote:<br>
> > > Date: Tue, 29 Jul 2008 14:36:24 -0400<br>
> > > From: "Clifford Thurber" <<a href="mailto:clifford@hdn.net">clifford@hdn.net</a>><br>
> > > To: "WiFiDog Captive Portal" <<a href="mailto:wifidog@listes.ilesansfil.org">wifidog@listes.ilesansfil.org</a>><br>
> > > Subject: Re: [isf-wifidog] output<br>
> > ><br>
> > > Interesting. Can I provide you with anything else that might help you?<br>
> > ><br>
> > > Thanks<br>
> > > Clifford<br>
> > ><br>
> > > On Tue, Jul 29, 2008 at 2:32 PM, acv <<a href="mailto:acv@miniguru.ca">acv@miniguru.ca</a>> wrote:<br>
> > ><br>
> > > > On Tue, Jul 29, 2008 at 01:41:04PM -0400, Clifford Thurber wrote:<br>
> > > > > Date: Tue, 29 Jul 2008 13:41:04 -0400<br>
> > > > > From: "Clifford Thurber" <<a href="mailto:clifford@hdn.net">clifford@hdn.net</a>><br>
> > > > > To: <a href="mailto:acv@miniguru.ca">acv@miniguru.ca</a><br>
> > > > > Subject: output<br>
> > > > ><br>
> > > > > Hi Alex,<br>
> > > > > This is what I am seeing now:<br>
> > > > ><br>
> > > > [ ... snip ... ]<br>
> > > > > called. Trying to reap a child<br>
> > > > > [7][Mon Jul 28 14:47:27 2008][26253](gateway.c:263) Handler for<br>
> > SIGCHLD<br>
> > > > > reaped child PID -1<br>
> > > > > [7][Mon Jul 28 14:47:27 2008][26253](util.c:121) Process PID 26358<br>
> > exited<br>
> > > > > [7][Mon Jul 28 14:47:27 2008][26253](centralserver.c:327) Level 1:<br>
> > > > > Connecting to auth server <a href="http://auth.ilesansfil.org:80" target="_blank">auth.ilesansfil.org:80</a><br>
> > > > > *** glibc detected *** wifidog: free(): invalid pointer:<br>
> > > > 0x0000003ea656a0c0<br>
> > > > > ***<br>
> > > > > ======= Backtrace: =========<br>
> > > > > /lib64/libc.so.6[0x3ea6278158]<br>
> > > > > /lib64/libc.so.6(cfree+0x76)[0x3ea627a796]<br>
> > > > > wifidog[0x4081ef]<br>
> > > > > wifidog[0x407d35]<br>
> > > > > wifidog[0x40baab]<br>
> > > ><br>
> > > > Congratulations, you found a hidden bug. Most versions of libc silently<br>
> > > > ignore when an application tries to free() memory that's already been<br>
> > > > free()'d. Gentoo, Ubuntu and apparently now Fedora have started<br>
> > enabling<br>
> > > > optional behaviour in the free() system call to exit out when that<br>
> > happens.<br>
> > > > This was originally implemented for debugging purpose.<br>
> > > ><br>
> > > > Now we have to find where free() gets called twice... Probably when<br>
> > > > connecting<br>
> > > > to the Auth Server.<br>
> > > ><br>
> > > > Alex<br>
> > > ><br>
> ><br>
> > > _______________________________________________<br>
> > > WiFiDog mailing list<br>
> > > <a href="mailto:WiFiDog@listes.ilesansfil.org">WiFiDog@listes.ilesansfil.org</a><br>
> > > <a href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog" target="_blank">http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog</a><br>
> ><br>
> > _______________________________________________<br>
> > WiFiDog mailing list<br>
> > <a href="mailto:WiFiDog@listes.ilesansfil.org">WiFiDog@listes.ilesansfil.org</a><br>
> > <a href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog" target="_blank">http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog</a><br>
> ><br>
<br>
> _______________________________________________<br>
> WiFiDog mailing list<br>
> <a href="mailto:WiFiDog@listes.ilesansfil.org">WiFiDog@listes.ilesansfil.org</a><br>
> <a href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog" target="_blank">http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog</a><br>
</div></div><br>_______________________________________________<br>
WiFiDog mailing list<br>
<a href="mailto:WiFiDog@listes.ilesansfil.org">WiFiDog@listes.ilesansfil.org</a><br>
<a href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog" target="_blank">http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog</a><br></blockquote></div><br></div>