jmp242 0 Posted 4 hours ago Share Posted 4 hours ago Ever since we deployed 8.1.6.0 we're seeing breakage on MacOS. Specifically all network access pauses for 30seconds or so. Example during ping 64 bytes from 128.84.44.120: icmp_seq=349 ttl=64 time=39.999 ms 64 bytes from 128.84.44.120: icmp_seq=350 ttl=64 time=26.542 ms 64 bytes from 128.84.44.120: icmp_seq=351 ttl=64 time=23.189 ms Request timeout for icmp_seq 352 Request timeout for icmp_seq 353 Request timeout for icmp_seq 354 Request timeout for icmp_seq 355 Request timeout for icmp_seq 356 Request timeout for icmp_seq 357 Request timeout for icmp_seq 358 Request timeout for icmp_seq 359 Request timeout for icmp_seq 360 Request timeout for icmpWe've tried disabling _seq 361 Request timeout for icmp_seq 362 Request timeout for icmp_seq 363 Request timeout for icmp_seq 364 Request timeout for icmp_seq 365 Request timeout for icmp_seq 366 Request timeout for icmp_seq 367 Request timeout for icmp_seq 368 Request timeout for icmp_seq 369 Request timeout for icmp_seq 370 Request timeout for icmp_seq 371 Request timeout for icmp_seq 372 Request timeout for icmp_seq 373 64 bytes from 128.84.44.120: icmp_seq=352 ttl=64 time=22049.514 ms 64 bytes from 128.84.44.120: icmp_seq=353 ttl=64 time=21052.131 ms 64 bytes from 128.84.44.120: icmp_seq=354 ttl=64 time=20050.618 ms 64 bytes from 128.84.44.120: icmp_seq=355 ttl=64 time=19052.432 ms 64 bytes from 128.84.44.120: icmp_seq=356 ttl=64 time=18052.368 ms 64 bytes from 128.84.44.120: icmp_seq=357 ttl=64 time=17053.837 ms 64 bytes from 128.84.44.120: icmp_seq=358 ttl=64 time=16058.246 ms 64 bytes from 128.84.44.120: icmp_seq=359 ttl=64 time=15056.902 ms 64 bytes from 128.84.44.120: icmp_seq=360 ttl=64 time=14055.501 ms 64 bytes from 128.84.44.120: icmp_seq=361 ttl=64 time=13054.711 ms 64 bytes from 128.84.44.120: icmp_seq=362 ttl=64 time=12051.026 ms 64 bytes from 128.84.44.120: icmp_seq=363 ttl=64 time=11048.996 ms 64 bytes from 128.84.44.120: icmp_seq=364 ttl=64 time=10046.244 ms 64 bytes from 128.84.44.120: icmp_seq=365 ttl=64 time=9046.100 ms 64 bytes from 128.84.44.120: icmp_seq=366 ttl=64 time=8046.033 ms 64 bytes from 128.84.44.120: icmp_seq=367 ttl=64 time=7045.444 ms When the dropouts happened the CPU usage of "com.eset.firewall" would spike to 100+ % of CPU. After a minute or so it would drop back to less than 10% and network would return. We've found that uninstalling ESET fixes these - various suggestions from the forums to turn off various scanning does not seem to be effective. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.