Ethereal-users: [Ethereal-users] How does ethereal identify tftp transfer

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Nitin Shrivastav <n_shrivastav78@xxxxxxxxx>
Date: Mon, 6 Mar 2006 07:49:14 -0800 (PST)
Hello,

I am trying to understand how does ethereal identifies
tftp data packets. I am running ethereal on the server
machine. When i initiate the tftp transfer from
clinet, my client uses a local udp port number 'x' and
dest port is well defined tftp port 69.

Now server responds back with a local udp source port
'y'destined to port 'x'. Subsequently, all the data
transfer happens using these two ports. On capturing
the packets in ethereal, it correctly identifies all
the data packets as belonging to a tftp connection.

The question is how does ethereal identifies this.
Does it mark the original client port number 'x' in
the first request packet to identify all the
subsequent packets with source port 'x' as belonging
to tftp..?

Thanks for your help,
Nitin


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com