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 each port.


Thomas

On Friday 23 October 2009 12:48:24 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
> -j ACCEPT
> 
> 
> 
> I will add the source directive when I'm looking it all down, will this
> line in the firewall of all clients will allow bacula to work correctly?
> For some reason, I am having issues getting this to work, the
> configuration is fine, because it can backup and communicate locally
> with no issues. Any tips would be appreciated. Thank you
> 
> ---
> 
> Kind Regards,
> 
> Mr Gabriel
> 

-- 
==========================================
Thomas McMillan Grant Bennett           Appalachian State University
Operations & Systems Analyst            P O Box 32026
University Library                                Boone, North Carolina 28608
(828) 262 6587

Library Systems Help Desk: https://www.library.appstate.edu/help/
==========================================

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users