> -----Original Message----- > From: John D. Hardin [mailto:[EMAIL PROTECTED]] > > You can't, not explicitly. ipfwadm and the 2.0 kernel only recognize > TCP, UDP, ICMP and ALL. > > What you can do is, at the end of your firewall file block TCP, UDP > and ICMP explicitly on the Inet interface. Then add rules to deal with > "other" traffic... > > ipfwadm -I -a deny $INET -p tcp > ipfwadm -I -a deny $INET -p udp > ipfwadm -I -a deny $INET -p icmp > > then, accept but don't log: > > ipfwadm -I -a accept $INET > > ... John, Thanx for your response. I haven't looked at it yet, but does the 2.2 kernel and ipchains provide a better solution to this problem? I guess I prefer shutting off the world to everything except things I want versus shutting off what I can then turn on everything else. I thought of another possible solution although I'm not sure how secure this would be. I maybe could allow everything in only for the IP address of the multicast router (24.93.0.234) -- or combining your idea and mine, deny the three protocols and allow everything else just for that IP address. For reference, the log entry in question was: Mar 24 00:07:44 homebase kernel: IP fw-in rej eth1 PROTO=2 24.93.0.234 224.0.0.1 L=28 S=0x00 I=34902 F=0x0000 T=1 Dave G. _______________________________________________ Masq maillist - [EMAIL PROTECTED] http://tiffany.indyramp.com/mailman/listinfo/masq Admin requests can be handled by web (above) or [EMAIL PROTECTED]
