1
/ \
2 - 4 - 5 - 6
\ /
3
Node |
Neighbors |
Routing table |
1 |
2, 4 |
* 2 |
2 |
1, 3, 4 |
* 3 |
3 |
2, 4 |
* 4 |
4 |
1, 2, 3, 5 |
* 1 |
5 |
4, 6 |
* 4 |
6 |
5 |
* 5 |
In parts a - f, give the nodes in order that deal with a message from the given sender to the receiver.
2 5
| \ / |
| 3 - 4 |
| / \ |
1 6
Node |
Neighbors |
Routing table |
1 |
2, 3 |
* 2 |
2 |
1, 3 |
* 3 |
3 |
1, 2, 4 |
* 1 |
4 |
3, 5, 6 |
* 5 |
5 |
4, 6 |
* 6 |
6 |
4, 5 |
* 4 |
In parts a - b, give the nodes in order that deal with a message from the given sender to the receiver.
----------Answers for the network given in the sample problems:
4) If you delete the re-transmitted packet, the sender will again wait
for a timeout, at which point it will yet again resend the same
packet. Thus, the protocol for a re-transmitted packet is really
identical as to the protocol used for the originally transmitted packet.
5) Deleting the ACK or NAK packets has the same effect as deleting the
originally transmitted packets. Consider things from 0's point of
view. Whether the original packet got deleted, or the ACK got deleted,
0 has not heard anything in response to the packet it originally sent.
Since it is not sure that the packet was received, it will resend the packet.
0 simply has no way to differentiate between a lost packet and a lost ACK.
Lab 15, Exercise 4
----------
3) 159.121.2.13 will send messages to 138.92.0.5.
However these nodes are not directly connected.
4) If not connected, 159.121.66.98 sends outgoing (or forwarded) messages
to its neighbor, 37.61.25.46
5) Will vary somewhat. In this applet, the "forwarded" count actually
includes those messages which originate with that node. For this
particular node, you will find that it receives zero packets, and
the forwarded count is roughly twice that of the number it sends.
No packets should be dropped.
6) Packets are sent from 128.92.6.17 to 159.121.66.98
Packets are sent from 159.121.2.13 to 138.92.0.5
7) Node 37.61.25.46 does not send or receive messages. It will have
only forwarded messages.