Now I saved a tcpdump on this (running pre13):
15:04:33.300000 mylinux.mydom.ain.1118 > mercury-novell-mailer.de.smtp: S 1304940560:1304940560(0) win 512 <mss 1460> (ttl 64, id 56645)
15:04:36.290000 mylinux.mydom.ain.1118 > mercury-novell-mailer.de.smtp: S 1304940560:1304940560(0) win 15360 <mss 1460> (ttl 64, id 56656)
15:04:36.330000 mercury-novell-mailer.de.smtp > mylinux.mydom.ain.1118: . ack 1304940561 win 16080 (ttl 119, id 64164)
15:04:36.330000 mylinux.mydom.ain.1118 > mercury-novell-mailer.de.smtp: R 1304940561:1304940561(0) win 0 (ttl 64, id 56658)
After this netstat shows: SYN_SENT, timer off (0.00/0).
I was even able to reproduce this multiple times now..
Why is Linux sending a RST? There's a SYN ACK missing, right?
So that's maybe correct (I didn't read the RFC), but dropping the timer
and block the connect() not, IMHO ;-)
You can test it yourelf by telneting the offending host (if you need the
address for testing, please tell me, Alan- I don't want to post it here
to protect the innocent(?) :-)
73,
Olaf
-- ------------------------------------------------------------------------- ! dc1ik@bofh.ampr.org - erb@inss1.etec.uni-karlsruhe.de ! Finger me for ! ! <A HREF="http://home.pages.de/~grotto/">click</A> ! PGP-public key! -------------------------------------------------------------------------