Zitat von David Pearce <[email protected]>:
We did some rearranging of our firewall and found an interesting issue. Our Bareos storage server is named "G". It reaches out to a client "C" and starts a backup. Then for reasons I don't understand, "C" opens a new connection and communicates with "G". Since "C" is in our DMZ, it can't make a connection unless we allow it so it fails until we add a rule allowing it.Why would "C" need to open a new connection to "G"? Thanks!
This is the standard behaviour of the client, it opens a connection to the SD :
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-180001.10You can use the passive client feature which is intended for the use case you describe
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-33300026.1 Regards Andreas -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
