Re: [*EXT*] Re option forwardfor with IPv6

I'm currently facing a bug in gerrit 3.1.x which strip the last hextet of an IPv6 address. https://bugs.chromium.org/p/gerrit/issues/detail?id=12429#c4 A patch is on its way. Maybe it will make IPv6 logging more consistent. Will post my finding then. -- Ionel GARDAIS - Mail original

Re: mirroragent (haproxy)

Dear Christopher Configuration`s and info about haproxy and spoa version in attachment. >   * If possible, info about the mirror requests Requests coming to haproxy should go to a specific IP, as well as duplicated in our parser located on another IP address. On the parser’s machine, we don’t

Re: Segfault on 2.1.3

❦ 3 mars 2020 15:34 -07, Sean Reifschneider : > We've been running haproxy 1.8 series for quite a while. We're currently > in the process of updating to 2.1, and have installed from the vbernat PPA > on Ubuntu 18.04 using the same old config file. > > Now we are seeing segfaults a few times a

[PR] Add missing string length for lua sticktable lookup

Dear list! Author: Nathan Neulinger Number of patches: 1 This is an automated relay of the Github pull request: Add missing string length for lua sticktable lookup Patch title(s): Add missing string length for lua sticktable lookup Link: https://github.com/haproxy/haproxy/pull/530

stable-bot: Bugfixes waiting for a release 2.1 (17), 2.0 (13)

Hi, This is a friendly bot that watches fixes pending for the next haproxy-stable release! One such e-mail is sent periodically once patches are waiting in the last maintenance branch, and an ideal release date is computed based on the severity of these fixes and their merge date. Responses

Segfault on 2.1.3

We've been running haproxy 1.8 series for quite a while. We're currently in the process of updating to 2.1, and have installed from the vbernat PPA on Ubuntu 18.04 using the same old config file. Now we are seeing segfaults a few times a day: Mar 03 14:53:52 fw1.dev.realgo.com kernel:

[PATCH] limit cirrus-ci to stable freebsd images only

Hello, "snap" images are not usable. they break all the time. let us switch to freebsd-12.1 (the only available stable image) Cheers, Ilya Shipitcin From 19206e40c7f7d7bbef014a660fc2060f3882a9de Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Wed, 4 Mar 2020 01:18:02 +0500 Subject: [PATCH]

Re: option forwardfor with IPv6

Hello, On Tue, 3 Mar 2020 at 19:06, Ionel GARDAIS wrote: > > Hi, > > What is the expected behavior of "option forwardfor" with an IPv6 connection ? > Frontend listen on IPv4 and IPv6. The expected behavior is to insert the IPv6 address into the X-F-F header, and this is exactly what happens in

option forwardfor with IPv6

Hi, What is the expected behavior of "option forwardfor" with an IPv6 connection ? Frontend listen on IPv4 and IPv6. For IPv4 incoming connections, the server correctly displays the original IP address, wether the haproxy-to-server is made with IPv4 or IPv6. For IPv6 incoming connections,

Re: Log IP and port from haproxy to server

Thanks I was not looking at the proper documentation. El mar., 3 mar. 2020 a las 17:33, Tim Düsterhus () escribió: > > Pepe, > > Am 03.03.20 um 17:28 schrieb Pepe Charli: > > In "mode tcp", Is it possible to log the IP and port from haproxy to > > server (haproxyIP and haproxPort)? > > > >

Re: Log IP and port from haproxy to server

Pepe, Am 03.03.20 um 17:28 schrieb Pepe Charli: > In "mode tcp", Is it possible to log the IP and port from haproxy to > server (haproxyIP and haproxPort)? > > clientIP:ClientPort- > frontendIP:frontendPort > haproxyIP:haproxyPort -> serverIP:serverPort > %ci:%cp %fi:%fp >

Log IP and port from haproxy to server

In "mode tcp", Is it possible to log the IP and port from haproxy to server (haproxyIP and haproxPort)? clientIP:ClientPort- > frontendIP:frontendPort haproxyIP:haproxyPort -> serverIP:serverPort %ci:%cp %fi:%fp %??:%?? %si:%sp Thanks,

Re: mirroragent (haproxy)

Le 03/03/2020 à 14:39, Tuktamyshev Ainur a écrit : Dear, Collegues. There was a problem when mirroring traffic through Haproxy. In our spoa-mirror logs next mistakes: [ 0][0.000600] --- start --- 2020-03-03 15:48:30 - [ 1][ 318.942594] <1:26> (E) Failed to

[PATCH] MINOR: ssl: add "ca-no-names-file" directive

rebase from dev branch:(https://github.com/haproxy/haproxy/issues/404)++ManuLe 20 déc. 2019 à 17:00, Emmanuel Hocdet a écrit :patch update,Le 19 déc. 2019 à 17:08, Emmanuel Hocdet a écrit :With this proposition, ca-root-file should be rename to something like

interpreting haproxy 2.1 EOL statement

Hi, >From the following: $ ~/git.haproxy.org/haproxy-2.1/haproxy -v HA-Proxy version 2.1.3-ce757f-13 2020/02/21 - https://haproxy.org/ Status: stable branch - will stop receiving fixes around Q1 2021. Known bugs: http://www.haproxy.org/bugs/bugs-2.1.3.html that EOL is around Q1 2021.

mirroragent (haproxy)

Dear, Collegues. There was a problem when mirroring traffic through Haproxy. In our spoa-mirror logs next mistakes: [ 0][0.000600] --- start --- 2020-03-03 15:48:30 - [ 1][ 318.942594] <1:26> (E) Failed to receive frame data: Stale file handle [ 2][ 416.600422]

Re: Let's Encrypt ca-file for check-ssl on server line

Hi all. Thanks for help. Regards Aleks On 02.03.20 23:25, Tim Düsterhus wrote: Aleks, Am 02.03.20 um 23:19 schrieb Aleksandar Lazic: I think I found the solution. ``` curl -vO https://letsencrypt.org/certs/isrgrootx1.pem.txt curl -vo