This is what I use on all my clients:
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9102 -j ACCEPT
I had only one issue which was on one server and I couldn't connect. I moved
the rule to the top of the list of rules and then I was able to connect. I
usually use a separate rule for eac
Gabriel - IP Guys wrote:
>
>
> Dear All,
>
>
>
> I need some fresh eyes on this at the moment. I made this entry in the
> firewall scripts of my Linux servers which will be running some
> component of Bacula
>
>
>
> iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 9101:9103
>
Gabriel - IP Guys wrote:
>
>
> Dear All,
>
>
>
> I need some fresh eyes on this at the moment. I made this entry in the
> firewall scripts of my Linux servers which will be running some
> component of Bacula
>
>
>
> iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 9101:9103
>
Dear All,
I need some fresh eyes on this at the moment. I made this entry in the
firewall scripts of my Linux servers which will be running some
component of Bacula
iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 9101:9103
-j ACCEPT
I will add the source directive when I'm
