Hello Davide,
Weel, it seems to be an idiosncrazy in ipfw/freebsd on my side, when
you limit simultaneous connections. It then sort of never gets past
the FIN_WAIT_2 state, waiting for something from the remote side,
which either never gets returned, or gets re-throttled by the ipfw
rules. I actually want to try and see if I can reshuffle the rules
slightly so that the flow changes, and see if I still get the same
problem...
The problem is definitely in the firewalling, as the FIN_WAIT_2's
dissapear when reloading the firewall rules...
I currently have some more in the funny wait state:
Wed Apr 26 10:30:00 2006 1 196.207.45.253
Wed Apr 26 10:30:00 2006 1 196.209.32.160
Wed Apr 26 10:30:00 2006 1 202.156.166.221
Wed Apr 26 10:30:00 2006 1 68.42.173.133
Wed Apr 26 10:30:00 2006 1 70.114.137.133
Wed Apr 26 10:30:00 2006 1 85.250.39.162
Wed Apr 26 10:30:00 2006 1 88.137.176.231
Wed Apr 26 10:30:00 2006 1 88.155.148.150
(Logfile I append every 10 minutes with summary of FIN_WAIT_2
states...)
Tuesday, April 25, 2006, 7:47:06 PM, you wrote:
On Mon, 24 Apr 2006, Jorn Hass wrote:
Davide: Seems like your server somehow didn't close the FIN_WAIT_2
state on my server, due to IPFW firewalling. (Known FreeBSD
problem...) I have subsequently set the firewalling to limitless
connections from troublesome servers like this (Currently 2...),
then it manages to close them, as this seems to happen in the IPFW
throttling stage on simultaneous connections.
Hmm, strange. I tried from my home comcast account and all transactions
where correct.
- Davide
-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]
--
Best regards,
Jornmailto:[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]
