To answer your questions. The bogus packets only show up in the log
when doing FTP. These log messages do not occur under any other
circumstances. The log is empty accept when I do FTP.  I have gone
to FTP1.FreeBSD.org through FTP14.FreeBSD.org. used Windows free
shareware WS_FTP pgm, windows native DOS FTP and from FBSD box, FTP
to FreeBSD sites and FTP from my FBSD boxes on my LAN to the FBSD
gateway to user home directory and the anonymous FTP. In all cases
there are no log messages until I say bye to end the FTP session,
then these bogus packets show up in  the ipmon log. When I remove
the  ipnat FTP/proxy rule from the ipnat rules file and reload
filter rules followed by the reload of the ipnat rules the problem
goes away. I don't have to be a  genius rocket scientist to
comprehend where the problem is, plus with 30 years technical
experience installing mainframe operating systems I know how to
determine where an problem is located.  I have determined where the
problem is and have described it in sufficient detail, and have had
other posters verify they can reproduce it.  Process of elimination
points to the problem being in the ipnat FTP/proxy code. It's now
the author of the ipnat FTP/proxy code's, turn to use what ever
tools he needs to prove other wise.

As I posted in an earlier reply, maybe changing one or more of the
sysctl values may correct the problem, but with out any
documentation on their meanings I can do nothing about tweaking  the
sysctl values myself.

Why don't somebody from this list post the meanings of the sysctl
knobs, like the one that controls the expiring of the temp proxy
rules or the one that controls the expiring of the entries in the
keep state table. Those two sure would be likely candidates bearing
closer inspection to see their effect on the stated problem.

Or how about an complete description of just what the  ipnat
FTP/proxy functions does internally and how it's use changes what
filter rules are needed.


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of mouss
Sent: Sunday, December 28, 2003 7:43 AM
To: [EMAIL PROTECTED]
Cc: horio shoichi; [EMAIL PROTECTED]
Subject: Re: BUG in ipnat FTP proxy

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