Forum Discussion

TMcGov_92811's avatar
TMcGov_92811
Icon for Nimbostratus rankNimbostratus
May 21, 2008

LTM IP Forwarding Virtual Server behaviour issues

Hello,

 

 

I have setup my bip3400 with a wilcard IP Forwarding Virtual Server to allow full routing through the BigIP.

 

 

virtual IP-Forwarding-VS {

 

disable

 

ip forward

 

destination any:any

 

mask none

 

}

 

VLAN231

 

|

 

|

 

MY VLAN <---> FW <---> VLAN230 <----> BIGIP

 

|

 

|

 

VLAN232

 

 

 

1. With the IP Forwarding Virtual Server enabled, from my desktop in "MY VLAN" I am able to ping servers on VLANs 231 and 232 through the BigIP. The BigIP is their default gateway. However servers on VLAN231 cannot ping through the BigIP to VLAN232 nor vice versa. These are directly connected interfaces so of course they are in the routing table. Why is this connectivity not allowed by the IP Forwarding Virtual Server.

 

 

Kernel IP routing table

 

Destination Gateway Genmask Flags Metric Ref Use Iface

 

127.1.1.0 * 255.255.255.0 U 0 0 0 tmm0

 

10.77.232.0 * 255.255.255.0 U 0 0 0 QA-App-Int-232

 

172.20.1.0 * 255.255.255.0 U 0 0 0 eth0

 

127.2.0.0 * 255.255.255.0 U 0 0 0 eth0

 

10.77.230.0 * 255.255.255.0 U 0 0 0 QA-App-Ext-230

 

10.77.231.0 * 255.255.255.0 U 0 0 0 QA-App-Int-231

 

127.0.0.0 - 255.0.0.0 ! 0 - 0 -

 

default 10.77.230.1 0.0.0.0 UG 0 0 0 QA-App-Ext-230

 

default 172.20.1.1 0.0.0.0 UG 1 0 0 eth0

 

 

 

2. From my desktop in the "MY VLAN" I am able to ping servers on VLANs 231 and 232 through the BigIP. I noticed that if I disable the IP Forwarding Virtual Server, traffic will continue to flow unless I reboot the BigIP. Only after a reboot is the traffic blocked. Is this normal behavior ?

 

 

  • 1. Did you ensure that the Servers on VLAN 231 and 232 segments are pointing at the BIGIP as thier gw?

     

    2. This is a behavior i have noticed in the past, I never investigated it but I don't think it should be normal behaviour.

     

     

     

    CB