Redirect Port 80 to Port 81 while using Layer4 Virtual Server

Question

Hi there,  
&nbsp;  
&nbsp; Am very new to iRules and am trying to find out if its possible and if so how I can redirect traffic coming in on port 80 to port 81 using a Performance (Layer4) Virtual Server without resorting to SNAT. 
&nbsp;  
&nbsp; I have a VS with a VIP of 172.25.80.153:80 and I need traffic to go to the pool nodes on 172.25.80.28:81.  How ever, Layer 4 VS do not perform address or port translation by default.  Is it possible to perform this by using an iRule? 
&nbsp;  
&nbsp; Thanks 
&nbsp;  
&nbsp; Marc

jrahm · Answer

The LTM supports this with the fastL4 profile without Irules.  Just set your vip up on port 80 and your referenced pools up on port 81, the LTM will do the translation for you:

pool test-pool { 
    monitor all tcp 
    members 
       10.10.10.10:81 
       10.10.10.20:81 
 } 
 virtual test-vip { 
    pool test-pool 
    destination 10.10.8.10:80 
    ip protocol tcp 
    vlans public enable 
    profiles fastL4 
 }

marc_zw_57558 · Answer

I have the virtual server setup as below. 
&nbsp;  
&nbsp; pool rdb-ws-pool81 { 
&nbsp;    monitor all http_webservice 
&nbsp;    member 172.25.80.27:81 
&nbsp;    member 172.25.80.28:81 
&nbsp; } 
&nbsp;  
&nbsp; virtual rdb-ws-vs02 { 
&nbsp;    destination 172.25.80.153:http 
&nbsp;    ip protocol tcp 
&nbsp;    translate address disable 
&nbsp;    translate service disable 
&nbsp;    profile fastL4 
&nbsp;    pool rdb-ws-pool81 
&nbsp; } 
&nbsp;  
&nbsp; For some reason, traffic being passed to the nodes is hitting port 80 and not port 81. 
&nbsp;  
&nbsp; Any ideas?

jrahm · Answer

That's becuase you have translation disabled, any reason why?

marc_zw_57558 · Answer

It was setup following the instructions in the Configuration Guide.  It is using nPath routing which says to disable both Address and Port Translation.  
&nbsp;  
&nbsp; I did enable Port Translation but this stopped the VS from responding altogether.

jrahm · Answer

nPath routing is a completely different animal.  
&nbsp;    
&nbsp;  How will the tcp session ever establish?  You are hitting IP:80, but hearing back from IP:81, which will be reset.  This is why translation must be disabled for nPath routing, which means that your virtual must support the servers real port.  I can't think of any way around this other than tossing nPath routing, but then, I'm just a caveman...

Forum Discussion

Redirect Port 80 to Port 81 while using Layer4 Virtual Server

7 Replies

Recent Discussions

vulnerabilities (CVE-2020-36363), CVE-2016-0736,CVE-2019-6593-FOR VERSION BIGIP LTM-16.1.4

Chrome V 124+ on MacOS - Virtual Server Access Issue

Port Group on F5OS network setting

Advise on setting up IRULE

F5 iRule to replace host to path

Related Content

Integrating SSL Orchestrator with Fortinet FortiGate Virtual Edition as a Virtual Wire

Anchor Link Redirect

Quick Optimizations for F5 BIG-IP Virtual Edition

Check a Virtual Server's SSL Status

Virtual Server graphical App for F5 LTM