A change in behaviour in libpcap means that ctdb_killtcp no longer works when configured with --enable-pcap and compiled against libpcap ≥ 1.9.1. See: https://github.com/the-tcpdump-group/libpcap/issues/860 and pcap_set_immediate_mode(3PCAP) for more details. About to post merge request with fix.
Merge request: https://gitlab.com/samba-team/samba/-/merge_requests/3225
This bug was referenced in samba master: d87041d8968e91db9d257445321b85693303f95e ffc2ae616d8fab7528fbdfd8c6b94c5b9a0e3a7c dc7b48c404337891b5105df4d6751cf549a533eb
Created attachment 18059 [details] Patch for v4-19-test Cherry picks cleanly, compiles, smoke tested
Created attachment 18060 [details] Patch for v4-18-test Cherry picks cleanly, compiles, smoke tested
Created attachment 18061 [details] Patch for v4-17-test Cherry picks cleanly on top of original pcap updates, from ~12 months ago. Including patch for v4-17-test on the basis that any use of pcap_open_live() to create a file descriptor for use with tevent is likely to be broken... and v4-17-stable might as well have a working version of this code (sane libpcap support that works with IB). Compiles, smoke tested.
Comment on attachment 18061 [details] Patch for v4-17-test Sorry, I messed up the reviewed-by tags :-(h
Comment on attachment 18061 [details] Patch for v4-17-test Having to review when not being formally asked by bugzilla is very confusing to me, sorry :-(
Pushed to autobuild-v4-{19,18,17}-test.
This bug was referenced in samba v4-19-test: 9f57371128d8ef40448651874857f445be6ed041 58e7d6a945136fe9dd26810f4a22e48d9cf0943f 1af8a09966a82a19d269cc1339232f271dff51bc
This bug was referenced in samba v4-17-test: 74d43dd395b0481d1c7588e80a0e5cb542e7124b bb905f04b505369e805613e694c2cbb62bd91dee 8d1e4f1d4f183bde3a741e0ffccf2ac7c4f08d4e
This bug was referenced in samba v4-18-test: 550972627b745fe01600fb5bd705472554372f9b 2b5512712e50761117bacd8c78fc3c45e846ee90 5fac5b7b2fd3a61401b46f8dfd9ba38aeb4a5091
Closing out bug report. Thanks!
This bug was referenced in samba v4-19-stable (Release samba-4.19.0): 9f57371128d8ef40448651874857f445be6ed041 58e7d6a945136fe9dd26810f4a22e48d9cf0943f 1af8a09966a82a19d269cc1339232f271dff51bc
This bug was referenced in samba v4-17-stable (Release samba-4.17.11): 74d43dd395b0481d1c7588e80a0e5cb542e7124b bb905f04b505369e805613e694c2cbb62bd91dee 8d1e4f1d4f183bde3a741e0ffccf2ac7c4f08d4e
This bug was referenced in samba v4-18-stable (Release samba-4.18.7): 550972627b745fe01600fb5bd705472554372f9b 2b5512712e50761117bacd8c78fc3c45e846ee90 5fac5b7b2fd3a61401b46f8dfd9ba38aeb4a5091