|
Bugzilla – Full Text Bug Listing |
| Summary: | SFW2-OUT-ERROR -- /var/log/firewall entries on a fresh SUSE Linux 10.0 system | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Bryce Nesbitt <bryce2> |
| Component: | Security | Assignee: | Security Team bot <security-team> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Bryce Nesbitt
2005-11-12 22:30:03 UTC
The SFW2-INext-DROP-DEFLT messages mentioning port 5353 are caused by mdnsd, multicast "echoes" from your own packages. Port 5353 is closed by default. The port 80 SFW2-OUT-ERROR messages are strange but harmless. For some reason netfilter doesn't consider the packages NEW,ESTABLISHED,RELATED. Does it stop logging that if you restart SuSEfirewall2? If the mDNS port is closed by default, why does SUSE enable mDNSd by default? for LAN use. External zone != LAN. |