Hi, I am working on implementing av proxy-solution with the help of F5 BIG-IP to do SSL-decrypt. In short: Users surf the web, and the traffic hits the F5 internal VLAN over a fiber-trunk(2.1 and 2.2), the next hop for the traffic is a pool containing a proxy-solution(int 1.1). After the traffic has passed the proxy, it returns to the F5 on a different interface(1.2) and is Auto Mapped before being sent to the pool containing the internet facing router. But for some reason it all stops when the proxy tries to send the traffic back to the F5 on Int 1.2. In the tcpdump I can see that the F5 is responding to requests from the proxy with the same self-IP that is defined on the internal VLAN that is assigned to the fiber trunk. And for that reason the connection times out, and the users have no internet access. A tracert from a klient looks like this: 1 <1 ms 156 ms <1 ms 192.168.50.13 - Client2 1 ms 147 ms <1 ms 192.168.50.1 - Router on the way3 2 ms 1 ms 1 ms 192.168.1.12 - BIG-IP Local self-ip internal4 2 ms 2 ms 3 ms 192.168.1.114 - Proxy IP5 4 ms 211 ms 4 ms 192.168.1.12 - BIG-IP Local self-ip - Now on the vs_proxy_return VLAN (verifed with tcpdump)6 Host unreachable Internal VLAN local Self-ip: 192.168.1.12Internal VLAN floating Self-ip: 192.168.1.14Proxy_return VLAN local Self-ip: 192.168.1.118Proxy_return VLAN floating Self-ip: 192.168.1.119 The Proxy is connected directly to the F5, no switches involved. One TP into port 1 and out again of port 2. There is no NATing in the proxy, so the packet should be untouched. Config: ltm virtual /Common/vs_proxy { description destination /Common/0.0.0.0:0 mask any pool /Common/pool_proxy profiles { /Common/fastL4 { } } source 0.0.0.0/0 translate-address disabled translate-port disabled vlans { /Common/internal } vlans-enabled } } ltm virtual /Common/vs_proxy_return { description "" destination /Common/0.0.0.0:0 mask any pool /Common/pool_gateway profiles { /Common/fastL4 { } } source 0.0.0.0/0 translate-address disabled translate-port disabled vlans { /Common/cp_proxy_return } vlans-enabled } Is this a bug, or am I doing something very very wrong here? This works on a customer I have, but on 1.4.1, this is done on 1.5.1 HF3.

YOur problem description is a bit unclear, but I'd like to point out a few things. The BIGIP is unlikely to be responding to Requests from your proxies. Your Proxies should be sending Connections to a specific IP address on the BigIP (a Virtual Address most likely), and so the response to the proxy will be the IP of the virtual. If you see some traffic from the Bigip to the Proxy and it is using a floating IP address, then it is likely to be traffic originating from a client, and also handled by a Virtual server. If you see traffic with a self-IP, then it is most likely to be monitor traffic (and you should probably ignore it). You will need to describe better what objects are involved, and how the traffic flows. Example: Ingres ->vlan internal -> Virtual vsinbound ->Egres: vlan proxy; -> Pool: proxy-pool Then paste the config of the virtual. Do this for all the relevant flows, and it should present a better picture what's going on...

After the traffic has passed the proxy, it returns to the F5 on a different interface(1.2) and is Auto Mapped before being sent to the pool containing the internet facing router. i do not see snat automap (source-address-translation { type automap }) in vs_proxy_return virtual server. are you using snat list for traffic from proxy? can you post the configuration? tmsh list snat (snat list name) But for some reason it all stops when the proxy tries to send the traffic back to the F5 on Int 1.2. In the tcpdump I can see that the F5 is responding to requests from the proxy with the same self-IP that is defined on the internal VLAN that is assigned to the fiber trunk. is the response of the request from proxy indeed? is tcp sequence and acknowledgment number correct?

There is a floating IP for every vlan, to ensure proper HA.

F5 BIG-IP answers with a self-ip that is not associated with that VLAN

BinaryCanary_19
Historic F5 Account
Jul 06, 2014
YOur problem description is a bit unclear, but I'd like to point out a few things.

