Adam, I had not seen the problem before tonight when I really tried to beat
my soekris 4511 to a pulp. I managed to kill it just like you describe. I
started at the top of the page and hit every link just as fast as soekris
would deliver them, got all the way down and back up to Aliases before I got
a Server Busy page, I hit back, and managed to click a few more pages before
I lost all connectivity to the GUI. Now all I get is "Cannot find server"
yet I still have access to outside pages and mail still seems to go thru
fine. I generally use IE but Firefox cannot get to the GUI right now either.
I hooked up my laptop to the console to reboot it and noticed that the
wireless link was down and would not connect. After a reboot, things are
almost normal, wireless is still down now but that may be a different issue.
I have just hammered it with Firefox .08 and I cannot kill the GUI with it.
Went back to IE and could not make it down the list before getting locked
out again. This is using IE6 SP1, and I suspect it could be a browser issue
but for the life of me can't figure why the GUI would respond any different
using one or the other.
> -----Original Message-----
> From: Adam Nellemann [mailto:adam at nellemann dot nu]
> Sent: Tuesday, June 22, 2004 6:55 PM
> To: Dinesh Nair
> Cc: Filip Onkelinx; m0n0wall at lists dot m0n0 dot ch
> Subject: Re: [m0n0wall] Re: [m0n0wall-dev] Still got GUI
> hangs with 1.1b14?!?
> Dinesh Nair wrote:
> > On Mon, 21 Jun 2004, Adam Nellemann wrote:
> >>Filip Onkelinx wrote:
> >>>Hi Adam,
> >>>It looks like this is only happening using I.E. , did you try with
> >>>any other browser (Mozilla FireFox, Opera, ...) ? I suspect your
> >>>problem is related to the way IE handles persistent
> (trying to keep
> >>>persistent connections open as long as possible , or opening too
> >>>many simultaneous connection threads)
> >>(See my previous post in response to Joey Morin.)
> >>Still sounds like it must have been introduced when that connection
> >>(or whaterver) limit was imposed on mini_httpd, but what do I know?
> > i wrote the patch to mini_httpd to return a 503 http error (server
> > overloaded) when the connection limit is reached. iianm, manuel has
> > set the web server to max 8 simultanoues connections in the normal
> > webgui and
> > 16 in the captive portal.
> > Regards, /\_/\ "All dogs go to heaven."
> > dinesh at alphaque dot com (0 0) http://www.alphaque.com/
> > +====+
> > | for a in past present future; do
> > | for b in clients employers associates relatives
> neighbours pets; do |
> > | echo "The opinions here in no way reflect the opinions
> of my $a $b." |
> > | done; done
> > +====+
> Hmm, I'm afraid I don't know which error I got precisly (not
> the least due to the obscure way IE reports these errors)?
> I'll take a closer look the next time it happens...
> But still, I should think that if this were really related to
> the max.
> connection limit recently imposed, these connections would
> time out or some such, so I would be able, after a wait, to
> connect again. Since I've tried waiting 12 hours (including
> reseting my client PC at least
> once) without any change, I guess it must be something else?
> Anything I can do to gathe further information for you about this?
> (And am I still the only one seeing this? If so, I guess it
> could be some obscure RAM or CF error?)
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch