I just recently set this firewall up and have been watching the amount
of traffic going in and out. I have a lab with 2 hyper-v servers and
about 30 VMs. (not all running at the same time). Over the last few days
a large amount of traffic has gone ou...
Hey Guys, I just setup this Fortigate 60C. I upgraded the os to 5.2. I
created a VIP and then created a policy. This is for Port 25 and is
being used to simply forward port 25 traffic to my mail filter. I
noticed in my message tracking logs that Exte...
Ok I got this figured out. it was as you had originally suggested, I had
NAT enabled in the policy. Previously most firewalls I worked with
either did NAT or Route and no other way. If you disabled NAT it was
"System Wide" not like the fortigate whic...
Guys Any help here? I discovered today that my mail relay has been being
used as an open relay because the IP address 192.168.1.225 FG firewall
is listed as an internal IP (due to it being internal). This caused my
relay to think all inbound emails w...
This is what I found for changing flow mode:
http://help.fortinet.com/fos50hlp/54/Content/FortiOS/fortigate-whats-new-54/Top_ProxyFlowPerVDOM.htm
I am running OS 5.2 though so I am not sure if my 60C supports those
same options.
I do have NAT Enabled but that shouldn't cause the Source IP address to
change from an External IP to the Firewall's IP. That sounds like
proxying to me.
Any suggestions here? the email in the screenshot is from office 365,
the message was sent from EOP to my environment, the source IP address
should have been a publicly routable address and the 192.168.1.225 which
is the internal IP of the firewall.
