Providing Internet Access to a "remote" Real server

Is the BIG-IP being relied upon to route the traffic out? Is this necessary? I ask as the server clearly isn't using the BIG-IP as it's default gateway.

real server, do i see a Cisco ACE term there :)

if you are talking about a node which needs to be able to access the internet through the BIG-IP you need to setup a virtual forwarding server on the big-ip which allows access from the server side of the big-ip to the client side (assuming basic setup).

http://support.f5.com/kb/en-us/solutions/public/7000/500/sol7595.html

Did you want your real server to be able to access the internet(outbound)? Is your BigIP and real server on the same subnet? In this case you'll have to set up the BigIP as your default gateway for the real server to get out to the internet via the BigIP, and you'll need a virtual forwarding server on the BigIP.

Or access from the internet to your real server(Inbound)? In this case you'll need a Virtual forwarding server for this

I believe the above is correct if I understand your question.

Leonardo

If it's outbound and you want to use the BigIP you'll have to somehow get the BipIP in the path out to the internet. Otherwise when your real server tries to go out to the internet, using an public IP, it'll just follow its path out to the internet, there isn't anything to tell it to go to the BigIP first. Make sense?

Might be easier to setup a static NAT on your router. Do you have an available publicly routable IP address/NAT pool to use for the external NAT address?