#44 Multiple TCP_WAIT per browser 'Reload'
mutella is awesome by the way.
i just upgraded to 0.4.3 and it looks good so far, but:
i run mutella on my fileserver/firewall and access it
on another machine through the web interface. if I
click by browser's 'Reload' button and then check the
mutella system's open ports (netstat -ant), there are 5
to 10 TCP_WAIT's for every time I click reload. The
TCP_WAIT connections are from my browsing system to the
system with mutella.
I can't remember this being a problem in 0.4.1, but as
long as I just click the buttons on the webpage itself
(i.e. Overview, Searches, etc.), then it just uses one
ESTABLISHED connection without all the TCP_WAIT's.
Linux 2.4.19 on both systems
Mozilla 1.2.1 on browsing system
Mutella 0.4.3 on mutella system
|Browse| <----> |Mutella/Firewall| <----> |Internet|
It's not that big a problem, but it would only take a
100 or so 'Reload' requests to take up a considerable
chunk of the open ports on a system, especially if it
had a long TCP_WAIT timeout (standard is 240 seconds).
Logged In: YES
user_id=625095
That should obviously be TIME_WAIT.
Err . . . sorry 'bout this . . . kinda. Apparently, the
TIME_WAIT thing is just a quirk of the TCP protocol in
general. From what I can tell, there's nothing wrong with
it as long as you don't have thousands of them lying around.
dannyd