{"id":154,"date":"2012-12-10T16:34:03","date_gmt":"2012-12-10T12:34:03","guid":{"rendered":"http:\/\/port25.io\/?p=154"},"modified":"2013-10-23T15:52:11","modified_gmt":"2013-10-23T11:52:11","slug":"managing-network-interfaces-with-powershell-v3","status":"publish","type":"post","link":"https:\/\/rakhesh.com\/powershell\/managing-network-interfaces-with-powershell-v3\/","title":{"rendered":"Managing network interfaces with PowerShell v3"},"content":{"rendered":"

Update<\/strong>: Learnt from this StackOverflow post<\/a> that the cmdlets below are only available on PowerShell v3 running on Windows 8\/ Windows Server 2012 (and later). They are not available on PowerShell v3 running on Windows 7\/ Windows Server 2008. <\/p>\n

Windows Server 2012 comes with PowerShell v3 and that has the ability to manipulate the network interface from within PowerShell. Meaning you can view the IP address, set IP address, change name of the interface, and so on. I find that cool!<\/p>\n

I explored these new cmdlets by typing Get-Net<\/code> at the PowerShell prompt and pressing TAB<\/code>. This shows all the commands and I kept trying the ones I felt interested in and discovered new ones from reading the help pages.<\/p>\n

For starters, Get-NetIPInterface<\/code> shows you the available network interfaces. You can pass the cmdlet parameters to filter the results in terms of (say) showing only the interfaces that are connected or showing only the interfaces that are assigned an IP from DHCP.<\/p>\n

\"image.png\"<\/a><\/p>\n

To see the IP addresses, use the Get-NetIPAddress<\/code> cmdlet:<\/p>\n

\"image.png\"<\/a><\/p>\n

We can combine the two cmdlets. For instance, to find the IP addresses of the DHCP assigned interfaces one can pipe the two commands: Get-NetIPInterface \u2013Dhcp Enabled | Get-NetIPAddress<\/code><\/p>\n

\"image.png\"<\/a><\/p>\n

To change an interface settings such as enable\/ disable DHCP use the Set-NetIPInterface<\/code> cmdlet.<\/p>\n

To assign a new IP address use the New-NetIPAddress<\/code> cmdlet (this automatically disables DHCP on that interface if it\u2019s enabled). To change the property of an existing IP address (such as the subnet mask, for instance) use the Set-NetIPAddress<\/code> cmdlet. And To un-assign an IP address use the Remove-NetIPAddress<\/code> cmdlet.<\/p>\n

\"image.png\"<\/a><\/p>\n

\"image.png\"<\/a><\/p>\n

I find the Set-NetIPAddress<\/code> cmdlet slightly confusing. One would expect it to be able to set an IP address too, for instance, but it does not work that way. To add to the confusion this cmdlet too has switches similar to the New-NetIPAddress<\/code> cmdlet to specify an IP Address (the -IPAddress<\/code> switch) so you\u2019d think it\u2019s possible to set an IP address this way. But don\u2019t be fooled. All this \u2013IPAddress<\/code> switch does with the Set-NetIPAddress<\/code> cmdlet is to let you select interfaces matching that IP address.<\/p>\n

If you try and set an IP address using the Set-NetIPAddress<\/code> cmdlet you get an error:<\/p>\n

\"image.png\"<\/a><\/p>\n

The error message is obvious. You can see the cmdlet is trying to find interfaces matching the IP address you specify \u2013 and failing \u2013 rather than set that as the IP address of an interface.<\/p>\n

Moving on, I like to rename the network adapters in my VMs. That too is possible using PowerShell now. Rename-NetAdapter<\/code> is your friend!<\/p>\n

\"image.png\"<\/a><\/p>\n

I also like to disable some of my network adapters. You can do that too now through PowerShell using the Disable-NetAdapter<\/code> cmdlet.<\/p>\n

\"image.png\"<\/a><\/p>\n

Would have been handy if cmdlets such as Disable-NetAdapter<\/code> were a part of Set-NetAdapter<\/code> (via a switch).<\/p>\n

PowerShell is also now cool enough to fiddle with the bindings. So, for instance, if you want to disable IPv6 for one of your interfaces \u2013 possible now via PowerShell! Use Get-NetAdapterBinding<\/code> to see the available bindings (IPv4, IPv6, etc) and disable using Disable-NetAdapterBinding<\/code>.<\/p>\n

\"image.png\"<\/a><\/p>\n

Goes without saying \u2013 all these Disable-*<\/code> cmdlets have an Enable-*<\/code> counterpart too. So you can enable whatever you disable.<\/p>\n

This<\/a> TechNet topic gives a list of all the Network related cmdlets in PowerShell.<\/p>\n

When assigning a new IP address to an interface using New-NetIPAddress<\/code> you can pass a default gateway IP too via the \u2013DefaultGateway<\/code> switch. If you forget to do that, there’s no way to add a default gateway – perhaps using the Set-NetIPAddress<\/code> cmdlet as I was expecting. The only alternatives are to remove the IP address via the Remove-NetIPAddress<\/code> cmdlet and then re-add the IP address but this time specifying the default gateway; or use the New-NetRoute<\/code> cmdlet to manipulate the routing table directly.<\/p>\n

The Get-NetRoute<\/code> cmdlet can be used to view the existing routing table. And the New-NetRoute<\/code> can be used to add a new route. To make a route the default gateway set the destination prefix as 0.0.0.0\/0<\/code> (for IPv4) or ::\/0<\/code> (for IPv6). Examples below:<\/p>\n

\"image.png\"<\/a><\/p>\n

\"image.png\"<\/a><\/p>\n

\"image.png\"<\/a><\/p>\n

Lastly, there are cmdlets to configure the DNS resolvers. The Get-DnsClient<\/code> cmdlet shows you DNS configuration information for each interface. It doesn\u2019t show the resolver addresses; rather this cmdlet is about the DNS client itself and so shows information such as the DNS suffixes and the search list for these suffixes. The Get-DnsClientServerAddress<\/code> cmdlet does what it says \u2013 it shows you the resolver server address for each interface \u2013 and is probably what most of us will commonly use.<\/p>\n

\"image.png\"<\/a><\/p>\n

To set DNS resolves you can use the Set-DnsClientServerAddress<\/code> cmdlet. To specify multiple addresses put them in brackets with the entries comma separated and in double quotes. The double quotes are important because without them the addresses are ignored.<\/p>\n

\"image.png\"<\/a><\/p>\n

The same cmdlet can be used with a \u2013ResetServerAddresses<\/code> switch to remove the server addresses.<\/p>\n

\"image.png\"<\/a><\/p>\n

And that\u2019s more or less it. These cmdlets only touch the tip of the ice-berg, but I think these are the ones most of us will regularly use.<\/p>\n

Just to summarize here\u2019s a table with all the cmdlets:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Get-NetIPInterface<\/code><\/td>\nShows you the available network interfaces. Can pass parameters to filter the results (e.g. only the DHCP assigned ones).<\/td>\n<\/tr>\n
Get-NetIPAddress<\/code><\/td>\nShows you the IP addresses. Again, can filter using parameters.<\/td>\n<\/tr>\n
Set-NetIPInterface<\/code><\/td>\nChange an interface settings. Such as turn off\/ on DHCP, IPv6 neighbor discovery settings, router settings (advertising, packet forwarding), and Wake on LAN.<\/td>\n<\/tr>\n
New-NetIPAddress<\/code><\/td>\nAssign a new IP address to an interface. Use the \u2013DefaultGateway switch to specify the default gateway.<\/td>\n<\/tr>\n
Remove-NetIPAddress<\/code><\/td>\nRemove an assigned IP address from an interface.<\/td>\n<\/tr>\n
Set-NetIPAddress<\/code><\/td>\nChange IP address properties. For instance: change the subnet mask.<\/td>\n<\/tr>\n
Rename-NetAdapter<\/code><\/td>\nRename a network adapter.<\/td>\n<\/tr>\n
Disable-NetAdapter<\/code><\/td>\nDisable a network adapter. To enable use Enable-NetAdapter<\/code>.<\/td>\n<\/tr>\n
Get-NetAdapterBinding<\/code><\/td>\nView the network adapter bindings. Such as IPv4, IPv6, Client for Microsoft Networks.<\/td>\n<\/tr>\n
Disable-NetAdapterBinding<\/code><\/td>\nDisable network adapter bindings. To enable use Enable-NetAdapterBinding<\/code>.<\/td>\n<\/tr>\n
Get-NetRoute<\/code><\/td>\nView the routing table.<\/td>\n<\/tr>\n
New-NetRoute<\/code><\/td>\nAdd an entry to the routing table. Use destination prefix as 0.0.0.0\/0<\/code> (for IPv4) or ::\/0<\/code> (for IPv6) to set default gateway.<\/td>\n<\/tr>\n
Remove-NetRoute<\/code><\/td>\nRemove a routing table entry.<\/td>\n<\/tr>\n
Get-DnsClient<\/code><\/td>\nView the DNS client settings. Such as DNS suffix, search list, and so on.<\/td>\n<\/tr>\n
Get-DnsClientServerAddress<\/code><\/td>\nView the DNS client server addresses.<\/td>\n<\/tr>\n
Set-DnsClient<\/code><\/td>\nModify the DNS client settings.<\/td>\n<\/tr>\n
Set-DnsClientServerAddress<\/code><\/td>\nAdd DNS client server addresses. Put multiple address as (\u201cx.x.x.x\u201d, \u201cx.x.x.x.\u201d, \u2026\")<\/code>. Use the -ResetServerAddresses<\/code> switch to remove the server addresses<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Now that\u2019s a good reference for me too to check whenever I forget these commands!<\/p>\n","protected":false},"excerpt":{"rendered":"

Update: Learnt from this StackOverflow post that the cmdlets below are only available on PowerShell v3 running on Windows 8\/ Windows Server 2012 (and later). They are not available on PowerShell v3 running on Windows 7\/ Windows Server 2008. Windows Server 2012 comes with PowerShell v3 and that has the ability to manipulate the network … Continue reading Managing network interfaces with PowerShell v3<\/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":[2],"tags":[27,87,35,50],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/154"}],"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=154"}],"version-history":[{"count":0,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/154\/revisions"}],"wp:attachment":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/media?parent=154"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/categories?post=154"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/tags?post=154"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}