Shorewall wont start because of selinux policy

[bmentink]

Hi All,

I am new Fedora and selinux and got caught out by shorewall not being able to start because of a policy problem with perl not being allowed to access a shorewall directory ..... at least that is what the journal log shows.

From my searching the net, this sort of thing was an issue back in F14 days .. is it still a problem?

I am trying to get shorewall going because I need to DNAT some ports for my SIP phone and tried to do it on the standard firewall included in F17, but it doesn't work.

Any idea's either ig getting shorewall going or putting DNAT rules in the stock firewall ..

Cheers,
B

EDIT: I found that by starting shorwall by "/usr/sbin/shorewall start" it works fine ... it's just when started as a service that I get the selinux problems ..

[Darton]

Interesting, do you have a log of the SELinux error?

[bmentink]

Originally Posted by Darton

Interesting, do you have a log of the SELinux error?

No, don't have that log, I will re-create the failure and post the log ...