Hi All, Have you encountered this scenario?I am using a FortiOS 5.4.3,
FG300D, an Allow any internal user OUT, Natted to the firewall interface
IP.There is also an inbound rule for a specific user/device using a VIP
that is not the interface IP. When...
Hi Emnoc. 166 is just used for the inbound VIP, no IP Pool, no outbound
rules for it. A colleague indeed confirmed that this has been resolved
by removing the one-to-one VIP on a previous issue.
Hi Guys, Sorry I can't get a hold of the customer to simulate the
traffic for packet capture. I have attached here the screen capture
instead of the timedout traffic being SNATTED to a public IP 166.*.*.*
eventhough the policy says use the interface ...
Hi All, The inbound DNAT-VIP is working fine but its just weird that the
outbound traffic for that specific internal server is natted to the
public IP used on that VIP. Even though the outbound policy says use the
interface IP. i'll post the debug af...
Hi Emnoc, Yup I've done that and the firewall is just dropping the
packet saying status "timedout"it's just wierd that the the outbound
rule is source natted to a VIP ip address even though the firewall
policy is saying use the interface IP. That VIP...
