On 4/10/22 16:09, Shawn Heisey wrote: > On 4/10/2022 3:41 AM, Frederic Lecaille wrote: >> Here is a "bind" line example (SSL must be enable as for TCP) for a >> QUIC/h3 listener: >> >> bind quic4@<ip:port> ssl crt <your-cert> proto quic alpn h3 > > Frederic is replying only to me, not including the list.
Ooop, indeed, sorry. > I'm following the advice from Willy to put quic handling on a separate > haproxy process. I copied my 2.4 haproxy.cfg, deleted a bunch of stuff > that's irrelevant or caused config errors and seemed like I could do > without. > > I still have config errors. I updated my bind line to this: > > bind quic4@0.0.0.0:443 ssl crt > /etc/ssl/certs/local/mainwildcards.pem proto quic alpn h3 > > That produces the following when checking the config file: > > [ALERT] (821651) : config : parsing [/etc/haproxy/haproxy6.cfg:52] : > 'bind' : unsupported protocol family 2 for address 'quic4@0.0.0.0:443' Are you sure you run the correct binary? This is exactly the error we get when we try to bind a QUIC address with a haproxy binary without QUIC support compiled.
