Re: [Shorewall-users] Shorewall 5.1.6

2017-08-24 Thread Norman Henderson
Thanks but... too risky! Eventually I found a post advising to delete the package entries from /var/lib/dpkg/status, all of the lines from "Package: shorewall" down to just before the next "Package:" line. And also shorewall-core and shorewall-init (and for some people there might be others). So A

Re: [Shorewall-users] Enabling Postfix MX backup server and port issues

2017-08-24 Thread Tom Eastep
On 08/24/2017 11:48 AM, Tom Eastep wrote: > > As far as I am aware, neither UDP port 1370 nor TCP port 1328 have > anything to do with Postfix. Port 1370 is us-gv (Unix Shell to > GlobalView) while 1328 is echoserver (and also used by malware). I > suggest that you use netstat to try to determine

Re: [Shorewall-users] Enabling Postfix MX backup server and port issues

2017-08-24 Thread Bill Shirley
Port 3128 is squid. You're being probed for open ports. I don't see anything in those messages related to mail. Bill On 8/24/2017 2:48 PM, Tom Eastep wrote: On 08/24/2017 10:04 AM, Davide Marchi wrote: Hi friends, I'm enabling Postfix MX backup server and from that moment I see "mydestinatio

Re: [Shorewall-users] Enabling Postfix MX backup server and port issues

2017-08-24 Thread Tom Eastep
On 08/24/2017 10:04 AM, Davide Marchi wrote: > Hi friends, > I'm enabling Postfix MX backup server and from that moment I see > "mydestination" and "relay_domains" ip DROP(ped) > > "mydestination" is:91.205.175.213 (SERVER1) > "relay_domains" is:5.189.166.16 (SERVER2) > > > As here you can see:

[Shorewall-users] Enabling Postfix MX backup server and port issues

2017-08-24 Thread Davide Marchi
Hi friends, I'm enabling Postfix MX backup server and from that moment I see "mydestination" and "relay_domains" ip DROP(ped) "mydestination" is:91.205.175.213 (SERVER1) "relay_domains" is:5.189.166.16 (SERVER2) As here you can see: SERVER1: Aug 24 18:13:22 server kernel: [17818755.169878]

Re: [Shorewall-users] MySQL Replication with ssl connection and ports configuration

2017-08-24 Thread Davide Marchi
[..] Hi Davide, Diagnosing something like this typically requires the complete output of 'shorewall dump'. However, based on the syslog messages it looks like you simply need to add the 'routeback' option to the eth0 line in /etc/shorewall/interfaces on both hosts. If that does not resolve

Re: [Shorewall-users] Shorewall 5.1.6

2017-08-24 Thread Vieri Di Paola via Shorewall-users
From: Norman Henderson > > I have a couple of remotely located systems with the Ubuntu-packaged > shorewall 5.0.4 and would like to > move to building the current release 5.1.6 instead. On Gentoo, you can use slotted packages. I don't know about Ubuntu - I d