Susefirewall2 fills my logs with reports of dropped packets as a stupid windows network monitor tries to talk SNMP. I've asked them to stop, but often "fixing the internet" is not the easiest way to resolve problems. The SLES9 version of Susefirewall2 lacks the parameter "FW_SERVICES_DROP_EXT="0/0,tcp,161" # Packets to silently reject without log message. So as I've done so often, I upgraded the SLES9 RPM. rpm -Fvh SuSEfirewall2-3.3-18.noarch.rpm Pulled a copy of /etc/sysconfig/Susefirewall2 across from my 9.3 workstation and customised it. Rebooted and it seems to work fine. I'll give it a week and upgrade all the production boxes. Just wanted to share that, (and see if anyone knew why not...) michaelj -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166 No matter how much you pay for software, you always get less than you hoped. Unless you pay nothing, then you get more.