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.

Created a separated Feature request https://vyos.dev/T7516

Different values originate from the Kernel source code depending on the actual available amount of system memory:

• min value 1024
• up to 4GB RAM 65536
• more then 4GB RAM 262144

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

Caused by this commit that merges iproute2-next into the main branch of iproute2 and introduced in v6.15.0 which was pushed to debian-backports a couple of days ago.

PR https://github.com/vyos/vyos-vpp/pull/35

The same bug with nat44

set interfaces ethernet eth0 address '192.168.122.14/24'
set interfaces ethernet eth0 description 'WAN'
set interfaces ethernet eth1 address '100.64.0.1/24'
set interfaces ethernet eth1 description 'LAN'

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