Re: [Bacula-users] Remote Client Security Alerts

2024-09-27 Thread Chris Wilkinson
I set up firewalld on the client. This was a learning curve but has done the trick. It depends on the Dir server having a static ip since it's not possible to set a source address as a FQDN in firewalld. I didn't find a way round that in case the server has a DHCP address. Fortunately my ISP does p

Re: [Bacula-users] Remote Client Security Alerts

2024-09-27 Thread Josip Deanovic via Bacula-users
On 2024-09-17 13:57, Dragan Milivojević wrote: AFAIK there is no such feature on the FD side but I might be wrong. If the option "--with-tcp-wrappers" is used for building Bacula daemons, Bacula daemons would make use of libwrap library. I recommend using local firewall rather than tcp wrapper

Re: [Bacula-users] Remote Client Security Alerts

2024-09-17 Thread Martin Simmons
They are being sent to the Director by the client (nuc2). I suggest adding some firewall rules on nuc2 to only allow connections to port 9102 from the Director. __Martin > On Tue, 17 Sep 2024 11:41:14 +0100, Chris Wilkinson said: > > I keep getting security alerts from a remote client back

Re: [Bacula-users] Remote Client Security Alerts

2024-09-17 Thread Bill Arlofski via Bacula-users
On 9/17/24 4:41 AM, Chris Wilkinson wrote: I keep getting security alerts from a remote client backup. The backups always run to success. The IPs that are listed in the job log are different every time and in various locations including some in Russia but also in London and European data centres

Re: [Bacula-users] Remote Client Security Alerts

2024-09-17 Thread Dragan Milivojević
AFAIK there is no such feature on the FD side but I might be wrong. On Tue, 17 Sept 2024 at 13:52, Chris Wilkinson wrote: > > Is that something that can be done in the FD or is it a job for iptables? > > -Chris Wilkinson > > On Tue, 17 Sep 2024, 12:48 Dragan Milivojević, wrote: >> >> These are j