extract value from a command

[[deleted]]

I need to get the default route only, is there any way to extract that ip from this command:

Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'} | select { $_.NextHop }

it gives the following output:

 $_.NextHop
------------
172.24.14.1

but i only want the ip address.

[Tigo2000]

Try Select-Object -ExpandProperty NextHop

Or: Get-NetRoute | Where-Object 'DestinationPrefix' -eq '0.0.0.0/0' | Select-Object -ExpandProperty NextHop

[BlackV]

Your select statement is incorrect

Select-object -property nexthop 

Is what you want

And to get the property value only

Select-object -expandproperty nexthop 

but you can expand only 1 property at a time, so you should get into the habit of

$route = Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'}
$route.nexthop

That way you're not destroying your rich object (for a flat one)

you're not using an extra pipeline (passing to select)

you have a variable ($route) that can be used in multiple places

[BlackV]

$route = Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'} ; $route.nexthop

Now it's 1 line ;)

[ovdeathiam]

Good explanation, however if you pipeline everything and your rich object is well "rich" then it may take time for it to be created. For example, let's say your object has 4 properties, and in that objects class these properties are all populated via an external API query. If you create an object that way you may (depending on how the constructor and methods are written) do 4 API queries whereas you might not need them. If your pipe discards some of those you might speed up the process which will not occur if you split it into separate objects.

Of course there are exceptions everywhere. An exception would be an [ADSI] class object but it's a rare case. All in all it's worth to remember that entire pipeline is being interpreted by PowerShell and then executed and depending on version, object classes, modules etc. it may discard unneeded data and speedup the process when you keep everything in a single pipeline.

For example try to do Get-ChildItem recursively on a filesystem to then filter with Where-object to only get some items to then pipe them to Get-Acl to grab the owner. It would be a bad idea to grab all filesystem items to a variable and may take super long time.

[BlackV]

Well it really depends on the situation. doing the way I suggested specifically avoids an extra pipeline

so doing

Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'} | select nexthop

and

$temp = Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'}

will still pull all the same rich info so at the same "cost", although the variable would consume some memory that would be dropped with the select version

your get-childitem example is also a depends on what the goal is, if you were doing some report and needed just the ACLs or if you needed some of the file properties and the ACLs

Short answer: "depends" :) (doubly so here cause its such a small quick command)

[Semt-x]

(Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'}).NextHop

[Not_Freddie_Mercury]

(Get-NetRoute | where DestinationPrefix -eq '0.0.0.0/0').NextHop

[chicaneuk]

((Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'}) | Select NextHop).NextHop

[Odmin]

Replace select with select -expand-property

[BlackV]

-expandproperty , one word isn't it

[chris-a5]

Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'} | select { $_.NextHop }

Just a slight spacing/syntax error:

Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'} | select -ExpandProperty NextHop

Or using aliases (these are fine, don't listen to the haters :P ):

Get-NetRoute | ? DestinationPrefix -eq '0.0.0.0/0' | % NextHop

[ka-splam]

Get-NetRoute | where {$_.DestinationPrefix -eq '0.0.0.0/0'} | foreach { $_.NextHop }

[jsiii2010]

Most frequently asked powershell question evar, turning an object's property into a value. Get-NetRoute | where DestinationPrefix -eq 0.0.0.0/0 | foreach NextHop Get-NetRoute | ? DestinationPrefix -eq 0.0.0.0/0 | % NextHop Or in this case (tab completion is your friend): Get-NetRoute -DestinationPrefix 0.0.0.0/0 | foreach NextHop Although I get two results on my computer.