address contained in each packet's header? If so, where?
> packets from joe to you would look like:
>
> 98-00-12-45-78-45 / 00-40-80-12-34-56 / 129.129.0.15 / 204.125.16.99 / 20
>
> while packets from fred to you look like:
>
> 98-00-12-45-78-45 / 00-40-80-99-88-77 / 129.129.0.15 / 18.0.1.200 / 20
You didn't say what these five numbers are. What are they?
> > I'm really confused now. I thought the FTP server (the parent process)
> > was listening on port 20. How does the TCP stack know to give the
> > packet that comes in on port 20 to the child process? In the header,
> > the IP address is the same and both carry the same port number, 20.
> > There's no other identification in the header that the TCP stack can
> use
> > to properly steer the packet.
>
> the packets DO have different addresses for the target
Which number is the target value? And which layer contains the table
that has the matching target value so the packet can be properly steered
to the target?
Thanks.
- Peter Skye
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 02 |
October |
1998 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.