OK. Client is on private address (so its FQDN or name is not visible on internet) and behind firewall and server is on public IP (on registered domain) and on cloud. Permittedpeer on client side will be IP or name of server it is clear. But what will be on server side, IP or name of external address of firewall or what. If external address of firewall then then how it will pass packets to client.
On Thu, Dec 11, 2014 at 10:50 PM, David Lang <[email protected]> wrote: > > you don't need to open an inbound connection. The NAT that allows you to > connect out also allows the responses back in. > > David Lang > > > On Thu, 11 Dec 2014, Muhammad Asif wrote: > > Hi Rsyslog Users >> >> My Rsyslog server is on cloud and rsyslog client in my organization on >> private IP. >> I want my rsyslog client to receive logs from internal devices and send to >> rsyslog server on cloud. My client is behind firewall. I want RELP on TLS >> between client and server. My client can access server but question is on >> what port rsyslog client receive acknowledgment from server so that I >> could >> do destination NAT of my firewall to reach reply from server to client. >> > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