The BIGIP is unlikely to be responding to Requests from your proxies. Your Proxies should be sending Connections to a specific IP address on the BigIP (a Virtual Address most likely), and so the response to the proxy will be the IP of the virtual. If you see some traffic from the Bigip to the Proxy and it is using a floating IP address, then it is likely to be traffic originating from a client, and also handled by a Virtual server. If you see traffic with a self-IP, then it is most likely to be monitor traffic (and you should probably ignore it).

You will need to describe better what objects are involved, and how the traffic flows.

Example:

Ingres ->vlan internal -> Virtual vsinbound ->Egres: vlan proxy; -> Pool: proxy-pool

Then paste the config of the virtual.

Do this for all the relevant flows, and it should present a better picture what's going on...
nitass
Employee
Jul 06, 2014
After the traffic has passed the proxy, it returns to the F5 on a different interface(1.2) and is Auto Mapped before being sent to the pool containing the internet facing router.

i do not see snat automap (source-address-translation { type automap }) in vs_proxy_return virtual server. are you using snat list for traffic from proxy? can you post the configuration?

tmsh list snat (snat list name)

But for some reason it all stops when the proxy tries to send the traffic back to the F5 on Int 1.2. In the tcpdump I can see that the F5 is responding to requests from the proxy with the same self-IP that is defined on the internal VLAN that is assigned to the fiber trunk.

is the response of the request from proxy indeed? is tcp sequence and acknowledgment number correct?

ReWrite_132188

Nimbostratus

Jul 07, 2014

Thanks for the answers. I know the explanation is kinda hard to understand..

Second try:

Ingres- vlan Internal -> Virtual vs_proxy -> Egres Vlan cp_proxy - > Pool: pool_proxy - > Proxy - > Ingres -> vlan cp_proxy_return -> Virtual vs_proxy_return - > Pool: pool_gateway -> Internet.

The traffic stops on Virtual vs_proxy_return. I can ping the F5 from the proxy, and the F5 can ping the proxy on the corrects IPs. But doing a packet dump I can only see the IP from the Internal vlan responding to packets from the Proxy..

Config

