On Mon, 29 Apr 2002, Roger Fischer wrote:

> But I've found there's no way to put a dynamic address into my filter list.

I've been unsuccessful with the same.  A customer of mine's been trying to
get this setup.  They have to configure their external interface by DHCP.  
Although the IP address is almost permanent, the DNS servers and some
other DHCP set values change.  Yes, this is odd, but true.

> Are there any problems, or would I be any less secure by eliminating my address
> and rewriting the above rules like this?
> 
>      pass  in  quick on eth0 proto tcp  from any  port = 25  flags S  keep state
>      pass  in  quick on eth0 proto tcp  from any  port = 80  flags S  keep state
>      block return-rst in log proto tcp  from any  port = 21
>      block return-rst in log proto tcp  from any  port = 22
>      block return-rst in log proto tcp  from any  port = 23

I've seen others in this list use something like:

pass in quick on eth0 proto tcp from any to eth0/32 port 25 flags S keep state
                                            ^^^^^^^

...but I haven't had luck with that either.  I've also seen 0.0.0.0/32
suggested, but as of IPF v3.4.20 that also didn't work for me either.

All I've seen work in this environment is adding a 'to any' between your
from and port number, but I'm not sure that's a good idea.  If an attacker
on the same segment (perhaps this is a cable modem) aimed packets at the
outside MAC of the firewall, I think the traffic would go right through
regardless of where it was destined.  That would be a bad thing.

Furthermore, if they sent that packet from a bogus source address(ie.
192.168.0.20), it might even force the inside interface of the firewall
(192.168.0.1) to respond TO that address causing even more havoc.  
(192.168.0.1 sending an RST to 192.168.0.20, much to the real .20's
surprise)
-- 
mat.

Reply via email to