Web server manager wrote: >> >>>In particular, does >>> >>>block in quick on xl1 from any to any >>>pass out quick on xl1 proto tcp from any to any flags S keep state keep frags >>>pass out quick on xl1 proto udp from any to any keep state >>>pass out quick on xl1 proto icmp from any to any keep state >>> >>>allow in icmp-type 3 code 4 for a stateful tcp connection? >>> >>Yes. >> > > Are you sure about that? When we started using IP Filter recently (V3.4.25, on > Solaris 2), I thought the same but rapidly found that it wasn't really true, > with a proportion of such ICMPs being logged as blocked. I assumed that was > because the ICMPs were from intermediate "infrastructure" (routers, terminal > server sending source quench for a saturated dialup connection, etc.) rather > than the end-point recorded by "keep state" - the log entries identified the > sources and that explanation certainly seemed to fit. Does that sound > reasonable? Or should the ICMP still have been recognised, so that the > blocking implies something else was wrong?
Depends what you mean by "am I sure".. =) I'm sure that IP Filter *should* have let them pass. There are a variety of reasons it may not have, the most likely being lag time. Albeit I've not delved into the code, I understand that IPF does have the ability to recognize all of these cases. > Our configuration files are currently allowing echo, squench, redir, > unreach, and timex in explicitly, plus any other ICMP that's recognisably > associated with stateful TCP connections. I don't allow any of these explicitly, but they all come through for me. Then again I'm on a small home network. At my old job, IPF guarded a small internal network with no servers, and I was asked to put a server behind it before I left (the company more or less when out of business, so all our servers in the datacenter became one server housed locally - don't ask me why)... but I never got to look at the effects of that... Phil -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, 1759
