Bug 3377 - /etc/init.d/iptables is not available - so one cannot do "/etc/init.d/iptables stop"
Summary: /etc/init.d/iptables is not available - so one cannot do "/etc/init.d/iptable...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2011-11-17 09:25 CET by Shlomi Fish
Modified: 2012-02-22 18:20 CET (History)
1 user (show)

See Also:
Source RPM: iptables-1.4.12.1-8.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Shlomi Fish 2011-11-17 09:25:54 CET 
Description of problem:

/etc/init.d/iptables is not available - so one cannot do "/etc/init.d/iptables stop". Right now the procedure for nullifying the iptables rules is more complex and caused my laptop to become unavailable after I did it improperly.

Please provide /etc/init.d/iptables again.
Comment 1 Manuel Hiebel 2011-11-17 12:26:32 CET 
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

Keywords: (none) => Triaged
Assignee: bugsquad => tmb

Comment 2 Shlomi Fish 2011-11-17 14:27:32 CET 
(In reply to comment #0)
> Description of problem:
> 
> /etc/init.d/iptables is not available - so one cannot do "/etc/init.d/iptables
> stop". Right now the procedure for nullifying the iptables rules is more
> complex and caused my laptop to become unavailable after I did it improperly.
> 
> Please provide /etc/init.d/iptables again.

OK, now I found out (after examining the iptables' .spec file) that /etc/init.d/iptables is now present in /usr/lib64/iptables (or "/usr/lib" on 32-bit systems) if systemd is enabled. So a valid workaround would be to run "/usr/lib64/iptables stop" as root.
Comment 3 Thomas Backlund 2011-11-17 17:50:55 CET 
Actually since we are switching to systemd, iptables have been converted to native systemd service, so the right command is:

systemctl stop iptables.service


or you can use the "old" service command, so:

service iptables stop
Comment 4 Marja Van Waes 2012-02-22 13:39:25 CET 
(In reply to comment #3)
> Actually since we are switching to systemd, iptables have been converted to
> native systemd service, so the right command is:
> 
> systemctl stop iptables.service
> 
> 
> or you can use the "old" service command, so:
> 
> service iptables stop

@ Shlomi

Does that work OK for you, so that this bug can be closed?

CC: (none) => marja11

Comment 5 Shlomi Fish 2012-02-22 18:20:40 CET 
(In reply to comment #4)
> (In reply to comment #3)
> > Actually since we are switching to systemd, iptables have been converted to
> > native systemd service, so the right command is:
> > 
> > systemctl stop iptables.service
> > 
> > 
> > or you can use the "old" service command, so:
> > 
> > service iptables stop
> 
> @ Shlomi
> 
> Does that work OK for you, so that this bug can be closed?

I guess. Closing.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.