Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inbound route #18

Open
kevin-dfo opened this issue Aug 9, 2019 · 0 comments
Open

Inbound route #18

kevin-dfo opened this issue Aug 9, 2019 · 0 comments

Comments

@kevin-dfo
Copy link

I think I'm running into an async routing with inbound connections.

I have a public ip with a front end ip config on the public load balancer.
On the fortigates I have a virtual IP external IP is the pip, mapped IP is the ip of the vm. Port forward enabled 80:80
IPv4 Policy, From any To any, source all, destination virtual IP, action accept, NAT Disabled.
I have a simple vm with nginx installed.

Route table 0.0.0.0/0 > internal load balancer.

Hit the public ip from a bunch a locations and some will succeed and some will timeout.
Enable NAT on the policy solves the issue but then the nginx logs show the fortigate ip which is not ideal. Am I missing a setting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant