Bug 303851
Summary: | ip6tables startup complains "never matched protocol: 51" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
Component: | system-config-securitylevel | Assignee: | Thomas Woerner <twoerner> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | fortran, sconklin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 1.7.0-6.fc7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-11-15 03:41:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Jaegermann
2007-09-24 19:10:14 UTC
Assigning to system-config-securitylevel. system-config-securitylevel-1.7.0-6.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-securitylevel' The same thing happens in Fedora 8. system-config-securitylevel-1.7.0-6.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report. I am getting this error on my Fedora 8 startup (so I'm not sure if it's captured
by a log). As in the original report, there is a port 51 line in
/etc/sysconfig/ip6tables that is probably causing it. Also:
> rpm -q system-config-firewall
system-config-firewall-1.0.12-4.fc8.noarch
Since this is now in a different component and F level, should I open a new bug?
Please use "lokkit -q" to update your firewall configuration and the problem should be gone. (In reply to comment #6) > Please use "lokkit -q" to update your firewall configuration and the problem > should be gone. So it did. Thank you. |