Not translating outbound port 25 communication

[sebna]

Hi All,

I am looking to block LAN to WAN translation of communication through port 25 other then for a one specific local IP.

Any help welcomed with rules creation - I assume two rules.

Thanks

[phil.davis]

You just need to block the traffic - the fact that it would have had NATranslation aplied to it, had it been passed, is a moot point. So you don't need to change any NAT rule/s.

I use aliases for everything, and never put a magic IP address number directly in a rule. So, make an Alias for the IP address that is allowed to go out through WAN to port 25 on the public internet - let's say it is called MailServer.

You could do the block in 1 rule with a "not" (!) rule:
Block source ! MailServer destination any port 25
and then this assumes that there is some more general pass rule later that will let the MailServer-sourced traffic through with "everything else".

But often it is clearer to explicitly allow what you want to allow, then block the rest, using 2 rules:
Pass source MailServer destination any port 25
Block source any destination any port 25

[johnpoz]

No a fan of aliases for everything.  For one is mailserver going to be dhcp, I think not - so why not put in the IP address to make sure you don't run into issues with name resolution since this IP is not going to be changing very often..  Makes the rule table easier to understand because its clear cut address X has access out.

Now aliases make sense if you need to put in something that needs to be resolved, or you have a list of things you want to add..  But when rule is so straight forward, allow IP X out, why not just use the IP vs the extra steps of alias?

[phil.davis]

Yeh, the alias for a single static IP is just personal preference - do whatever you can understand and maintain the easiest in that regard.

[sebna]

Hi Guys,

Thank you for your help. I followed the advice and created set of two rules on LAN side of FW to block all 25 port traffic other then my mail server.

I also use aliases for everything. That saves time when you change IP of the particular service and do not have to track all rules for changes but just adjust alias IP.

Cheers