Eagor's Forums » CEN6520 - Project 2 » Do we want the Client to router communication, router to client communication?

Author

Topic: Do we want the Client to router communication, router to client communication?

Steven Eagen Posts: 14

Date Posted: 2005-01-30 23:03 David Mauk asked: Do we want the Client to router communication, router to client communication? (As I understand it we should in the end perhaps be able to take my client and run it will any of your routers.) Could header be the same as router to router? If so then client needs to know about destinations (it already has its IP as the source)).

jesse_sweetland Posts: 14

Date Posted: 2005-01-31 06:57 There needs to be some kind of header between the client and the Router so that the router knows where to send the segment. It would be simplest to make client->router communication the same as router->router communication; i.e. use the same header. The only difference is that the MTU between a client and a router is theoretically unlimited (65521B in practice). If you had a segment of 500B, the client would send a "fragement" of 514B (500B data, 14B header) to the router.

David Mauk Posts: 17

Date Posted: 2005-02-03 00:33 I agree your proposal sounds good thus we shall do unless someone else has a good agrument against it.

jesse_sweetland Posts: 14

Date Posted: 2005-02-08 19:26 Router and client are on same machine so must operate on distinct ports. Recommend routerPort, clientPort as command line args to both router and client apps. See post in "What port is your router using" for details.