Forum Discussion
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
- Grayson_149410
Nimbostratus
Just wanted to bump this to see if anyone has ever seen an issue with this or some checkbox I might be missing.
- Jinshu
Cirrus
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 }
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com