Re: can't connect to remote client

>>>>> On Thu, 4 Sep 2025 15:52:47 +0100, Martin Simmons said:
> 
>>>>> On Thu, 4 Sep 2025 09:32:15 -0400, Gary Dale said:
> > 
> > The files are all in /etc/bacula.
> > 
> > It seems to me that if you shouldn't use localhost / 127.0.0.1 in a 
> > configuration file, the default configuration files shouldn't use it. 
> > Instead they should use a descriptive meta-value such as <network name 
> > of the storage device> or <network name of the changer>. This would 
> > prevent the services from starting until the values are replaced with 
> > something legitimate. They would also remove the need for multiple 
> > comments (most of which are NOT currently in the files) about what the 
> > value should not be.
> 
> How did you install Bacula?  It doesn't use localhost when compiling from
> source, but possibly some packager wanted to make it work out of the box on a
> single machine so configured it to use localhost.

Sorry, I see now that it was Debian.

Looking at their bacula-common package, I see that it:

1) Uses localhost for everything in bacula-dir.conf.

2) Use DirAddress = 127.0.0.1, SDAddress = 127.0.0.1 and FDAddress = 127.0.0.1
in the corresponding conf files, so each daemon only listens on 127.0.0.1.

That is a "safe" default config for someone to play with on a workstation
because it prevents connections from outside, but it won't work on a network
server.  You can just remove the DirAddress, SDAddress and FDAddress
directives if your local network is safe.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367105

__Martin