https://github.com/vyos/vyos-1x/pull/4548

HI ,
I tested it . it works well. Could you please merge it into stable version vyos 1.4 ? Many thanks!

PR https://github.com/vyos/vyos-1x/pull/4547

This most likely a cause https://vyos.dev/T7459

PR https://github.com/vyos/vyos-1x/pull/4023

Need to check with the latest rolling release, as we have more flexibility in the bridge firewall. But command set interfaces bridge br0 ip adjust-mss '1377', with no extra config, most probably won't have desired effect.

PR: https://github.com/vyos/vyos-1x/pull/4546

Could be closed

vyos@r14# grep speed /opt/vyatta/etc/config/config.boot
            speed "115200"
[edit]
vyos@r14#

PR https://github.com/vyos/vyos-1x/pull/4545

https://github.com/vyos/vyos-vpp/pull/36

PR: https://github.com/vyos/vyos-1x/pull/4544

I stumbled over it today on my 1.4 boxes. It would be nice to have the possibilty to exclude forwarding traffic from conntrack.

Sorry, my bad, capturing traffic send from the haproxy to the backend actually contains the X-Forwarded-For header. Simply close my request and thanks for the quick answer / interaction.

Would you like to create a PR?

You're right, headers for port and protocol are being added but not the host.

It already should work if the backend mode http https://github.com/vyos/vyos-1x/blob/a711ceb80158a1dcdeecd1570ca705684d636327/data/templates/load-balancing/haproxy.cfg.j2#L199-L203
Can you re-check?

Well, it could be an option in the load-balancing haproxy service definition, something like "option forwardedfor" that would enable the http header and feed it with real client IP.

If it helps with the investigation, the bug report in question is T7482. I had to trim the text down quite a bit for the Task Tracker to allow me to create it.

Any idea for CLI?

@mykolaba unfortunately, it's impossible because, according to our current Cloudflare plan, events are only available within the last 72 hours.