Joel E. Carlson wrote: <SNIP>
>>> >>> block in log on interface proto icmp all >>> pass in on interface proto icmp from \ >>> any to ip icmp-type echo >>> pass in on interface proto icmp from \ >>> any to ip icmp-type echorep >>> >>Nope. Echo is 8, and Echoreply is 0. You need *either* >> >>pass in on interface proto icmp from any to ip icmp-type 3 code 4 >> <SNIP> > > Excellent I already had the keep state in on my services. Thanks for > checking out my icmp rules and pointing out how I could optimize on > one. Every little bit counts. ;-) Huh? When I said "either" I meant "either this or that" as in, one of the two options that I gave ... I wasn't saying you need only one of your rules from above. I was saying you only needed one of the two options I was about to present. As for your rules, the first allows people to ping you whilt he other allows in responses to your pings, I believe. So the first one is only necessary if you want people to be able to ping you. As for the second one, if you're keeping state on outgoing traffic ICMP traffic, you won't need it. Phil -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, 1759
