Hi all,
In case anyone else is looking to solve this problem in a standard way, I
have written a fairly simple module that attempts to close out this gap:
https://forge.puppetlabs.com/alexharvey/firewall_multi/readme
Best regards,
Alex
On Wednesday, November 30, 2011 at 11:17:25 AM UTC+11, Moh
in case it help someone, I got it too do what I needed this way:
# Allow netbackup
define allow_netbackup() {
firewall { "300 allow netbackup traffic from ${name}":
proto => 'tcp',
dport => [13724,1556,10102,10082],
source => $name,
action
Cool. Thanks guys.
On Tue, Nov 29, 2011 at 5:23 PM, Jacob Helwig wrote:
> On 2011-11-29 13:05 , Mohamed Lrhazi wrote:
>> Hi,
>>
>> am trying this rule:
>>
>>
>> firewall { '100 allow ssh from GUNET':
>> proto => 'tcp',
>> dport => '22',
>> source => ['10.0.0
On 2011-11-29 13:05 , Mohamed Lrhazi wrote:
> Hi,
>
> am trying this rule:
>
>
> firewall { '100 allow ssh from GUNET':
> proto => 'tcp',
> dport => '22',
> source => ['10.0.0.0/8','192.168.0.0/16',],
> action => accept,
> }
>
>
> and it on
On Tue, Nov 29, 2011 at 10:05 PM, Mohamed Lrhazi wrote:
> firewall { '100 allow ssh from GUNET':
> proto => 'tcp',
> dport => '22',
> source => ['10.0.0.0/8','192.168.0.0/16',],
> action => accept,
> }
>
>
> and it only seems to add a rule for the first
Hello,
While I have never used this particular package, I am curious about that
trailing comma:
source => ['10.0.0.0/8','192.168.0.0/16',],
or
source => ['10.0.0.0/8','192.168.0.0/16'],
Charles Buckley
On Tue, Nov 29, 2011 at 2:05 PM, Mohamed Lrhazi wrote:
> Hi,
>
> am trying th
Hi,
am trying this rule:
firewall { '100 allow ssh from GUNET':
proto => 'tcp',
dport => '22',
source => ['10.0.0.0/8','192.168.0.0/16',],
action => accept,
}
and it only seems to add a rule for the first subnet. The second is
silently igno
