For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Michael_57131's avatar
Michael_57131
Icon for Nimbostratus rankNimbostratus
May 03, 2013

Asymmetric routing condition with two "external" networks

(Hopefully the attached PNG file shows, the red line is how the traffic is routed now, you can see the asymmetry, and the green line is how I'd like to force all traffic between these nodes)   We ...
config
design
What_Lies_Bene1's avatar
What_Lies_Bene1
Icon for Cirrostratus rankCirrostratus
May 07, 2013
There are is a flaw in that plan, namely that a forwarding VS will rely on the routing table and any static route you configure will be installed with a higher metric that the route that's created by the connected interface.

The default gateway can't be directly modified as such and certainly not on a per connection basis, however, this iRule (applied to a L3 or above VS) should work I think as long as NodeB also routes back via the firewall; 


when CLIENT_ACCEPTED {
 if { [IP::addr [IP::local_addr] equals 10.101.104.0/24] } {
   nexthop vlan_name 10.101.224.220
}
}