On 30 Jan 2018 7:00 p.m., "Bill Shirley" <b...@knoxvillechristian.org> wrote:
On 1/30/2018 9:15 AM, Karol Augustin wrote: >From the information you provided it looks like problem is not fixable by you. It's ok to have private address configured on your server if it is properly translated upstream. Amazon does that. You have private IP configured on your machine but it is translated to the same public address for both incoming and outgoing connections. Talk to your ISP about this. Karol -- Karol Augustin ka...@augustin.pl http://karolaugustin.pl/ +353 85 775 5312 <+353%2085%20775%205312> In an earlier post: Becouse I prefer to use fail2ban for brute force attacks and fail2ban depends source IP address.In this setup I can't see source IP. Also I'll use iptables as a permanent filter for some IPv4 blocks (like china). He needs to see the real public addresses of those who connect to this new server. You said this machine has address 192.168.34.30/24. Who gave it this address? Bill ISP has a OS deployment team. They prepare this machine for us. I do not have much choice becouse our company outsourced some jobs (like os installations and network definitions) and this is the one of them. You wrote specs and they prepare for you.
