Well, tcpdump (on both sides) will show what happened during the session termination: was there any RST? is there a timeout issue? were FINs acked or not?

Also, can you do your tests with other servers such as ftp.freebsd.org, ftp.netbsd.org, ftp.free.fr?

This in turn will allow people here to better understand the "problem" and see whether it can be "fixed" or not.

I've seen similar logs for http traffic (certainly related to the "stop" button of the browser), but I didn't really check the details.

mouss


fbsd_user wrote:


Sorry but I do not agree with your opinion. Another reader posted he
gets the same results as I do, and I responded to him through this
list with more conversation about were the bug is and what the
circumstances are that causes it. Running an tcpdump is not going to
show me how the 'ipnat ftp/proxy' temp rules are launched and
removed with in the timing of the close session request, that's
happening internal to ipnat processing. My log shows me enough to
know where the problem is. Before one says right out of hand that
there is no bug, one should first try to reproduce it and use what
ever tools they think are necessary to disprove it, which may lead
to another person verifying it's a bug.





Reply via email to