Hi Olivier,
Thanks for the time you're taking to check the issue.
I'll get an environment back with TCP splicing enabled and I'll run it
in GDB and provide you a core dump
Best Regards,
--
Julien Semaan
jsem...@inverse.ca :: +1 (866) 353-6153 *155 ::www.inverse.ca
Inverse inc
e're black-holing the traffic since we use
haproxy for our captive portal
I'd be happy to provide a pcap but for privacy reasons I can't
extract it from a production environment and I can't see to replicate it
in lab.
Thanks!
--
Julien Semaan
jsem...@inverse.ca :: +1 (866) 353-6153 *155
be glad to provide them or
if you have a pcap I can replay to generate this issue in our lab.
Best Regards,
--
Julien Semaan
jsem...@inverse.ca :: +1 (866) 353-6153 *155 ::www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
On 2018-07-24 12
Doing it with the patch does the equivalent of disabling it with the
option (realized there was an option afterwards).
We're more looking to know if the haproxy team is interested in getting
the issue addressed more than just getting the workaround
Thanks!
--
Julien Semaan
jsem
be found with this limited
information.
After commenting out the code for TCP splicing with the patch attached
to the email, then the issue stopped happening.
Best Regards,
--
Julien Semaan
jsem...@inverse.ca :: +1 (866) 353-6153 *155 ::www.inverse.ca
Inverse inc. :: Leaders behind SOGo (ww
5 matches
Mail list logo