ltm snat-translation /Common/182.xx.xx.149 {
    address 182.xx.xx.149
    inherited-traffic-group true
    traffic-group /Common/traffic-group-1
}
ltm snat-translation /Common/182.xx.xx.150 {
    address 182.xx.xx.150
    inherited-traffic-group true
    traffic-group /Common/traffic-group-1
}
ltm snat-translation /Common/185.xx.xx.146 {
    address 185.xx.xx.146
    inherited-traffic-group true
    traffic-group /Common/traffic-group-1
}
ltm snatpool /Common/sNAT-pool-outbound-inet {
    members {
        /Common/182.xx.xx.149
        /Common/182.xx.xx.150
    }
}
ltm virtual /Common/vs_ext_all {
    description 
    destination /Common/0.0.0.0:0
    mask any
    pool /Common/pool_proxy_ext
    profiles {
        /Common/fastL4 { }
    }
    source 0.0.0.0/0
    translate-address disabled
    translate-port disabled
    vlans {
        /Common/external
    }
    vlans-enabled
}
ltm virtual /Common/vs_ext_ret_all {
    description 
    destination /Common/0.0.0.0:0
    mask any
    pool /Common/pool_gateway_int
    profiles {
        /Common/fastL4 { }
    }
    source 0.0.0.0/0
    translate-address disabled
    translate-port disabled
    vlans {
        /Common/cp_proxy
    }
    vlans-enabled
}
ltm virtual /Common/vs_proxy {
    description 
    destination /Common/0.0.0.0:0
    mask any
    pool /Common/pool_proxy
    profiles {
        /Common/fastL4 { }
    }
    source 0.0.0.0/0
    translate-address disabled
    translate-port disabled
    vlans {
        /Common/internal
    }
    vlans-enabled
}
ltm virtual /Common/vs_proxy_https {
    description 
    destination /Common/0.0.0.0:443
    ip-protocol tcp
    mask any
    pool /Common/pool_proxy
    profiles {
        /Common/clientssl {
            context clientside
        }
        /Common/http { }
        /Common/serverssl {
            context serverside
        }
        /Common/tcp { }
    }
    rules {
        /Common/pre_proxy
    }
    source 0.0.0.0/0
    translate-address disabled
    translate-port enabled
    vlans {
        /Common/internal
    }
    vlans-enabled
}
ltm virtual /Common/vs_proxy_return {
    description 
    destination /Common/0.0.0.0:0
    mask any
    pool /Common/pool_gateway
    profiles {
        /Common/fastL4 { }
    }
    source 0.0.0.0/0
    translate-address disabled
    translate-port disabled
    vlans {
        /Common/cp_proxy_return
    }
    vlans-enabled
}
ltm virtual /Common/vs_proxy_return_http {
    description 
    destination /Common/0.0.0.0:80
    ip-protocol tcp
    mask any
    pool /Common/pool_gateway
    profiles {
        /Common/http { }
        /Common/serverssl-insecure-compatible {
            context serverside
        }
        /Common/tcp { }
    }
    rules {
        /Common/post_proxy
    }
    source 0.0.0.0/0
    source-address-translation {
        type automap
    }
    translate-address disabled
    translate-port enabled
    vlans {
        /Common/external
    }
    vlans-enabled
}
ltm virtual-address /Common/0.0.0.0 {
    address any
    arp disabled
    icmp-echo disabled
    mask any
    traffic-group /Common/traffic-group-1
}
ltm data-group internal /Common/bypass_nett {
    type ip
}
ltm data-group internal /Common/host_bypass {
    type string
}
ltm data-group internal /Common/hostname_bypass {
    type ip
}
ltm profile web-acceleration /Common/optimized-caching {
    app-service none
    cache-max-age 86400
    cache-object-max-size 2000000
    cache-object-min-size 0
    cache-size 7mb
    defaults-from /Common/webacceleration
}
ltm profile web-acceleration /Common/webacceleration {
    app-service none
    cache-aging-rate 9
    cache-client-cache-control-mode all
    cache-insert-age-header enabled
    cache-max-age 3600
    cache-max-entries 10000
    cache-object-max-size 50000
    cache-object-min-size 500
    cache-size 75mb
    cache-uri-exclude none
    cache-uri-include { .* }
    cache-uri-include-override none
    cache-uri-pinned none
    metadata-cache-max-size 25mb
}
net route /Common/DMZ-nett {
    gw 192.168.xx.1
    network 185.xx.xx.128/26
}
net route /Common/external_default_gateway {
    interface /Common/external
    network default
}
net route /Common/net-172.16.0.0-mask12 {
    gw 192.168.xx.1
    network 172.16.0.0/12
}
net route /Common/net-192.168.0.0-mask16 {
    gw 192.168.xx.1
    network 192.168.0.0/16

nitass
Employee
Jul 07, 2014
The traffic stops on Virtual vs_proxy_return. I can ping the F5 from the proxy, and the F5 can ping the proxy on the corrects IPs. But doing a packet dump I can only see the IP from the Internal vlan responding to packets from the Proxy.

have you configured floating self ip on every vlan?

sol7336: The SNAT Automap and self IP address selection

http://support.f5.com/kb/en-us/solutions/public/7000/300/sol7336.html
ReWrite_132188
Nimbostratus
Jul 07, 2014
There is a floating IP for every vlan, to ensure proper HA.

ReWrite_132188

Nimbostratus

Jul 07, 2014

Base_config

cm traffic-group /Common/traffic-group-local-only { }
cm trust-domain /Common/Root {
    ca-cert /Common/dtca.crt
    ca-cert-bundle /Common/dtca-bundle.crt
    ca-devices { /Common/xx /Common/xx }
    ca-key /Common/dtca.key
    guid xx
    status initialized
    trust-group /Common/device_trust_group
}
net route-domain /Common/0 {
    id 0
    vlans {
        /Common/http-tunnel
        /Common/socks-tunnel
        /Common/HA
        /Common/external
        /Common/internal
        /Common/cp_proxy
        /Common/cp_proxy_return
    }
}
net self /Common/185.xx.xx.146 {
    address 185.xx.xx.146/25
    traffic-group /Common/traffic-group-1
    vlan /Common/external
}
net self /Common/192.168.xx.219 {
    address 192.168.xx.219/29
    traffic-group /Common/traffic-group-1
    vlan /Common/cp_proxy_return
}
net self /Common/192.168.xx.14 {
    address 192.168.xx.14/28
    traffic-group /Common/traffic-group-1
    vlan /Common/internal
}
net self /Common/192.168.xx.211 {
    address 192.168.xx.211/29
    traffic-group /Common/traffic-group-1
    vlan /Common/cp_proxy
}
net self /Common/185.xx.xx.144 {
    address 185.xx.xx.144/25
    traffic-group /Common/traffic-group-local-only
    vlan /Common/external
}
net self /Common/192.168.xx.12 {
    address 192.168.xx.12/28
    traffic-group /Common/traffic-group-local-only
    vlan /Common/internal
}
net self /Common/192.168.xx.209 {
    address 192.168.xx.209/29
    traffic-group /Common/traffic-group-local-only
    vlan /Common/cp_proxy
}
net self /Common/192.168.xx.217 {
    address 192.168.xx.217/29
    traffic-group /Common/traffic-group-local-only
    vlan /Common/cp_proxy_return
}
net self /Common/192.168.xx.201 {
    address 192.168.xx.201/29
    traffic-group /Common/traffic-group-local-only
    vlan /Common/HA
}
net self-allow {
    defaults {
        ospf:0
        tcp:161
        tcp:22
        tcp:4353
        tcp:443
        tcp:53
        udp:1026
        udp:161
        udp:4353
        udp:520
        udp:53
    }
}
net stp /Common/cist {
    interfaces {
        1.1 {
            external-path-cost 20000
            internal-path-cost 20000
        }
        1.2 {
            external-path-cost 20000
            internal-path-cost 20000
        }
    }
    trunks {
        Trunk_inbound_outbound {
            external-path-cost 2000
            internal-path-cost 2000
        }
    }
    vlans {
        /Common/HA
        /Common/cp_proxy
        /Common/cp_proxy_return
        /Common/external
        /Common/internal
    }
}
net trunk Trunk_inbound_outbound {
    interfaces {
        2.1
        2.2
    }
    lacp enabled
}
net vlan /Common/HA {
    description Failover
    failsafe-action failover
    failsafe-timeout 10
    interfaces {
        Trunk_inbound_outbound {
            tagged
        }
    }
    tag 3517
}
net vlan /Common/cp_proxy {
    description 
    interfaces {
        1.1 { }
    }
    tag 3518
}
net vlan /Common/cp_proxy_return {
    description 
    interfaces {
        1.2 { }
    }
    tag 3519
}
net vlan /Common/external {
    description "Trafikk ut"
    interfaces {
        Trunk_inbound_outbound {
            tagged
        }
    }
    tag 3511
}
net vlan /Common/internal {
    description 
    interfaces {
        Trunk_inbound_outbound {
            tagged
        }
    }
    tag 3500
}

nitass

Employee

Jul 07, 2014

But doing a packet dump I can only see the IP from the Internal vlan responding to packets from the Proxy.

again, is the response packet of the request from proxy?

have you ever tried tcpdump on bigip screen? did you see lis=/Common/vs_proxy_return in the line of the response packet?

[root@ve11a:Active:In Sync] config  tcpdump -nni 0.0 -s0 -c 10 port 23
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on 0.0, link-type EN10MB (Ethernet), capture size 65535 bytes
02:59:05.266764 IP 192.168.207.54.63243 > 172.28.24.10.23: S 1191863643:1191863643(0) win 8192 (mss 1260,nop,wscale 8,nop,nop,sackOK) in slot1/tmm0 lis=
02:59:05.267004 IP 172.28.24.10.23 > 192.168.207.54.63243: S 3126593467:3126593467(0) ack 1191863644 win 3780 (mss 1460,sackOK,eol) out slot1/tmm0 lis=/Common/bar
02:59:05.269906 IP 192.168.207.54.63243 > 172.28.24.10.23: . ack 1 win 65520 in slot1/tmm0 lis=/Common/bar
02:59:05.271480 IP 192.168.207.54.63243 > 172.28.24.10.23: P 1:22(21) ack 1 win 65520 in slot1/tmm0 lis=/Common/bar
02:59:05.271500 IP 172.28.24.10.23 > 192.168.207.54.63243: . ack 22 win 3801 out slot1/tmm0 lis=/Common/bar
02:59:05.277238 IP 200.200.200.14.63243 > 200.200.200.101.23: S 4146213709:4146213709(0) win 4380 (mss 1460,sackOK,eol) out slot1/tmm0 lis=/Common/bar
02:59:05.399602 IP 200.200.200.101.23 > 200.200.200.14.63243: S 2699578800:2699578800(0) ack 4146213710 win 5840 (mss 1460,nop,nop,sackOK) in slot1/tmm0 lis=/Common/bar
02:59:05.399625 IP 200.200.200.14.63243 > 200.200.200.101.23: . ack 1 win 4380 out slot1/tmm0 lis=/Common/bar
02:59:05.399647 IP 200.200.200.14.63243 > 200.200.200.101.23: P 1:22(21) ack 1 win 4380 out slot1/tmm0 lis=/Common/bar
02:59:05.476255 IP 200.200.200.101.23 > 200.200.200.14.63243: . ack 22 win 5840 in slot1/tmm0 lis=/Common/bar

ReWrite_132188

Nimbostratus

Jul 07, 2014

This is tcpdump data from the vs_proxy_return VLAN on int 1.2 on the BIG-IP.

I tried pinging and a regualar http request to www.vg.no.

13:44:46.673086 IP 185.32.91.150.lm-webwatcher > 195.88.55.16.http: S 1736017643:1736017643(0) win 8192 
13:44:49.670161 IP 185.32.91.150.lm-webwatcher > 195.88.55.16.http: S 1736017643:1736017643(0) win 8192 
13:44:50.406559 IP 192.168.252.12 > 185.32.91.150: ICMP host 195.88.55.16 unreachable, length 36
13:44:50.406579 IP 192.168.252.12 > 185.32.91.150: ICMP host 195.88.55.16 unreachable, length 36
13:44:50.406700 IP 185.32.91.150.lm-webwatcher > 195.88.55.16.http: R 1736017644:1736017644(0) ack 0 win 0
13:44:50.918318 IP 185.32.91.150.lm-webwatcher > 195.88.55.16.http: S 1736017643:1736017643(0) win 8192 
13:45:01.958484 IP 185.32.91.150.lm-webwatcher > 195.88.55.16.http: R 0:0(0) ack 1 win 0
13:45:01.958718 IP 195.88.55.16.http > 185.32.91.150.lm-webwatcher: R 1:1(0) ack 0 win 0
13:45:01.960035 IP 185.32.91.150.8209 > 195.88.54.16.http: S 1052416606:1052416606(0) win 8192 
13:45:04.974016 IP 185.32.91.150.8209 > 195.88.54.16.http: S 1052416606:1052416606(0) win 8192 
13:45:07.960917 IP 192.168.252.12 > 185.32.91.150: ICMP host 195.88.54.16 unreachable, length 36
13:45:07.960939 IP 185.32.91.150.8209 > 195.88.54.16.http: R 1052416607:1052416607(0) ack 0 win 0
13:45:07.960951 IP 192.168.252.12 > 185.32.91.150: ICMP host 195.88.54.16 unreachable, length 36
13:45:08.468489 IP 185.32.91.150.8209 > 195.88.54.16.http: S 1052416606:1052416606(0) win 8192 
13:45:15.049547 IP 185.32.91.150.8209 > 195.88.54.16.http: R 0:0(0) ack 1 win 0
13:45:15.049687 IP 195.88.54.16.http > 185.32.91.150.8209: R 1:1(0) ack 0 win 0

nitass
Employee
Jul 07, 2014
This is tcpdump data from the vs_proxy_return VLAN on int 1.2 on the BIG-IP.

can you try this command instead?

tcpdump -nni 0.0 -s0 host 195.88.55.16 and port 80

ReWrite_132188

Nimbostratus

Jul 07, 2014

Sure!

14:35:52.315196 IP 185.32.91.150.8338 > 195.88.55.16.80: S 742896523:742896523(0) win 8192  in slot1/tmm1 lis=
14:35:52.315253 IP 185.32.91.150.8338 > 195.88.55.16.80: S 742896523:742896523(0) win 8192  out slot1/tmm1 lis=/Common/vs_proxy
14:35:52.315233 IP 185.32.91.150.8339 > 195.88.55.16.80: S 1782147585:1782147585(0) win 8192  in slot1/tmm0 lis=
14:35:52.315269 IP 185.32.91.150.8339 > 195.88.55.16.80: S 1782147585:1782147585(0) win 8192  out slot1/tmm0 lis=/Common/vs_proxy
14:35:52.315947 IP 185.32.91.150.8338 > 195.88.55.16.80: S 742896523:742896523(0) win 8192  in slot1/tmm1 lis=
14:35:52.316162 IP 185.32.91.150.8339 > 195.88.55.16.80: S 1782147585:1782147585(0) win 8192  in slot1/tmm0 lis=
14:35:53.222188 IP 185.32.91.150.8338 > 195.88.55.16.80: R 742896524:742896524(0) ack 0 win 0 out slot1/tmm1 lis=/Common/vs_proxy
14:35:53.222207 IP 195.88.55.16.80 > 185.32.91.150.8338: R 1:1(0) ack 0 win 0 out slot1/tmm1 lis=/Common/vs_proxy
14:35:53.222431 IP 185.32.91.150.8338 > 195.88.55.16.80: R 0:0(0) ack 1 win 0 in slot1/tmm1 lis=/Common/vs_proxy_return
14:35:53.223547 IP 185.32.91.150.8339 > 195.88.55.16.80: R 1782147586:1782147586(0) ack 0 win 0 out slot1/tmm0 lis=/Common/vs_proxy
14:35:53.223554 IP 195.88.55.16.80 > 185.32.91.150.8339: R 1:1(0) ack 0 win 0 out slot1/tmm0 lis=/Common/vs_proxy
14:35:53.223685 IP 185.32.91.150.8339 > 195.88.55.16.80: R 0:0(0) ack 1 win 0 in slot1/tmm0 lis=/Common/vs_proxy_return
14:35:53.729457 IP 185.32.91.150.8339 > 195.88.55.16.80: S 1782147585:1782147585(0) win 8192  in slot1/tmm0 lis=
14:35:53.729496 IP 185.32.91.150.8339 > 195.88.55.16.80: S 1782147585:1782147585(0) win 8192  out slot1/tmm0 lis=/Common/vs_proxy
14:35:53.729450 IP 185.32.91.150.8338 > 195.88.55.16.80: S 742896523:742896523(0) win 8192  in slot1/tmm1 lis=
14:35:53.729496 IP 185.32.91.150.8338 > 195.88.55.16.80: S 742896523:742896523(0) win 8192  out slot1/tmm1 lis=/Common/vs_proxy
14:35:53.729893 IP 185.32.91.150.8338 > 195.88.55.16.80: S 742896523:742896523(0) win 8192  in slot1/tmm1 lis=
14:35:53.729984 IP 185.32.91.150.8339 > 195.88.55.16.80: S 1782147585:1782147585(0) win 8192  in slot1/tmm0 lis=
14:35:59.735636 IP 185.32.91.150.8339 > 195.88.55.16.80: S 1782147585:1782147585(0) win 8192  in slot1/tmm0 lis=/Common/vs_proxy
14:35:59.735654 IP 185.32.91.150.8339 > 195.88.55.16.80: S 1782147585:1782147585(0) win 8192  out slot1/tmm0 lis=/Common/vs_proxy
14:35:59.735648 IP 185.32.91.150.8338 > 195.88.55.16.80: S 742896523:742896523(0) win 8192  in slot1/tmm1 lis=/Common/vs_proxy
14:35:59.735668 IP 185.32.91.150.8338 > 195.88.55.16.80: S 742896523:742896523(0) win 8192  out slot1/tmm1 lis=/Common/vs_proxy
14:35:59.735826 IP 185.32.91.150.8338 > 195.88.55.16.80: S 742896523:742896523(0) win 8192  in slot1/tmm1 lis=/Common/vs_proxy_return
14:35:59.735796 IP 185.32.91.150.8339 > 195.88.55.16.80: S 1782147585:1782147585(0) win 8192  in slot1/tmm0 lis=/Common/vs_proxy_return
14:36:05.222183 IP 185.32.91.150.8338 > 195.88.55.16.80: R 0:0(0) ack 1 win 0 out slot1/tmm1 lis=/Common/vs_proxy
14:36:05.222202 IP 195.88.55.16.80 > 185.32.91.150.8338: R 1:1(0) ack 0 win 0 out slot1/tmm1 lis=/Common/vs_proxy
14:36:05.222448 IP 185.32.91.150.8338 > 195.88.55.16.80: R 0:0(0) ack 1 win 0 in slot1/tmm1 lis=/Common/vs_proxy_return
14:36:05.223696 IP 185.32.91.150.8339 > 195.88.55.16.80: R 0:0(0) ack 1 win 0 out slot1/tmm0 lis=/Common/vs_proxy
14:36:05.223704 IP 195.88.55.16.80 > 185.32.91.150.8339: R 1:1(0) ack 0 win 0 out slot1/tmm0 lis=/Common/vs_proxy
14:36:05.223994 IP 185.32.91.150.8339 > 195.88.55.16.80: R 0:0(0) ack 1 win 0 in slot1/tmm0 lis=/Common/vs_proxy_return
14:36:19.571174 IP 185.32.91.150.8347 > 195.88.55.16.80: S 3918794636:3918794636(0) win 8192  in slot1/tmm1 lis=
14:36:19.571226 IP 185.32.91.150.8347 > 195.88.55.16.80: S 3918794636:3918794636(0) win 8192  out slot1/tmm1 lis=/Common/vs_proxy
14:36:19.571608 IP 185.32.91.150.8347 > 195.88.55.16.80: S 3918794636:3918794636(0) win 8192  in slot1/tmm1 lis=
14:36:22.574181 IP 185.32.91.150.8347 > 195.88.55.16.80: S 3918794636:3918794636(0) win 8192  in slot1/tmm1 lis=/Common/vs_proxy
14:36:22.574208 IP 185.32.91.150.8347 > 195.88.55.16.80: S 3918794636:3918794636(0) win 8192  out slot1/tmm1 lis=/Common/vs_proxy
14:36:22.574409 IP 185.32.91.150.8347 > 195.88.55.16.80: S 3918794636:3918794636(0) win 8192  in slot1/tmm1 lis=/Common/vs_proxy_return
14:36:25.570207 IP 185.32.91.150.8347 > 195.88.55.16.80: R 3918794637:3918794637(0) ack 0 win 0 out slot1/tmm1 lis=/Common/vs_proxy
14:36:25.570217 IP 195.88.55.16.80 > 185.32.91.150.8347: R 1:1(0) ack 0 win 0 out slot1/tmm1 lis=/Common/vs_proxy
14:36:25.570526 IP 185.32.91.150.8347 > 195.88.55.16.80: R 0:0(0) ack 1 win 0 in slot1/tmm1 lis=/Common/vs_proxy_return
14:36:26.084242 IP 185.32.91.150.8347 > 195.88.55.16.80: S 3918794636:3918794636(0) win 8192  in slot1/tmm1 lis=
14:36:26.084296 IP 185.32.91.150.8347 > 195.88.55.16.80: S 3918794636:3918794636(0) win 8192  out slot1/tmm1 lis=/Common/vs_proxy
14:36:26.084680 IP 185.32.91.150.8347 > 195.88.55.16.80: S 3918794636:3918794636(0) win 8192  in slot1/tmm1 lis=
14:36:31.879833 IP 195.88.55.16.80 > 185.32.91.150.8347: R 1:1(0) ack 0 win 0 out slot1/tmm1 lis=/Common/vs_proxy_return
14:36:31.879860 IP 185.32.91.150.8347 > 195.88.55.16.80: R 0:0(0) ack 1 win 0 out slot1/tmm1 lis=/Common/vs_proxy
14:36:31.879865 IP 195.88.55.16.80 > 185.32.91.150.8347: R 1:1(0) ack 0 win 0 out slot1/tmm1 lis=/Common/vs_proxy
14:36:31.880012 IP 195.88.55.16.80 > 185.32.91.150.8347: R 1:1(0) ack 0 win 0 in slot1/tmm1 lis=
14:36:31.880101 IP 185.32.91.150.8347 > 195.88.55.16.80: R 0:0(0) ack 1 win 0 in slot1/tmm1 lis=

nitass
Employee
Jul 07, 2014
on the /Common/vs_proxy, i think i do not see syn-ack from proxy.

Forum Discussion

F5 BIG-IP answers with a self-ip that is not associated with that VLAN

Recent Discussions

Background Tasks

Which process is consuming higher CPU

SSL bridging without SSL proxy forward

Big-IP VE edition for MacBook M4 Chip

Client SSL Profile set to Require Client Certificate breaks RDP in APM

Related Content

Copy over self IPs from several partitions

About Self IP, and Virtual IP

Question & Answer: Regarding CVE-2020-5902

New Virtual Server Pool, Self IP and routing configuration

Using Public IPs as a self, external and VS IPs

ABOUT DEVCENTRAL

RESOURCES

SUPPORT

PARTNERS