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

David_Gill's avatar
David_Gill
Icon for Cirrus rankCirrus
Jul 08, 2021

iRule access to route table

I have two types of users connecting to the same Big-IP APM using the F5 Access VPN client. Both users reach internal servers via the route table which is populated via BGP. So far, so good. The chal...
BIG-IP Access Policy Manager (APM)
devops
JRahm's avatar
JRahm
Icon for Admin rankAdmin
Jul 08, 2021

If your nexthops are distinguishable and consistent, the safest path forward would be to use LINK::nexthop for this (and in conjunction with LINK::vlan_id if necessary)

 

If you really want to pull the routing table in, you could write an iCall script to periodically read the routing table and set iStats variables then use an ISTATS::get call to pull the right information based on your key. But if I'm understanding your ask correctly, I think the LINK::nexthop approach is the best bet.