 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
 | The contents of the Router metrics page were merged into Metrics (networking) on 2014-09-10. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. |
Best possible?
editArticle states:
- The routing table stores only the best possible routes
I'm not an expert on the subject, but this seems like a radical overgeneralization to me. I see no reason a local network routing table shouldn't have overlapping entries for different networks (e.g. 192.168.1.0/24 and 192.168.0.0/16) with different metrics in order to determine what happens for addresses that could be served by either route. But such a routing table has two possible routes for (say) 192.168.1.1, one of which is not the best possible route. JulesH (talk) 09:34, 23 May 2012 (UTC)
- The routing table stores whatever routes are put into it by administrators and routing protocols. The router tries to choose the best possible route from among the choices available in the routing table. I have fixed this. ~KvnG 16:04, 10 September 2014 (UTC)
Example of the Best possible routes
edit- It would be suitable example for the actual network routing table.
- 1) overlapping entries for different networks (e.g. 192.168.1.0/24 and 192.168.0.0/16) with different metrics can be utilised for multiple paths for the each network
- 2) The Multiple path can be used for 1:n paths for redundancy( 1 is the best active route and n paths would be redundnacy)
- 3) In other case, n paths can be utilised for load balancing. Goodtiming8871 (talk) 04:50, 8 April 2014 (UTC)