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

afedden_1985's avatar
afedden_1985
Icon for Cirrus rankCirrus
Mar 25, 2015

Interesting question and more details are needed about the servers side of the VIPs. You can have IPv4 VIPs load balance to IPV6 servers or IPV4 VIPs load balance to IPV6 servers it doesn't matter what combination you use. Your question about a VIP targeting a VIP is possible but more complicated than just sending from the VIP to the servers.

 

  • Craig_Baker_187's avatar
    Craig_Baker_187
    Icon for Altocumulus rankAltocumulus
    Mar 25, 2015
    Behind the IPv6 VIPs there will be a pool of IPv6-only servers running docker containers on high end ports. so for example we may have APP_1 running on servers s1, s2 and s3 port 6000. These 3 address:port pairings would make up the pool. A IPv6 DNS entry (app1.domain.com) would point to an IPv6 VIP for APP_1. The VIP would load balance between the servers s1:6000, s2:6000, and s3:6000. APP_2 may be running on s2, s3 and s5:6001, and would also have its own IPv6 VIP and DNS entry. Both APP_1 and APP_2 would also have an IPv4 DNS entry. All IPv4 DNS entries would go to a 3rd VIP that would NAT the IPv4 request into an IPv6 request, and then do the DNS lookup and route accordingly. We would hope in the future to be able to turn off the IPv4 VIP once we stop getting IPv4 requests. Also if a request comes in using IPv6 it should be routed directly to the APP's IPv6 VIP by usingt the IPv6 DNS entry. Is that any more helpful? What else do you need to know aobut the servers side of the VIPs?