Matt Organ
@Slater450413@infosec.exchange
Just another Linux hacker Constantly struggling to hide my affection of hacker subculture and memes behind the veil of corporate professionalism. Father of 2, master of none. Interested in #MotorSport, #F1, #VintageCars, #VideoGames, #InfoSec, #OpenHAB, #HomeAutomation, #Linux, #OSS. Thoughts and opinions are my own. I am not a bot (that I'm aware of).
infosec.exchange
Anyone else notice or have issues where ping.exe on Windows 10/11 behavior appears to be buggy these days.
If I ping an address known to be offline.
On both Linux and Unix, I correctly get 100% packet loss.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
From 192.168.0.101 icmp_seq=1 Destination Host Unreachable
--- 192.168.0.2 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
On Windows I get an utterly broken 0% packet loss
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.100: Destination host unreachable.
Ping statistics for 192.168.0.2:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
The impact is that you then can't accurately measure the commands exitstatus/errorlevel when used in a script.
#infosec #Windows10 #Windows11 #networking #Linux
