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

Grayson_149410's avatar
Grayson_149410
Icon for Nimbostratus rankNimbostratus
Aug 10, 2016

IP Forwarding DST Won't Accept Networks Only Hosts

We are currently building out a new network where we want to route with the LTMs. Each server has its default gateway set to the floating ip address of that network on the LTM.

 

When I create the below wildcard like Forwarding IP Virtual Server, I am able to RDP into the box just fine. However, when I change the destination to 172.19.96.0/22, everything breaks. Why do I have to be so specific? Everything work fine when trying to get to a real applications VS, but we need people to be able to connect directly to the web servers themselves to promote code/RDP into. We don't want to have to create a Forwarding VS for EVERY single server in the network. It would be a major nightmare.

 

ltm virtual /Common/test {
destination /Common/172.19.96.200:0
ip-forward
mask 255.255.255.255
profiles {
    /Common/fastL4 { }
}
source 0.0.0.0/0
translate-address disabled
translate-port disabled
vlans {
    /Common/Non-Prod_Web
}
vlans-enabled

}

 

3 Replies

  • The /22 forwarding VS should work fine. I have several of these with varying masks. Do the VS statistics show that the /22 VS is receiving traffic? You might have another VS taking precedence. See this article about traffic processing precedence SOL9038.

     

  • Just wanted to bump this to see if anyone has ever seen an issue with this or some checkbox I might be missing.

     

  • Try below virtual server config..

    ltm virtual /Common/test {
    destination /Common/172.19.96.0:0
    ip-forward
    mask 255.255.252.0
    profiles {
        /Common/fastL4 { }
    }
    source 0.0.0.0/0
    translate-address disabled
    translate-port disabled
    vlans {
        /Common/Non-Prod_Web
    }
    vlans-enabled
    }