![]() ![]() Unfortunately, we won't be watching any TV this weekend, so we won't be exercising channels in the usual way until Monday, although I can leave an Apple TV client playing continuously. Before your reply, I'd jumped the gun and uninstalled Little Snitch, so I guess my first testing period will be without Little Snitch in the mix. Okay, I'll be recording the netstat -anL minutely. It goes up to 128, but then resets back to 18, instead of 0. Now I'll run: sudo hping3 -q -c 256 -S -p 8089 -faster localhost echo date netstat -anL | grep 8089 netstat -nt | grep 8089 | head -6 sleep 2 echo date netstat -anL | grep 8089 - it returns: HPING localhost (utun4 127.0.0.1): S set, 40 headers + 0 data bytes And now it's 18/18/128, before even attempting your hping script. However, I just ran the netstat again, and now it's 17/17/128 *.8089 - I'm not sure what incremented it, but another household member is now using channels in the other room via (an ethernet connected) Apple TV. Yes, the output of netstat -anL | grep 8089 remained 15/15/128 *.8089 after running curl -s localhost:8089/status - repeated runs of curl to localhost don't seem to increment it. HPING localhost (utun13 127.0.0.1): S set, 40 headers + 0 data bytesĢ56 packets tramitted, 0 packets received, 100% packet loss ![]() $ echo date sudo /opt/homebrew/Cellar/hping/3.20051105/sbin/hping3 -q -c 256 -S -p 8089 -faster localhost echo date netstat -anL | grep 8089 netstat -nt | grep 8089 | head -6 sleep 2 echo date netstat -anL | grep 8089 I was able to make those numbers go up on my own M1 mini using hping3, but I observe them resetting back to zero within a couple seconds. So your output is still sitting at 15/15/128? I wonder if the others here affected also are using Little Snitch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |