Notice: This is NOT about mailing list format!
Upon looking for ipfilterd on SGI machines, I found that chkconfig said
it was not there, even though /usr/etc/ipfilterd was present. Also, the
ipfilterd man pages simply said that the filter syntax was the same as
for netsnoop, which you have to purchase. (Thanks to Chan Wilson for
posting the man pages for netsnoop and ipfilterd!)
Ed Gaines of SGI investigated ipfilterd for me, and this is what he
> Okay, I figured it out. The ipfilterd stuff loads when you select the
> eoe2.sw.ipgate component from the eoe2 stuff on the inst menu. I didn't
> so my machine doesn't have it. My gateway did, though.
> I looked at the ipfilterd.conf file, and I remain convinced that all you
> need is the filter syntax (documentated in the netvis user's guide).
> As to firing up the ipfilterd daemon, the /etc/init.d/network script already
> checks for it with chkconfig and launches it (at startup) if the chkconfig
> is successful. The gotcha seems to be that installation of the ipgate
> software doesn't seem to put a ipfilterd file in /etc/config. So I made
> my own (with the command cp /etc/config/network /etc/config/ipfilterd),
> issued a chkconfig, and lo and behold, there it was! So that'll get the
> daemon launched.
> Want a manual?
- Mac Allen