Forum Discussion

Aditya_Mehra's avatar
Aditya_Mehra
Icon for Cirrus rankCirrus
Jan 24, 2019

Forward traffic to pool member with same port as VS - VIP is on port 0

Hi,

 

Need help in setting up an application.

 

VIP is on port 0 as the application can work on 30 ports.

 

Now i want to forward the traffic to the pool member on the same port as it arrives on the virtual server.

 

eg: abc.com:4448 -> VIP is on port 0 so it will take it

 

Now it should go to the pool memebrs on port 4448 as well, and so on for any other request coming in to the VS

 

application delivery
BIG-IP
  • Kai_Wilke's avatar
    Kai_Wilke
    Icon for MVP rankMVP
    Jan 24, 2019

    Hi Aditya,

    define your Virtual Server as well as your Pool Members with the 

    :any
    port setting (Port 0 in WebUI).

    This will make sure your VS accepts traffic on every port and forwards the traffic to your pool members on the same port.

    Cheers, Kai

  • Stanislas_Piro2's avatar
    Stanislas_Piro2
    Icon for Cumulonimbus rankCumulonimbus
    Jan 24, 2019

    You can define the virtual server with port translation disabled... the virtual server won’t change the port

     

    • AceDawg1's avatar
      AceDawg1
      Icon for Nimbostratus rankNimbostratus
      Jan 28, 2019

      Have you tried running a capture (tcpdump and ssldump) to determine where SSL communications are breaking down? If you're not familiar with ssldump, check out: 

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

    • Aditya_Mehra's avatar
      Aditya_Mehra
      Icon for Cirrus rankCirrus
      Jan 30, 2019

      Hey, Did not take a tcp and ssl dump, but I added the below iRule and it works for http port.

       

      when CLIENT_ACCEPTED { if {([TCP::local_port] != 80) && ([TCP::local_port] != 8103)} { HTTP::disable } }

       

      But this does not work for https, the request passes through to the backend pool member succesfully but the X-Forwarded IP is not present. I believe as we disable the http profile then the X-Forwarded_http profile is not used at all.

       

      Any workaround for this?