Haproxy remap tcp port with single backend

haproxy

I'm using haproxy in tcp mode. I have a single frontend that listens to several ports:

frontend front
   mode tcp
   bind *:20000
   bind *:20001
   ...
   default_backend back

And a single backend that forwards these requests without changing ports:

backend back
   server myserver server.host.com check port 20000
   server anotherServer another.host.com check port 20000
   server mybackup backup.host backup.host.com check port 20000 backup
   # some other useful backend logic, like logging
   # which I don't want to repeat a bunch of times

Because we are supporting some legacy APIs, we need to accept some old, lower level ports and remap them. For example, I want to accept port 200 and remap it to 20000, 201 to 20001, etc.

I was hoping for a frontend directive to change port like you might do for a header in http mode, but I can't find one. Will have have to abandon my nice clean single backend?

Best Answer

I would go about using 2 backends if I were you.

If you insist, you can use the use-server <server> if <condition> option and test dst_port.

Something like: use-server bla20001 if dst_port 201 or something like this.

Related Solutions

HAProxy – ssl client ca chain cannot be verified

The files server.pem and client.pem should have 3 sections in it and should look like this:

The private key might not be RSA, but it should be first. The first certificate is the signed server certificate. The second certificate should be the CA certificate. You can copy and paste each section using a text editor. To check your certificate, run this.

$ openssl verify -CAfile ca1-certificate.pem server.pem
server.pem: OK

Haproxy logging not work

To have these messages end up in - for example - /var/log/haproxy.log you will need to do two things:

configure your syslog to accept network logs - at least on localhost
configure haproxy to send events to 127.0.0.1 on local2/local3 or any such facility

So, your haproxy.cfgs global section would look something like:

global
    log         127.0.0.1 local2 notice
    log         127.0.0.1 local3

While your syslog.conf should look like:

local2.*        /var/log/haproxy
local3.*        /var/log/haproxy-access_log

If you use modern distro with rsyslog, then just create a file called

/etc/rsyslog.d/haproxy.conf

with following contents:

$ModLoad imudp
$UDPServerAddress 127.0.0.1
$UDPServerRun 514

local2.*        /var/log/haproxy
local3.*        /var/log/haproxy-access_log

And after that restart rsyslogd and haproxy.

Best Answer

Related Solutions

HAProxy – ssl client ca chain cannot be verified

Haproxy logging not work

Related Topic