Comment 7 for bug 41087
Revision history for this message
| Tero Karvinen (karvinen+launchpad) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Firehol claims it is "already running" but fails to start. Firewall is left completely open.
1) $ sudo /etc/init.d/firehol stop
Stopping iptables firewall: FireHOL ...FireHOL: Clearing Firewall: OK
done.
2) $ sudo /etc/init.d/firehol start
Starting iptables firewall: FireHOL ...Stopping: FireHOL is already running.
done.
What should happen: firewall should be enabled, blocking unwanted traffic.
What actually happens: Firewall is open, letting everything trough.
$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Bug bypass: 'sudo /etc/init.d/firehol restart'
Tested on Ubuntu 5.10 Breezy Badger, firehol 1.231-2 and iptables 1.3.1-2ubuntu1.1. Was reproducible on multiple computers. Vesa Nieminen and "Linux-verkon hallinta" course helped to find this bug.