Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 108096 - /etc/rc.d/init.d/ntp refers to OLD iptables/firewall name
Summary: /etc/rc.d/init.d/ntp refers to OLD iptables/firewall name
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: CambridgeBlocker
TreeView+ depends on / blocked
 
Reported: 2003-10-27 17:16 UTC by Gene Czarcinski
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version: 4.2.0-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-10-28 10:15:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gene Czarcinski 2003-10-27 17:16:05 UTC
Description of problem:

The start/stop script for ntp refers to the old iptables name
(RH-Lokkit-0-50-INPUT) rather than the new iptables name (RH-Firewall-1-INPUT).

Comment 1 Harald Hoyer 2003-10-28 10:15:15 UTC
THX!

Comment 2 Vadim Nasardinov 2004-01-24 23:02:16 UTC
I'm upgrading my Red Hat Linux 8.0 box to Fedora Core 1.  I don't know
if this has been fixed already or not, but ifup-post has the same problem:

$ cat -n /etc/sysconfig/network-scripts/ifup-post | grep Lokkit
    77        iptables -L -n 2>/dev/null | grep -q RH-Lokkit-0-50-INPUT ; then
    81                          if ! iptables -L RH-Lokkit-0-50-INPUT -n | grep -q "$nameserver.* --sport 53 " ; then
    82                                  iptables -I RH-Lokkit-0-50-INPUT -m udp -s $nameserver/32 --sport 53 -d 0/0 --dport 1025:65535 -p udp -j ACCEPT


Comment 3 Harald Hoyer 2004-01-26 09:30:02 UTC
created new bug #114278 for the last comment


Note You need to log in before you can comment on or make changes to this bug.