Forum Discussion

TD_388740's avatar
TD_388740
Icon for Nimbostratus rankNimbostratus
Apr 30, 2019

VPN SSL traffic not being forwarded when using a not directly attached network as VPN Pool

Hi, I have a F5 setup in AWS to use for Client VPN. I had it working fine but then found out that the ACLs are not being applied because I bypass the VS which is used for the VPN Clients.   Here i...
AWS
BIG-IP Access Policy Manager (APM)
devops
TD's avatar
TD
Icon for Nimbostratus rankNimbostratus
May 06, 2019

Hi rafaelbn, here is some more info.

 

VPN Pool subnet: 10.2.0.0/24 Public subnet in VPC: 10.237.243.0/26 Private subnet in VPC: 10.237.240.0/24 Private interface F5 selfIP: 10.237.240.209 Public Interface F5 VS: 10.237.243.12 Fortigate FW: 10.237.240.130

 

  1. 0.0.0.0/0 --> 10.237.240.130 (fortigate firewall for scanning internet traffic)
  2. 10.0.0.0/8 --> 10.237.240.1 (def. gw for private subnet in VPC)

I also tried only a default route and leaving out the fortigate but that didn't help. The fortigate is also only for scanning the internet facing traffic (webscanning).

 

I also have a route in the routing tables of the VPC that is pointing to the private interface of the F5 for the VPN Pool network (the selfIP interface of the F5).

 

On the fortigate there are three routes 0.0.0.0/0 --> 10.237.243.1 10.2.0.0/24 --> 10.237.240.209 10.0.0.0/8 --> 10.237.240.1 (for mm access)

 

Here are pictures of the forwarding VS I had configured and with which routing works. I had the same configured for UDP.

 

 

Related Content