Forum Discussion
Disable Inter-VLAN Routing?
- Jun 07, 2023
レザ As long as the servers sit in a different VLAN it would be up to your routing to not allow them to reach each other. Example, if you have VLANs 1-5 and the F5 and the firewall sit in each VLAN with the F5 being in 1 arm mode then each server should have the firewall as their gateway. As long as the switch seperating each VLAN doesn't performing any routing then those servers should not be able to reach each other without going through the firewall. They could technically reference the F5 as their gateway but if the F5 doesn't not have a forwarding virtual server configured with SNAT enabled on that virtual server they will not be able to communicate with each other without using the firewall.
What do you mean by routing between Vlans on Bigip ?
Also clarify your words regards bigip bypass Firewall ?
Each of my servers are inside their own vlan and the gateway of all these servers is the firewall, and any communication between these servers should only be through this firewall. since the load balancer has one arm inside each vlan, is it possible that the servers of different vlan communicate with each other without passing through the firewall?
Do you mean servers' vlans separated but can reach other through Bigip ?
YESSSSSSSSSSSSSSSS 🙂
Thanks
レザ As long as the servers sit in a different VLAN it would be up to your routing to not allow them to reach each other. Example, if you have VLANs 1-5 and the F5 and the firewall sit in each VLAN with the F5 being in 1 arm mode then each server should have the firewall as their gateway. As long as the switch seperating each VLAN doesn't performing any routing then those servers should not be able to reach each other without going through the firewall. They could technically reference the F5 as their gateway but if the F5 doesn't not have a forwarding virtual server configured with SNAT enabled on that virtual server they will not be able to communicate with each other without using the firewall.
- wtwiggsJun 11, 2023Altocumulus
just to add to Paullus correct answer, another option to consider dependng on your security or other architectural requirements, is to use "route domains" to partition your F5 system such that the VLANs behind the firewall are in separate F5 route domains, with no parent-child relationship and strict isolation enabled... in this case, there is no way the F5 could forward any packets between the VLANs even if a virtual server (such as a "forwarding" virtual server) were created, since there is full isolation between the VLANs due to the separate (and isolated) route domains. more info here:
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