2016-09-22 12:43:57 +00:00
|
|
|
---
|
|
|
|
title: About the interface Resource
|
2018-02-16 00:28:15 +00:00
|
|
|
platform: os
|
2016-09-22 12:43:57 +00:00
|
|
|
---
|
|
|
|
|
|
|
|
# interface
|
|
|
|
|
2019-04-26 18:24:29 +00:00
|
|
|
Use the `interface` Chef InSpec audit resource to test basic network adapter properties, such as name, status, and link speed (in MB/sec).
|
2016-09-22 12:43:57 +00:00
|
|
|
|
|
|
|
* On Linux platforms, `/sys/class/net/#{iface}` is used as source
|
|
|
|
* On the Windows platform, the `Get-NetAdapter` cmdlet is used as source
|
|
|
|
|
2017-10-03 21:35:10 +00:00
|
|
|
<br>
|
|
|
|
|
2018-08-09 12:34:49 +00:00
|
|
|
## Availability
|
|
|
|
|
|
|
|
### Installation
|
|
|
|
|
2019-04-26 18:24:29 +00:00
|
|
|
This resource is distributed along with Chef InSpec itself. You can use it automatically.
|
2018-08-09 12:34:49 +00:00
|
|
|
|
|
|
|
### Version
|
|
|
|
|
|
|
|
This resource first became available in v1.0.0 of InSpec.
|
|
|
|
|
2016-09-27 19:03:23 +00:00
|
|
|
## Syntax
|
2016-09-22 12:43:57 +00:00
|
|
|
|
|
|
|
An `interface` resource block declares network interface properties to be tested:
|
|
|
|
|
2017-05-18 19:28:19 +00:00
|
|
|
describe interface('eth0') do
|
2016-09-22 12:43:57 +00:00
|
|
|
it { should be_up }
|
|
|
|
its('speed') { should eq 1000 }
|
|
|
|
its('name') { should eq eth0 }
|
|
|
|
end
|
|
|
|
|
2017-10-03 21:35:10 +00:00
|
|
|
<br>
|
2018-02-16 02:34:11 +00:00
|
|
|
|
2018-02-15 14:33:22 +00:00
|
|
|
## Properties
|
2016-09-22 12:43:57 +00:00
|
|
|
|
2018-02-08 21:43:50 +00:00
|
|
|
`name`, `speed`
|
2018-02-16 02:34:11 +00:00
|
|
|
|
2018-02-08 21:43:50 +00:00
|
|
|
<br>
|
2016-09-22 12:43:57 +00:00
|
|
|
|
2018-02-08 21:43:50 +00:00
|
|
|
## Resource Property Examples
|
2016-09-22 12:43:57 +00:00
|
|
|
|
2016-09-27 19:03:23 +00:00
|
|
|
### name
|
2016-09-22 12:43:57 +00:00
|
|
|
|
2019-03-18 22:53:51 +00:00
|
|
|
The `name` property tests if the named network interface exists:
|
2016-09-22 12:43:57 +00:00
|
|
|
|
|
|
|
its('name') { should eq eth0 }
|
|
|
|
|
2016-09-27 19:03:23 +00:00
|
|
|
### speed
|
2016-09-22 12:43:57 +00:00
|
|
|
|
2019-03-18 22:53:51 +00:00
|
|
|
The `speed` property tests the speed of the network interface, in MB/sec:
|
2016-09-22 12:43:57 +00:00
|
|
|
|
|
|
|
its('speed') { should eq 1000 }
|
2018-02-08 21:43:50 +00:00
|
|
|
|
2019-03-18 22:53:51 +00:00
|
|
|
### ipv4_addresses
|
|
|
|
|
|
|
|
The `ipv4_addresses` property tests if the specified address exists on the named network interface:
|
|
|
|
|
|
|
|
its('ipv4_addresses') { should include '127.0.0.1' }
|
|
|
|
|
|
|
|
### ipv4_addresses_netmask
|
|
|
|
|
|
|
|
The `ipv4_addresses_netmask` property tests if the specified address and netmask exists on the named network interface:
|
|
|
|
|
|
|
|
its('ipv4_addresses_netmask') { should include '127.0.0.1/255.0.0.0' }
|
|
|
|
|
|
|
|
### ipv6_addresses
|
|
|
|
|
|
|
|
The `ipv6_addresses` property tests if the specified address exists on the named network interface:
|
|
|
|
|
|
|
|
its('ipv6_addresses') { should include '::1' }
|
|
|
|
|
|
|
|
### ipv4_cidrs
|
|
|
|
|
|
|
|
The `ipv4_cidrs` property tests if the specified address and netmask combination exists on the named network interface:
|
|
|
|
|
|
|
|
its('ipv4_cidrs') { should include '127.0.0.1/8' }
|
|
|
|
|
|
|
|
### ipv6_cidrs
|
|
|
|
|
|
|
|
The `ipv6_cidrs` property tests if the specified address and netmask combination exists on the named network interface:
|
|
|
|
|
|
|
|
its('ipv6_cidrs') { should include '::1/128' }
|
|
|
|
|
2018-02-16 00:28:15 +00:00
|
|
|
<br>
|
2018-02-08 21:43:50 +00:00
|
|
|
|
|
|
|
## Matchers
|
|
|
|
|
2018-02-16 03:07:18 +00:00
|
|
|
For a full list of available matchers, please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
|
2018-02-08 21:43:50 +00:00
|
|
|
|
|
|
|
### be_up
|
|
|
|
|
|
|
|
The `be_up` matcher tests if the network interface is available:
|
|
|
|
|
|
|
|
it { should be_up }
|
|
|
|
|
2019-03-18 22:53:51 +00:00
|
|
|
### have_an_ipv4_address
|
|
|
|
|
|
|
|
The `have_an_ipv4_address` matcher tests if the network interface has any IPv4 addresses assigned:
|
|
|
|
|
|
|
|
it { should have_an_ipv4_address }
|
|
|
|
|
|
|
|
### have_an_ipv6_address
|
|
|
|
|
|
|
|
The `have_an_ipv6_address` matcher tests if the network interface has any IPv6 addresses assigned:
|
|
|
|
|
|
|
|
it { should have_an_ipv6_address }
|