I had no idea that ping was that fucking complicated.
Biff has never tried to stab me with a steak knife. She must not love me!
She said she'll stab me with a knife if I really want her to but she'd rather not. She's remarkably sane. It's actually quite nice to be married to a chick that's not insane.
From what I gather on the link it is basically an echo function of the ICMP which is encapsulated somehow by the IT datagram, what ever the hell that is.
I will just think of it as an echo off a targeted server
I'm just not gonna think about it. I use ping fairly often, but I don't really need to know the details. The idea that it's its own protocol is all I need to know.
But, those are the kinds of questions I look up and the kind of questions I answer - except not that one. I did not know that about ping. I always thought it was just like every other packet (complete with syn and ack) on port 7. I had no idea it was that complex, which (I admit) is kinda why I was looking it up.
Some dude can connect every other way - except ping. I suspect they can't telnet either, but they haven't responded. It's 95% likely to be a hosts issue and the more recent Solaris deals with the hosts in two places instead of just one. Ping (and telnet) are on one and that one probably is misconfigured - but I wanted to check how ping worked first.
Maybe you should amend the Solaris to deal with the hosts in only one place to avoid this issue in the future, or just correctly configure the ping and telnet host
(post is archived)