Forum Discussion
Franky-frank-reg7
Altocumulus
AltocumulusF5 SMTP Fast Template - SNAT Not working as expected
Hello all, I'm having issues with getting SMTP to work with the FAST templates. Specifically, I'm trying to configure an SMTP template with no SNAT option checked so the backend pool members receive...
Franky-frank-reg7 That is true but to simplify the configuration so that you reduce the man hours you might/will spend in the future troubleshoot a non-standard deployment of the F5 you should deploy it as option 1
Paulius
MVP
MVPFranky-frank-reg7 You only need 1 forwarding virtual server that has a source and desination of 0.0.0.0 which will allow the F5 to pass traffic from one interface to the other without really changing anything on it. You do not need 1 forwarding VS per direction if the intent is just to route traffic from external to internal and internal to external for any IP you aren't load balancing on the F5.
Franky-frank-reg7Altocumulus
AltocumulusPerfect, thanks Paulius.
Last question before we test this is -- how do we designate which interface is external?
Currently, all traffic default routes to a GW IP that is available out of one of my self IP interfaces. I would imagine this would be my external interface?
- Paulius
Franky-frank-reg7 External and Internal are just common names that most people use when configuring F5s in path. Your external VLAN/interface would be which ever interface is in the subnet that you point your gateway to for your default route out typically denoted by a 0.0.0.0/0 route.
- Franky-frank-reg7
Thank you, the solution worked. We went with the option 1 inline VS with forwarding IP VIP to cover non-LTM proxied traffic.