Re:Should I Block ICMP?
by tredre3 on Wednesday January 11, 2023 @08:43AM
(#34338302)
> Alternatively, the most barebones version, useful for inside a container where all you have is a shell and the kernel:
> cat > /dev/tcp/www.google.com/443
I was unfamiliar with this device so I googled a bit. This isn't a real file/device, it's a bash-ism when built with --enable-net-redirections (apparently disabled in debian-based distros [1]).
That's too bad, would have been cool to have such easy access to sockets anywhere using fopen().
Re:Should I Block ICMP?
by jonas-w on Wednesday January 11, 2023 @12:21AM
(#34335279)
If it is a device in your local network, arp-scanning is also very useful. IIRC e.g. windows or ios devices won't respond to icmp pings but to arp "pings".
As a follow-up to a ping fail, I check to see if a known port is open using nmap.
gist: https://gist.github.com/veganjay/6b902c478bda429187f39e53a5b...
> cat > /dev/tcp/www.google.com/443
I was unfamiliar with this device so I googled a bit. This isn't a real file/device, it's a bash-ism when built with --enable-net-redirections (apparently disabled in debian-based distros [1]).
That's too bad, would have been cool to have such easy access to sockets anywhere using fopen().
1. https://www.oreilly.com/library/view/bash-cookbook/059652678...