{"id":2898,"date":"2016-04-10T09:34:49","date_gmt":"2016-04-10T05:34:49","guid":{"rendered":"https:\/\/rakhesh.com\/?p=2898"},"modified":"2016-04-10T11:38:30","modified_gmt":"2016-04-10T07:38:30","slug":"automatic-metric-and-windows-routing","status":"publish","type":"post","link":"https:\/\/rakhesh.com\/windows\/automatic-metric-and-windows-routing\/","title":{"rendered":"Automatic Metric and Windows routing"},"content":{"rendered":"

IP routing involves metrics. This is the cost of each route. If there are multiple routes to a destination then the route with lowest metric\/ cost is chosen.<\/p>\n

In the context of Windows OS there are two metrics that come into play.<\/p>\n

\"automatic<\/p>\n

One is the metric of the interface\/ NIC itself (that’s the “Automatic metric” checkbox above). By default its set to automatic, and this determines the cost of using that interface itself. For example if both your wireless and wired connection can access the Internet, which one should the machine choose? The interface metric is used to make this decision. You can assign a value to this metric if you want to force a decision.<\/p>\n

Each interface can have multiple gateways to various networks it knows of. Could be that it has more than one gateway to the same network – say, your wired connection can connect to the Internet from two different routers on your network, which one should it choose? Here’s where the gateway metric comes into play (circled in the screenshot above). By default when you add a gateway its metric is set to automatic, but here too you can assign a value.<\/p>\n

\"gateway<\/p>\n

So far so good. Now how does all this come into play together?<\/p>\n

The first thing to know is that gateway metrics have a value of 256 by default<\/strong> (when set to “Automatic metric”). So if you have more than one gateway to a particular destination, and the metric is set to automatic, then by default both gateways have a metric value of 256 and hence equal preference. Remember that.<\/p>\n

The next thing to know is that interface metrics have a value ranging from 5 to 50<\/strong> (when set to “Automatic metric”) based on the speed of the interface. Lower numbers are better than higher numbers. See this KB article<\/a> for the numbers, here’s a screenshot from that article.<\/p>\n

\"interface<\/p>\n

So if you have two wired connections for instance, one of speed 1 GB and other of speed 10 GB, then the 1 GB interface has a metric of 10 and the 10 GB interface has a metric of 5 – thus making the latter preferred.<\/p>\n

To view the interface & gateway metrics assigned to your interfaces use the netsh interface ip show address<\/code> command:<\/p>\n

C:\\WINDOWS\\system32>netsh interface ip show address\r\n\r\nConfiguration for interface \"Local Area Connection* 2\"\r\n    DHCP enabled:                         Yes\r\n    InterfaceMetric:                      5\r\n\r\nConfiguration for interface \"Ethernet\"\r\n    DHCP enabled:                         Yes\r\n    IP Address:                           10.136.20.16\r\n    Subnet Prefix:                        10.136.20.0\/24 (mask 255.255.255.0)\r\n    InterfaceMetric:                      10\r\n\r\nConfiguration for interface \"Ethernet 2\"\r\n    DHCP enabled:                         Yes\r\n    IP Address:                           10.171.1.6\r\n    Subnet Prefix:                        10.171.1.4\/30 (mask 255.255.255.252)\r\n\u00a0\u00a0\u00a0 Gateway Metric:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5\r\n    InterfaceMetric:                      20<\/pre>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
IP routing involves metrics. This is the cost of each route. If there are multiple routes to a destination then the route with lowest metric\/ cost is chosen. In the context of Windows OS there are two metrics that come into play. One is the metric of the interface\/ NIC itself (that’s the “Automatic metric” … Continue reading Automatic Metric and Windows routing<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[85],"tags":[604,27,603],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/2898"}],"collection":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/comments?post=2898"}],"version-history":[{"count":0,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/2898\/revisions"}],"wp:attachment":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/media?parent=2898"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/categories?post=2898"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/tags?post=2898"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}