|
|
| |
Date Posted: 2005-02-01 06:21 |
|
can we include another field in the routing table, let me call "client associated" , to know which client is connected to which router.
I guess clients just send and receive messages through their associated routers without having any clue about the network topology. If this is the case dont we need to have some kind of a reference of the remote client somewhere.
As of now the routing table is only showing what router to take(as EXIT) depending on the end router.
For Example , the test case wants Client 1 to send a segment to client 3 (seg size = 500 bytes)
So in the above case Client 1 sends 500B to its router (as per the network, it sends to router A. How in the world will router A know where to forward the segment as there are two router connections to it - router C and router D. So somehow all the routers should be aware of all the clients and their routers in the network.
Are we supposed to hardcode every node ????
Does anyone have a better idea regarding this ????
I hope, I am not interpreting this wrong !!!
|
| |
|