Howdy folks,

I'm getting lots of lot messages aong the lines of:

Jan 21 10:01:29 coyote ipmon[93472]: 10:01:28.664180 rl1 @0:52 b 206.65.183.140,80 -> 
192.168.23.211,34337 PR tcp len 20 52 -A IN

My understanding is that this is the result of a NAT connection being
closed done and a delayed packet comes from the web server a NATed user
was accessing, and thus the firewall catches this with my default block
all.

So I thought I would force a port range:

map rl1 192.168.23.0/24 -> rl1/32 portmap tcp/udp 48000:50000

And explicitly /not/ log that range:

block in quick on rl1 proto tcp from any to any port 48000 >< 50000

This didn't work.

After googling for a bit and delving into the FAQ, I've discovered that
on inbound packets ipnat occurs before ipfilter. I should've guess this:
when it says that 206.65.183.140,80 -> 192.168.23.211,34337 it's kinda
obvious that NATing has already occured before this ipf rule got hit.

I'd still like to not lgo these after-close port 80 packets, and I don't
want to try and force all workstations to use a specific port range. My
theory is that I can do this:

block in quick on rl1 proto tcp from any port = 80 to 192.168.23.0/24

Does this make sense? It doesn't /appear/ to be causing any problems ...

Also, is my understanding of why I'm getting these packets in teh first
place likely correct?

Thanks in advance,

- Tillman

-- 
``You cannot create experience. You must undergo it.''
    - Albert Camus

Reply via email to