Re: Why Ping Requires RAW Sockets?
Roy Smith <roy@panix.com> writes:
>One of my favorite interview questions for somebody who claims "expert
>knowledge of TCP/IP" or some such silliness on their resume is to ask them
>to sketch out both sides of a trivial TCP client-server application on the
>whiteboard. It usually takes a few hints, but eventually they converge on
>something like socket/bind/listen/accept/read on one side and
>socket/connect/write on the other. Then I draw them two timelines and ask
>them to show me all the packets that go on the wire, starting with the TCP
>three-way handshake. The good ones usually do that OK too. Then I ask
>them to correlate each system call in the application skeletons they just
>wrote with each packet that went out on the wire. That's where the fun
>usually begins.
But that's a trick question! (A number of packets does not
correlate to system calls)
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
|