Forum Discussion

kleis_oenema_67's avatar
kleis_oenema_67
Icon for Nimbostratus rankNimbostratus
Jan 20, 2014

Forward proxy HTTP_Proxy_v3.2 problem

We use a forward proxy, the DevCentral irule “HTTP_Proxy_v3.2” running on a F5 version 10.2.4. hf7. The Irule has been in place for a rather long time and its working fine when websites in the internet are addressed. The customer complained that he could not reach certain addresses using the proxy. We use contexts or partitions with strict route isolation The source system where the requests are launched is in partition, route-domain 17 address 161.10.10.20 /24 The target is in the same route-domain 17 and has address 161.10.10.40 /24 we call this "mysite.com" However the target is load-balanced and it's VIP address is 212.158.21.34 /25 using automap, residing in route-domain 16 We have the forward proxy HTTP_Proxy_v3.2 also in route-domain 16 listening on address 10.192.103.33 port 8080 having a snat-pool-address 212.158.21.25 /25

 

So the traffic flow should be like: 1) Initial request from 161.10.10.20 to mysite.com 2) The browser has as proxy 10.192.103.33 port 8080 and the request will be forwarded to the proxy 3) The proxy makes a DNS request to resolve mysite.com and retrieves the address 212.158.21.34 4) After the successful dns resolving we expect a connection setup from snat-pool-address 212.158.21.25 to the Vip address 212.158.21.34. However this request we never see appearing in a TCP dump. Instead we see in the tcpdump from the forward proxy, HTTP_Proxy_v3.2, to the client the message “Reset cause: BIG-IP: [0x11c9fc6:9870] {peer} TCP retransmit tim” .

 

Somehow the f5 proxy irule does not handle this kind of request when the request addresses are all contained in the same F5 box. Connections towards the internet say; www.google.com, using the F5 proxy irule, works fine. We have run out of our options to get this working, can this work, and if so, how can we get it working.

 

Who can help us out!!! Kleis

 

1 Reply

  • 4) After the successful dns resolving we expect a connection setup from snat-pool-address 212.158.21.25 to the Vip address 212.158.21.34. However this request we never see appearing in a TCP dump.

     

    i think it is expected because the target is another virtual server in the same unit. in this case, i think you need to use virtual command to route traffic to the target virtual server.

     

    virtual

     

    https://devcentral.f5.com/wiki/irules.virtual.ashx