Skip to content
This repository has been archived by the owner on Jan 24, 2019. It is now read-only.

Not adding a service #29

Open
waqarkhan3389 opened this issue Jul 13, 2015 · 1 comment
Open

Not adding a service #29

waqarkhan3389 opened this issue Jul 13, 2015 · 1 comment

Comments

@waqarkhan3389
Copy link

waqarkhan3389 commented Jul 13, 2015

I have cloned the git repo and used the following in my node config:

node testnode2 {

firewalld::service { 'testservice':
description => 'service',
ports => [{port => '65000', protocol => 'tcp',},],
}
}

This creates a config file in /etc/firewalld/services on the node but the service is not applied. I.e. when doing firewall-cmd --list-services it doesn’t show. And a manual firewalld restart didn’t pick up this file either. I have to do the following to get it to allow the port:

firewall-cmd --permanent --add-service=testservice
firewall-cmd --reload

Is this a config problem?

@asasfu
Copy link

asasfu commented Jul 18, 2015

What you're doing only creates the service's xml file; so in this case testservice.xml. You still need to create your zone and apply that rule, whether as a rule to allow anything to that 'service' which happens to be one port in that example or whether to apply that service into a rich_rule inside of the zone you create so you can apply source/destination rules to it as well. Keep an eye on some of the commits to this repo as we're likely doing some changes in the nearish future to improve it and possibly merge it with another module.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants