https://bz.apache.org/bugzilla/show_bug.cgi?id=70320
--- Comment #4 from xedex <[email protected]> --- (In reply to abernal from comment #3) > Thanks. I tried this locally: DocumentRoot on a CIFS mount (SMB 3.1.1, > default cache=strict), httpd 2.4.69, counting what the CIFS client reads in > /proc/fs/cifs/Stats. i tried that with debian 13 + apache2 (all last versions) -> still same problem then i tried that just right now with ubuntu 26.10 + nginx (also last version) to see if the problem is on apache2 alone. surprise. nope. its also with nginx and nearly same cfg as i used in apache but sure, converted for nginx. take a look at that interesting part ---log 1 start--- 2026-11-18 17:45:57.795186 ens3 Out IP 192.168.8.143.57458 > 192.168.8.129.445: Flags [P.], seq 720:792, ack 721, win 1022, options [nop,nop,TS val 3444002678 ecr 190625129], length 72 2026-11-18 17:45:57.797764 ens3 In IP 192.168.8.129.445 > 192.168.8.143.57458: Flags [P.], seq 721:793, ack 792, win 10000, options [nop,nop,TS val 190631273 ecr 3444002678], length 72 2026-11-18 17:45:57.797845 ens3 Out IP 192.168.8.143.57458 > 192.168.8.129.445: Flags [.], ack 793, win 1022, options [nop,nop,TS val 3444002681 ecr 190631273], length 0 2026-11-18 17:46:37.632290 ens3 In IP 172.110.223.81.40199 > 192.168.8.143.443: Flags [S], seq 627072495, win 1024, options [mss 1452], length 0 2026-11-18 17:46:37.632942 ens3 Out IP 192.168.8.143.443 > 172.110.223.81.40199: Flags [S.], seq 2299117300, ack 627072496, win 64240, options [mss 1460], length 0 2026-11-18 17:46:37.735315 ens3 In IP 172.110.223.81.40199 > 192.168.8.143.443: Flags [R], seq 627072496, win 1200, length 0 2026-11-18 17:46:59.235261 ens3 Out IP 192.168.8.143.57458 > 192.168.8.129.445: Flags [P.], seq 792:864, ack 793, win 1022, options [nop,nop,TS val 3444064118 ecr 190631273], length 72 2026-11-18 17:46:59.237187 ens3 In IP 192.168.8.129.445 > 192.168.8.143.57458: Flags [P.], seq 793:865, ack 864, win 10000, options [nop,nop,TS val 190637417 ecr 3444064118], length 72 2026-11-18 17:46:59.237349 ens3 Out IP 192.168.8.143.57458 > 192.168.8.129.445: Flags [.], ack 865, win 1022, options [nop,nop,TS val 3444064120 ecr 190637417], length 0 2026-11-18 17:47:14.608014 ens3 In IP 23.110.173.186.38558 > 192.168.8.143.443: Flags [S], seq 1782192566, win 64240, options [mss 1452,sackOK,TS val 2141012354 ecr 0,nop,wscale 11], length 0 2026-11-18 17:47:14.608699 ens3 Out IP 192.168.8.143.443 > 23.110.173.186.38558: Flags [S.], seq 3532999889, ack 1782192567, win 65160, options [mss 1460,sackOK,TS val 2486315458 ecr 2141012354,nop,wscale 9], length 0 2026-11-18 17:47:14.791994 ens3 In IP 23.110.173.186.38558 > 192.168.8.143.443: Flags [.], ack 1, win 32, options [nop,nop,TS val 2141012537 ecr 2486315458], length 0 2026-11-18 17:47:14.825407 ens3 In IP 23.110.173.186.38558 > 192.168.8.143.443: Flags [P.], seq 1:1934, ack 1, win 32, options [nop,nop,TS val 2141012570 ecr 2486315458], length 1933 2026-11-18 17:47:14.825616 ens3 Out IP 192.168.8.143.443 > 23.110.173.186.38558: Flags [.], ack 1934, win 133, options [nop,nop,TS val 2486315675 ecr 2141012570], length 0 2026-11-18 17:47:14.836640 ens3 Out IP 192.168.8.143.443 > 23.110.173.186.38558: Flags [P.], seq 1:2881, ack 1934, win 133, options [nop,nop,TS val 2486315686 ecr 2141012570], length 2880 2026-11-18 17:47:14.836752 ens3 Out IP 192.168.8.143.443 > 23.110.173.186.38558: Flags [P.], seq 2881:3333, ack 1934, win 133, options [nop,nop,TS val 2486315686 ecr 2141012570], length 452 2026-11-18 17:47:15.019937 ens3 In IP 23.110.173.186.38558 > 192.168.8.143.443: Flags [.], ack 2881, win 35, options [nop,nop,TS val 2141012765 ecr 2486315686], length 0 2026-11-18 17:47:15.019938 ens3 In IP 23.110.173.186.38558 > 192.168.8.143.443: Flags [.], ack 3333, win 37, options [nop,nop,TS val 2141012765 ecr 2486315686], length 0 2026-11-18 17:47:15.053052 ens3 In IP 23.110.173.186.38558 > 192.168.8.143.443: Flags [P.], seq 1934:2090, ack 3333, win 37, options [nop,nop,TS val 2141012798 ecr 2486315686], length 156 2026-11-18 17:47:15.053053 ens3 In IP 23.110.173.186.38558 > 192.168.8.143.443: Flags [P.], seq 2090:2588, ack 3333, win 37, options [nop,nop,TS val 2141012798 ecr 2486315686], length 498 2026-11-18 17:47:15.054236 ens3 Out IP 192.168.8.143.443 > 23.110.173.186.38558: Flags [P.], seq 3333:3620, ack 2588, win 144, options [nop,nop,TS val 2486315904 ecr 2141012798], length 287 2026-11-18 17:47:15.054618 ens3 Out IP 192.168.8.143.443 > 23.110.173.186.38558: Flags [P.], seq 3620:3907, ack 2588, win 144, options [nop,nop,TS val 2486315904 ecr 2141012798], length 287 2026-11-18 17:47:15.055475 ens3 Out IP 192.168.8.143.57458 > 192.168.8.129.445: Flags [P.], seq 864:1212, ack 865, win 1022, options [nop,nop,TS val 3444079938 ecr 190637417], length 348 2026-11-18 17:47:15.062761 ens3 In IP 192.168.8.129.445 > 192.168.8.143.57458: Flags [P.], seq 865:1377, ack 1212, win 10034, options [nop,nop,TS val 190639000 ecr 3444079938], length 512 2026-11-18 17:47:15.062888 ens3 Out IP 192.168.8.143.57458 > 192.168.8.129.445: Flags [.], ack 1377, win 1022, options [nop,nop,TS val 3444079946 ecr 190639000], length 0 2026-11-18 17:47:15.063850 ens3 Out IP 192.168.8.143.57458 > 192.168.8.129.445: Flags [P.], seq 1212:1576, ack 1377, win 1022, options [nop,nop,TS val 3444079947 ecr 190639000], length 364 2026-11-18 17:47:15.068495 ens3 In IP 192.168.8.129.445 > 192.168.8.143.57458: Flags [P.], seq 1377:1905, ack 1576, win 10067, options [nop,nop,TS val 190639000 ecr 3444079947], length 528 2026-11-18 17:47:15.070129 ens3 Out IP 192.168.8.143.443 > 23.110.173.186.38558: Flags [P.], seq 3907:3978, ack 2588, win 144, options [nop,nop,TS val 2486315920 ecr 2141012798], length 71 --- log 1 ends --- did you see first the normal 17:45:57 to 17:46:59 communication? thats regular 1 min difference. but after that long conversations between that suspect ip's which are mostly the regular ubuntu ip's who communicate with the intern 192.168.8.143 server ip comes the long shoot of --- log 2 starts --- 2026-11-18 17:47:15.071005 ens3 Out IP 192.168.8.143.57458 > 192.168.8.129.445: Flags [P.], seq 1576:1940, ack 1905, win 1022, options [nop,nop,TS val 3444079954 ecr 190639000], length 364 2026-11-18 17:47:15.073011 ens3 In IP 192.168.8.129.445 > 192.168.8.143.57458: Flags [P.], seq 1905:2142, ack 1940, win 10101, options [nop,nop,TS val 190639001 ecr 3444079954], length 237 2026-11-18 17:47:15.074978 ens3 Out IP 192.168.8.143.57458 > 192.168.8.129.445: Flags [P.], seq 1940:2304, ack 2142, win 1022, options [nop,nop,TS val 3444079958 ecr 190639001], length 364 2026-11-18 17:47:15.079933 ens3 In IP 192.168.8.129.445 > 192.168.8.143.57458: Flags [P.], seq 2142:2678, ack 2304, win 10134, options [nop,nop,TS val 190639001 ecr 3444079958], length 536 --- log 2 ends --- repeatings. all at 17:47:15 in ms speed. i counted around 1100 requests in araund 1 secound and same to 17:47:16.xxxxx. and so on. so it looks to me that the other ip's under log 1 send some commands to do that. i mean it's possible if the AI found more then 1000 vulnerabilities in the last 5 days in the linux kernel, because if you see the access.log, there are no requests in exact that moment 17:47:15.xxxx --- access.log starts--- 104.23.223.57 - - [18/Nov/2026:17:26:40 +0100] "GET /wp-admin/install.php?step=1 HTTP/2.0" 404 146 "-" "http://schatt.d> 45.198.224.125 - - [18/Nov/2026:17:44:40 +0100] "GET / HTTP/1.1" 301 162 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; r> 23.110.173.186 - - [18/Nov/2026:17:47:16 +0100] "GET / HTTP/2.0" 200 101 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64)> 192.178.7.193 - - [18/Nov/2026:17:50:46 +0100] "GET /robots.txt HTTP/1.1" 301 162 "-" "Mozilla/5.0 (compatible; Googleb> --- access.log ends--- yea...i cant do more atm. maybe you got an idea? i mean i cant buy now an new NAS to test it over NFS to see if that could be a CIFS problem =( and dont know one, but maybe its an intern debian hack? =/ i mean it's also suspect if ip 199.232.18.49 dp the same. it creates also around 1300 requests in 1 secound and other ip's too. > So here the traffic follows the requests and the size of the files served. > To compare with yours, please send for the same period as a capture: the > access log lines (with the sum of the %b sizes) and the size of the files > served from the share. If the traffic does not match the requests, it comes > from somewhere else (the CIFS client, the NAS or another process). > > My setup is not yours (Samba on loopback, not your NAS and kernel), so this > is not conclusive yet. hope the info above is more helpful...br -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
