@burakkucat That's an error message from the *nix ping command ? Never knew that, that’s exactly why I’m glad that I asked the question.
I wonder if that is an explicit check by the ping command’s own app code itself then? As opposed to some error coming back from lower layers. So I need to write a C program to whack a udp message off to say
10.0.0.0 and one to
81.187.147.192 (/26) which is a
(base + 0) ≠ .0 example.
I wonder if ping for windows also does the same thing?
So one certain reason already is that
- it might trigger misbehaving by certain tools on other machines
Out of devilment, I have forced the Ipv4 address of the current ios box to be .192 which is a
(base + 0) ≠ .0 example on this particular subnet, and the subnet mask is still correct at /26. Scanned the LAN, browsed the internet no problems as yet, nor any expected. To be fair, how would the internet even know in this
(base + 0) ≠ .0 case. I could use an ipv6
::0 source address as an evil test.