Forum Discussion
Creating VS for a network not directly connected
Hi,
I have a network that has a DMZ (10.1.1.0/24) and an Internal (10.2.2.0/24) network directly connected to the F5 LTM. The Internal network also has access to other networks (172.16.0.0/24) across a VPN tunnel. I need to create a Virtual Server on the DMZ that allows traffic to specific servers that are on 172.16.0.0/24 network.
I may have my information wrong, but if I just create a Forwarding(IP) Virtual Server for 172.16.0.0/24:* on all ports and assign it to the DMZ vlan, will it listen for incoming traffic on the DMZ interface for the 172 network? I think I read that if the F5 doesn't have a Self IP for that network, it won't ARP that network. Coming back I have a default Forwarding (IP) Virtual Server allowing access from Internal to DMZ (0.0.0.0/0:*). I also have routes in the F5 that point 172.16.0.0/24 traffic to the Internal network.
Either way I'm having issues with traffic going from the DMZ across the tunnel. Any help is appreciated.
Thanks,
Mike
- nitassEmployeeyou have added a route for 172.16.0.0/24 subnet on firewall to send traffic to bigip's dmz interface, haven't you?
- Thomas_Schocka1AltocumulusHi Mike,
- Mike_61640NimbostratusI went through and checked everything listed in your comments and they all seem to be in order. I have static routes for these networks and a Forwarding (IP) setup for the 172.16.0.0/24. I guess I just wanted to make sure that it would grab allow/grab this traffic if these networks were not directly connected. I know that standard VS's don't and wanted to confirm that the Forwarding (IP) VS didn't act the same way.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com