Must be started by upstart to make sure it runs before any networking daemons

Bug #578030 reported by Jürgen Kreileder
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
shorewall (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: shorewall

shorewall (and shorewall6) should be started by an upstart script in lucid and later. If started from /etc/init.d, shorewall might come up too late. Somebody might have already connected to a service (and may continue communication via an ESTABLISHED rule).

On lucid I see at least mysql, vsftpd, and rsyslog starting before shorewall sets up its rules.

It probably would be best to use the same start-on events as ufw:
,---
| # Make sure we start before an interface receives traffic
| start on (starting network-interface
| or starting network-manager
| or starting networking)
`--

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in shorewall (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.