Forum Discussion

sebasd_377069's avatar
sebasd_377069
Icon for Nimbostratus rankNimbostratus
Mar 28, 2019

vs wilcard performance l4 problem intervlan routing

Hi there,

i hope you are doing well, i'm checking that has a virtual server wildcard a performance l4 and has a pool, and has one pool address that is the gw from the upstream vlan is the external vlan in this example is the 1.1.1.0

so in here is marking like a tcp, so when a i make a ping from the vlan internal in this example 2.2.2.0 host to another host in the network 1.1.1.0 the ping is working and in the virtual address there is no ticket icmp but in the spanning ticket is marked, but in any case if put TCP and not ICMP ping should't work

so from my point of view i'm thinking that the is sending all the traffic that the vs_wildcard matching to the upstream firewall that has the same ip address that thas in the pool firewall

application delivery
BIG-IP
LTM

1 Reply

Sort By
  • sebasd_377069's avatar
    sebasd_377069
    Icon for Nimbostratus rankNimbostratus
    Mar 28, 2019

    so the intervlan routing is doing the fw? why doing this way? what about recommendation that f5 does:

     

    https://support.f5.com/csp/article/K7595

     

    which method is prefer? because what i want is to make it that f5 has all the invervlan routing and in the fw i see some traffic and when i captured traffic i see that in the ethernet header f5 mac src to dst mac firewall

     

    ltm virtual /Common/vs_wildcard { destination /Common/1.1.1.0:0 ip-protocol tcp mask 255.255.255.0 pool /Common/firewall profiles { /Common/fastL4 { } } source 2.2.2.0/24 source-address-translation { type automap } translate-address disabled translate-port disabled vlans { /Common/link_Trunk_Vlan2 } vlans-enabled