When did you get the VERRRRY EXPENSIVE SUPPORT CONTRACT for this news group? If you insist on acting like a spoiled customer we could treat you like a spoiled customer, get cash up front and only provide the amount of help paid for and repeat.
Remember this group is a volunteer effort and if you get people to decide not to help you they will not, its not their job. I would hope that you keep it in mind and stop treating it like it was. If you really want commercial support send mail to Darren and ask for a quote. now on to the message On Sun, 28 Dec 2003 10:33:05 -0500 fbsd_user <[EMAIL PROTECTED]> wrote: > 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. That is all very nice but have you considered the problem could be IPFilter/FreeBSD/version/ftpd/ftp client/any applied patches specific? Or that it may not exist on the boxes of people who could fix it? By giving the asked for tcpdump files you are helping solve your problem. You see this would allow the developers to say "Thats what happening, now why ain't it working?" > > 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. You could read the source and improve the documentation, FreeBSD is always taking patches, including docs. > > 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. Why don't you, the src code is located in /usr/src/sbin/sysctl(my box) and you can chase everything down from there. > > 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. the docs, err code, can be found here(my box) : /usr/src/sys/contrib/ipfilter/netinet and it really does tell you exactly what it does. marc
