On 5/8/2022 3:16 AM, Willy Tarreau wrote:
There's no good solution to this, except by forcing the exact address
yourself. The BSD socket API doesn't permit to send UDP packets from a
specific source, so the commonly used approach for clients is to bind
while sending the first packet, but that
On Sat, May 07, 2022 at 09:11:30AM -0600, Shawn Heisey wrote:
> If you look closely at the tcpdump output, you'll notice that when haproxy
> replies, it replies from the actual IP address of the machine (.200) rather
> than the ucarp VIP (.170) where it received the request. Is this something
>
On 5/7/2022 9:11 AM, Shawn Heisey wrote:
A couple of days ago I noticed that quictls had made a 3.0.3 version
available. I upgraded and then tried to rebuild haproxy (master
branch). The compile failed. Don't they know they shouldn't change
API in a point release? (It's not even a good
A couple of days ago I noticed that quictls had made a 3.0.3 version
available. I upgraded and then tried to rebuild haproxy (master
branch). The compile failed. Don't they know they shouldn't change API
in a point release? (It's not even a good idea in a minor release
unless there is
4 matches
Mail list logo
