Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 316327 - net-firewall/shorewall-common-4.2.11-r1: detect option for shorewall-perl
Summary: net-firewall/shorewall-common-4.2.11-r1: detect option for shorewall-perl
Status: RESOLVED DUPLICATE of bug 315747
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Netmon project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 288992
  Show dependency tree
 
Reported: 2010-04-20 09:48 UTC by Massimo Burcheri
Modified: 2010-05-04 06:32 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Massimo Burcheri 2010-04-20 09:48:47 UTC
shorewall6-4.2.11-r1.ebuild has an ewarn noting that the detect option on
interfaces should be avoided...
But shorewall-perl only supports 'detect' or '-' in this column (from man
shorewall-interfaces) while '-' only serves for multi zone interfaces.

Now with the detect option, shorewall does not come up.

Reproducible: Always
Comment 1 Massimo Burcheri 2010-04-25 08:28:02 UTC
This is rather urgent because currently the firewall does not come up at boot:
"Error: Unable to determine the routes through interface eth0"
Comment 2 Massimo Burcheri 2010-05-03 08:25:07 UTC

*** This bug has been marked as a duplicate of bug 315747 ***
Comment 3 Boney McCracker 2010-05-03 19:26:51 UTC
(In reply to comment #2)
> 
> *** This bug has been marked as a duplicate of bug 315747 ***
> 

Are you sure this is a duplicate of my bug 315747?

In 315747, shorewall DOES come up (it just does not appear to, because it is marked as "not started" by rc-status).
Comment 4 Massimo Burcheri 2010-05-04 06:32:12 UTC
I checked that, and YES, it is a duplicate: shorewall itself says it has started, only the rc-status is down.
Anyway I'm not completely sure about the shorewall status since it could not determine the interface address at start by "detect".