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

engtmk's avatar
engtmk
Icon for Nimbostratus rankNimbostratus
Nov 11, 2007

Big IP as default Gateway

I have server that is confgiured with the big ip as its default gateway     but these server cant reach any network outside its networks     so do we have to create routes on the LTM or s...
config
design
engtmk's avatar
engtmk
Icon for Nimbostratus rankNimbostratus
Nov 12, 2007
in the last post I discovered i was trying to access from non-direct connected vlan that's why ( I added route to that vlan ) now it's working

but i still has the same problem whenever I try to connect to one of the direct-connected vlan

and that what I got when I try to telnet from 192.168.110.1 (server with Bigip as its default GW)

to 192.168.3.102 (direct-connect vlan server)


22:29:57.131377 802.1Q vlan4094 P0 192.168.110.1.4422
 > 192.168.3.102.ftp: S 1469314934:1469314934(0) win 65535  (DF)
22:29:57.131396 802.1Q vlan4093 P0 192.168.110.1.4422
 > 192.168.3.102.ftp: S 1469314934:1469314934(0) win 65535  (DF)
22:29:59.992555 802.1Q vlan4094 P0 192.168.110.1.4422
 > 192.168.3.102.ftp: S 1469314934:1469314934(0) win 65535  (DF)
22:29:59.992561 802.1Q vlan4093 P0 192.168.110.1.4422
 > 192.168.3.102.ftp: S 1469314934:1469314934(0) win 65535  (DF)
22:30:06.007492 802.1Q vlan4094 P0 192.168.110.1.4422 
> 192.168.3.102.ftp: S 1469314934:1469314934(0) win 65535  (DF)
22:30:06.007499 802.1Q vlan4093 P0 192.168.110.1.4422 
> 192.168.3.102.ftp: S 1469314934:1469314934(0) win 65535  (DF)