Re: SMTP notification E-Mail LoadBalancing problem
-
Hi,
I noticed a problem with sending E-Mail notifications with LoadBalancing. I have two DSL lines WAN1 and WAN2 in LoadBalancing - both Tier1.
If my WAN1 goes down, the system tries to send an E-Mail notification but without success. If my WAN2 goes down then the system i able to send the E-Mail notification.
A attached you the system logs. For me it looks like as if the time between changing routing groups and sending the E-Mail should be a litte bit increased.
The GROWL messages over the LAN interface - which was always up, is working fine.
May 25 22:16:10 check_reload_status: reloading filter May 25 22:16:00 apinger: alarm canceled: WAN1(8.8.8.8) *** down *** May 25 22:15:15 php: : MONITOR: WAN1 is down, removing from routing group May 25 22:15:15 php: : MONITOR: WAN1 is down, removing from routing group May 25 22:15:15 php: : Could not send the message to E-MAIL-ADDRESS -- Error: could not connect to the host "smtp.web.de": ?? May 25 22:14:14 php: : MONITOR: WAN1 is down, removing from routing group May 25 22:14:13 check_reload_status: reloading filter May 25 22:14:03 apinger: ALARM: WAN1(8.8.8.8) *** down *** May 25 22:12:09 check_reload_status: reloading filter May 25 22:11:59 apinger: alarm canceled: WAN2(8.8.4.4) *** down *** May 25 22:10:29 php: : MONITOR: WAN2 is down, removing from routing group May 25 22:10:29 php: : MONITOR: WAN2 is down, removing from routing group May 25 22:10:29 php: : Message sent to E-MAIL-ADDRESS OK May 25 22:10:28 php: : MONITOR: WAN2 is down, removing from routing group May 25 22:10:28 check_reload_status: reloading filter May 25 22:10:18 apinger: ALARM: WAN2(8.8.4.4) *** down *** May 25 22:08:12 check_reload_status: reloading filter May 25 22:08:02 apinger: alarm canceled: WAN1(8.8.8.8) *** down *** May 25 22:06:25 php: : MONITOR: WAN1 is down, removing from routing group May 25 22:06:25 php: : MONITOR: WAN1 is down, removing from routing group May 25 22:06:25 php: : Could not send the message to E-MAIL-ADDRESS -- Error: could not connect to the host "smtp.web.de": ?? May 25 22:06:13 php: : MONITOR: WAN1 is down, removing from routing group May 25 22:06:12 check_reload_status: reloading filter May 25 22:06:02 apinger: ALARM: WAN1(8.8.8.8) *** down *** May 25 22:05:13 check_reload_status: reloading filter May 25 22:05:03 apinger: alarm canceled: WAN2(8.8.4.4) *** down *** May 25 22:03:29 php: : MONITOR: WAN2 is down, removing from routing group May 25 22:03:29 php: : MONITOR: WAN2 is down, removing from routing group May 25 22:03:29 php: : MONITOR: WAN2 is down, removing from routing group May 25 22:03:28 check_reload_status: reloading filter May 25 22:03:18 apinger: ALARM: WAN2(8.8.4.4) *** down *** May 25 21:38:01 check_reload_status: reloading filter May 25 21:37:51 apinger: alarm canceled: WAN2(8.8.4.4) *** down *** May 25 21:35:43 php: : MONITOR: WAN2 is down, removing from routing group May 25 21:35:43 php: : MONITOR: WAN2 is down, removing from routing group May 25 21:35:43 php: : Message sent to E-MAIL-ADDRESS OK May 25 21:35:43 php: : MONITOR: WAN2 is down, removing from routing group May 25 21:35:42 check_reload_status: reloading filter May 25 21:35:32 apinger: ALARM: WAN2(8.8.4.4) *** down ***
-
Or use a floating rule + outbound NAT to send that traffic into your failover group so it just goes out the other WAN.
-
Please give me an advice. How should this Floating rule look like ?
which interface should I select? WAN1, WAN2 ? Source my pfsense ? -
I moved this into its own thread because it wasn't really related to the other problem.
outbound NAT would look like:
[all your other outbound NAT rules]
WAN1 any * * 25 * * NO
WAN2 any * * 25 * * NOfloating rule would be:
Pass, interfaces: WAN1 WAN2, quick, out, tcp, destination port 25, gateway FailoverGroupName -
Okay and what should I have to add, if I do not use MANUAL outbound NAT at the moment ?
For me it isn't clear at all when to use manual and when automatic outbound NAT rules. I always used automatic in the past. :(
-
You have to use manual.
It will fill in automatically with an equivalent set of rules to the automatic ones.