Forum Discussion

sergio_baza_alo's avatar
sergio_baza_alo
Icon for Altocumulus rankAltocumulus
Dec 01, 2017
Solved

Routing in a standard virtual server

Hello all,

 

I want to use a virtual server with a TCP profile attached and without pool members.

 

In the network I’m going to set this virtual server as default gateway and this vs should route traffic to internet.

 

If the standard virtual server has no pool members and receive traffic, what is going to do with the traffic?? I would like to know if this traffic is going to be forwarded.

 

Other thing that I’ve thought is use an iRule to forward traffic to default gateway.

 

Also I’ve look the option of the forwarding ip virtual server, but I need the TCP profile and I don’t know if the virtual server behaves like an standard virtual server with a TCP profile.

 

What I finally need to achieve is create a default gateway that closes the connection and start a new one with the internet server that’s why I think the TCP profile is needed.

 

Thanks in advantage

 

  • Two options that I know of.

     

    Do exactly what you said you didn't want to do, create a node that is the IP address of your next hop, toss that into a pool, assign this single noded pool to your VS. Assign a ping monitor on it if you want to verify it is up. Otherwise assign no monitors to it.

     

    Option 2, do not assign a pool to the VS and instead use an iRule to forward traffic to the next hop IP address: https://devcentral.f5.com/wiki/iRules.nexthop.ashx I usually do this option with a forwarding server instead of a standard server because I did not want a full proxy for this traffic.

     

4 Replies

  • You can create such virtual server by disabling translate address option.

     

    When you set the virtual server destination with network mask, this option is disabled.

     

  • Two options that I know of.

     

    Do exactly what you said you didn't want to do, create a node that is the IP address of your next hop, toss that into a pool, assign this single noded pool to your VS. Assign a ping monitor on it if you want to verify it is up. Otherwise assign no monitors to it.

     

    Option 2, do not assign a pool to the VS and instead use an iRule to forward traffic to the next hop IP address: https://devcentral.f5.com/wiki/iRules.nexthop.ashx I usually do this option with a forwarding server instead of a standard server because I did not want a full proxy for this traffic.