Hi,
On 30.08.24 19:11, Willy Tarreau wrote:
Ah! so if there are any bugs left, we should be aware soon 😉
great to see MPTCP landing in haproxy currently! Thanks for everyone
having worked on this. I've looked at the patch set finally now (I wish
I had time to do that a bit earlier).
The syntax to add MPTCP support in the backend is not quite intuitive.
From the manual I couldn't actually see how it can be done, I initially
thought from just reading the manual, that the backend wouldn't support
mptcp. Until I looked at the patchset and the examples/mptcp.cfg file,
which contains this:
# MPTCP is usually used on the frontend, but it is also possible
# to enable it to communicate with the backend
backend mptcp_backend
server mptcp_server mptcp@[::]:4331
I have to admit I never used the proto@ syntax in backend definitions,
didn't even know it was possible here :). I think it would be good if
the manual would explain a little lit more verbose how mptcp is being
activated for backends. I would also not write that "MPTCP is usually
used on the frontend". My first productive use case requires mptcp on
both the frontend and the backend side, this isn't an unusual use case
at all.
What confuses me about that mptcp backend example is also the server
address [::], This looks more like a listening address; here should
probably be something like "some-mptcp-enabled-server.example.com" be
used, right?
Last but not least, the current haproxy 3.1-dev9 changelog doesn't
mention mptcp at all, shouldn't this be mentioned here?
Björn
