Forum Discussion
For anyone who happens to read this I found that if I changed the destination to anything other than a wildcard 0.0.0.0 the routing works. In the example above I changed the destination to be 192.168.1.0/24 on my outbound forwarding ip server and the routing works.
It seems my version of F5 does not work with a wildcard destination of 0.0.0.0
- Kevin_Davies_40Apr 18, 2017
Nacreous
A wildcard is not a valid IP address for the destination.
- Neil8319Apr 18, 2017
Nimbostratus
I thought it was possible to have a completely open ip forwarding virtual server listening on the internal vlan as many of the articles on this site seem to suggest. ie source 0.0.0.0/0 and destination 0.0.0.0/0.
it's obviously not the case. In anycase my issue is resolved.
- Kevin_Davies_40Apr 18, 2017
Nacreous
I mistook your word wildcard to mean *. You are using 0.0.0.0 and that's fine. Their must be something else causing you a problem. I am glad to hear it is resolved.