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.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of horio shoichi
Sent: Saturday, December 27, 2003 8:38 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: BUG in ipnat FTP proxy

On Sat, 27 Dec 2003 08:32:10 -0500
"fbsd_user" <[EMAIL PROTECTED]> wrote:
> I running FreeBSD 4.9 gateway with IPFILTER version 3.4.31
firewall.
> Have ms/windows boxes on private lan behind firewall. Have IPNAT
> running with FTP proxy enabled. From the ms/win lan users view
point
> every things is working fine for FTP client active and passive
> access to public FTP sites. The problem is I am finding default
log
> messages for inbound port 21 requests in the log file. The out
rule
> which passes the port=21 packet is an keep state rule and it looks
> like that when the FTP session conversation is completed the keep
> state table is releasing some left over stuff.
>
> In an effort to better understand what I was seeing I set up an
test
> configured as follows.
>
> The contents on my ipnat.rules file
> # Provide special NAT services for Active/Pasv FTP from LAN users.
> map rl0 10.0.10.0/29 -> 0/32 proxy port 21 ftp/tcp
>
> It's been 10 days and no response to my bug report.
> Is this mailing list the correct place to report bugs so the
author
> sees them?
>
<snip>

You haven't shown ipfilter bug. To see precisely how ipfilter
responded in each case, you could have hooked, say, tcpdump. Then
you could have seen what the two connected party had, and hadn't,
done. Note there are implementations which cut corners of tcp,
both in servers and clients.



horio shoichi

Reply via email to