Mail servers imap behind pfsense not reachable

Bob.Dig

@johnpoz said in [Mail servers imap behind pfsense not

edit: To be honest that is almost worse than local nat reflection. Since not only do you have the hairpin on pfsense. But you also have to deal with all the added latency and hairpin on their system ;)

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 18ms, Average = 15ms
PS C:\WINDOWS\system32>

It is ok for some messages I guess.

Suricata things I got attacked..

SERVER-OTHER MRLG fastping echo reply memory corruption attempt

Then this mystery is solved and I will not mention it anymore, because I am special.

johnpoz

Yeah for small amounts of traffic its not all that big of deal, but it sure isn't "optimal"

Be like walking to the front door in your house from your bedroom when you want to go kitchen.. vs just going to the kitchen.

But lets take for example your plex server sitting right next to your client.. Streaming some movie at XMbps..

Your plex server hands out 2 IPs with plex.tv - it lists your public IP, so that remote clients can talk to your plex server when they are out and about on the internet.

But when your client is local, it uses your local rfc1918 address. Which you have to make sure resolves by turning off rebind protection.. If not you would have to nat reflect to get to your own plex server

What is better when you say streaming a 20Mbps movie, or lets say multiple streams of that when your watching something, your kids watching something else, and the wife is watching her show on her ipad, etc..

In your scenario, not only would you be running traffic through pfsense that doesn't need to, you would also be limited by your internet connection speed.