Thanks for the replies... seems like there are a bunch of outdated technotes out there.
What I have done so far (and initial tests shows that the packets (so far) is sent in right direction(s) :P) is to create a vserver (type:forwarding ip) with net/mask 0.0.0.0/0 acting on any protocol and create a custom fastL4 profile that has reset on timeout disabled along with loose open (and close) enabled.
Then did the same as above but acting on udp as protocol and a custom fastL4 profile for that also similar to above with the addition of state timeout set to 5 seconds instead of default 300.
So now I have two vservers:
VS_ROUTE
VS_ROUTE_UDP
Ohh and finally setup the static (or whatever) routes one need in the network part...
And thats it? :-)
Looking at the different types one can setup your vserver to I found "stateless" in v11.1 which isnt mentioned in the help-pages.
How does "stateless" differ from "forwarding ip" for what I want to do (at a first glanze one could think that stateless is a more optimized version of forwarding ip since I want the F5 to route the packets and not touch them at all (except for packets directed to other vservers))?