what is optimized link state routing protocol?
139181
confirmed...it is used to overcome slow route convergence
137074
the book published by Andrew S. Tanenbaum named: Computer Networks, Fourth Edition  contains in a very detailed level a C implementation of sliding windows operations.\n\nIn my opinion, the best available
1136732
Ad-Hoc Mode is a way for wireless devices to communicate directly with each other without using an access point.\n\nInfrastructure Mode is a way wireless devices communicate with each other through an access point.
71965
MPLS is used mostly in telcom. On the outside the core routers to tag packets that are heading for the busy internal core with a special tag. The interal core routers don't have to dive deep into the packet to find out which way to route it or how to treat the packet QoS wise. This way you have the smaller outside routers with less traffic make it easier for busier larger routers to make routing choices.
981769
A wireless router xxxxx
29437
I am not sure if I got the correct meaning of your question, but I guess the answer, if you are asking the number of possible paths in such a network, is 2*n*(n-1) in the case of one-way paths and n*(n-1) when talking of two-way paths.\n\nThe reason is that, in the one-way case, each of the n nodes may be linked to any of the resting (n-1) nodes in one of the two possible ways, making 2*n*(n-1). In the case of two way paths, only one path linking each of the nodes exists thus the n*(n-1) number.\n\nYou may be asking the number of possible networks, which would be a more interesting problem. If this is so, please ask another question.
362876
easy, Use traffic shaping.  You create a access list with the traffic you want to limit.  turn on the traffic shaping command and refrence the acl.\n\nI warn you though.  If this is router is under heavy load your processor may not handle it.\n\nThats what i did.  cisco has many docs on traffic shaping and example configs.
1087540
Transmission Control Protocol - Internet Protocol
120350
TCP-F: TCP Feedback [55] is a feedback based approach to handle route failures in MANETs. This approach\nallows the TCP sender to distinguish between losses due to routes failure and those due to network congestion.\nThis is done as follows. When routing agent of a node detects the disruption of a route, it explicitly sends a Route\nFailure Notification (RFN) packet to the source. On receiving the RFN, the source goes into a snooze state. TCP\nsender in snooze state will stop sending packets, and will freeze all its variables, such as timers and congestion\nwindow size. The TCP sender remains in this snooze state until it is notified of the restoration of the route through\nRoute Re-establishment Notification (RRN) packet. On receiving the RRN, the TCP sender will leave the snooze\nstate and will resume transmission based on the previous sender window and timeout values. To avoid blocking\nscenario in the snooze state, the TCP sender, on receiving RFN, triggers a route failure timer. When this timer\nexpires the congestion control algorithm is invoked normally.\n\n\nRoute reconstruction (RR) detection) RRN packet resumes TCP to normal state\n---------\nObject RRN \n(Transaction) The relative record number of the record involved in the conflict\n-----------\n1. TCP-F\nIn the mobile ad hoc networks, topology may change rapidly due to\nthe movement of mobile hosts (MH). The frequent topology changes\nresult in sudden packet losses and delays. TCP misinterprets such\nlosses as congestion and invokes congestion, leading to unnecessary\nretransmission and loss of throughput. To overcome this problem,\nTCP-F (TCP-Feedback) [20] was proposed so that the sender can distinguish\nbetween route failure and network congestion. In this scheme,\nthe sender is forced to stop transmission without reducing window size\nupon route failure. As soon as the connection is reestablished, fast retransmission\nis enabled.\nTCP-F relies on the network layer at an intermediate node to detect\nthe route failure due to the mobility of its downstream neighbor along\nthe route. A sender can be in an active state or a snooze state. In the\nactive state, transport layer is controlled by the normal TCP. As soon\nas an intermediate node detects a broken route, it explicitly sends a\nroute failure notification (RFN) packet to the sender and records this\nevent. Upon reception of the RFN, the sender goes into the snooze\nstate, in which the sender completely stops sending further packets,\nand freezes all of its timers and the values of state variables such as\nRTO and congestion window size. Meanwhile, all upstream intermediate\nnodes that receive the RFN invalidate the particular route to avoid\nfurther packet losses. The sender remains in the snooze state until it is\nnotified of the restoration of the route through a route reestablishment\nnotification (RRN) packet from an intermediate node. Then it resumes\nthe transmission from the frozen state. The state machine of TCP-F
745362
A router is a computer networking device that forwards data packets across a network toward their destinations, through a process known as routing. Routing occurs at Layer 3 (the network layer i.e. Internet Protocol (IP)) of the OSI seven-layer protocol stack.\nclick here:http://en.wikipedia.org/wiki/Router\n\nGateway has several meanings. It may often share meanings with the term gate.\nclick here:http://en.wikipedia.org/wiki/Gateway
1093966
Organizing the different legs of a network
311912
http://www.howstuffworks.com/router.htm
118896
Well Router usally solve collisons.
336219
If you are refering to "traceroute", then yes, it\nis part of the base OS:\n\n$ which traceroute\n/usr/sbin/traceroute\n\n[Just so we're on the same page, this is the utility that\nuses ICMP to discover the route (and latencies) that\na packet would take from one location on the net to\nanother.]
890951
http://en.wikipedia.org/wiki/Routing
714063
buy a router\n\nA router (IPA pronunciation: [raʊtɚ] or [rutə(ɚ)]) is a computer networking device that forwards data packets across a network toward their destinations, through a process known as routing. Routing occurs at Layer 3 (the network layer i.e. Internet Protocol (IP)) of the OSI seven-layer protocol stack.\n\nA router acts as a junction between two or more networks to transfer data packets among them. A router is different from a switch. A switch connects devices to form a local area network (LAN).\n\n\n\nhttp://en.wikipedia.org/wiki/Router
1096655
The 'traceroute' program/utility uses the IP header  field called 'TTL' (or Time To Live) to illustrate the route a packet takes across a network en route to a given destination. As a packets traverses each hop along a route, the TTL value is decrimented until the packet reaches its destination. The traceroute program also measures latency to each hop along that route.\n\nThe program typically sends 3 UDP (in some versions it's ICMP) packets with an initial TTL value of 0 to a destination. However, when the packets hit the gateway node, that machine notes the TTL value is '0' and knows to return the packet back to the source. The program notes where the packet then came from and the elapsed time (latency). Again, the program sends another set of packets, this time with a TTL of 1. The gateway node receives the packet, decriments the TTL and forwards it to the next hop along the route. At hop #2, the packet now has a TTL of 0. The traceroute program increments the TTL value each iterration until the packet reaches the destination noce. Once reached, the output shows all the nodes along the route and the latency to each.\n\nIt's important to note that most Internet connections traverse asymmetric routes. That's to say that the route the packet took from the source to the destination is not necessarilly the route the packet will take on the way back. Tracroute only shows you the route in one direction. The only true way to get an idea of the path a packet takes between nodes A and B on the Internet is to view traceroute output from A to B as well as from B to A.