Policy
The following scenarios show how to configure different
traffic policies
. Policies can be used to manage and
classify network packets. traffic selectors
can be
configured to filter packets based on certain fields.
Test Policy Actions
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). Different traffic actions are
configured to accept, drop or limit incoming traffic.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 action accept set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.576 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.576/0.576/0.576/0.000 ms
Step 4: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 action accept set traffic policy POLICY_IN rule 1 action drop
Step 5: Expect a failure in the following command:
Initiate a udp connection from DUT1
to DUT0
and try to send some messages between both endpoints
admin@DUT0$ monitor test connection server 8080 udp admin@DUT1$ monitor test connection client 10.0.0.1 8080 udp
Step 6: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 action drop set traffic policy POLICY_IN rule 1 action rate-limit 10
Step 7: Initiate a bandwidth test from DUT1
to DUT0
admin@DUT0$ monitor test performance server port 5001 admin@DUT1$ monitor test performance client 10.0.0.1 duration 5 port 5001 parallel 1Expect this output in
DUT1
:Connecting to host 10.0.0.1, port 5001 [ 5] local 10.0.0.2 port 38048 connected to 10.0.0.1 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 3.99 MBytes 33.5 Mbits/sec 392 17.0 KBytes [ 5] 1.00-2.00 sec 1.24 MBytes 10.4 Mbits/sec 118 22.6 KBytes [ 5] 2.00-3.00 sec 700 KBytes 5.73 Mbits/sec 110 15.6 KBytes [ 5] 3.00-4.00 sec 1.24 MBytes 10.4 Mbits/sec 129 28.3 KBytes [ 5] 4.00-5.00 sec 1.30 MBytes 10.9 Mbits/sec 113 5.66 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 8.47 MBytes 14.2 Mbits/sec 862 sender [ 5] 0.00-5.00 sec 6.94 MBytes 11.6 Mbits/sec receiver iperf Done.
Note
Previous test should show a very low bandwidth rate.
Test Policy Copy
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). Different copy
actions are
configured to store the ToS value in the conntrack mark
and extra conntrack mark
fields.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 copy tos connmark set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 tos 12 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.668 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.325 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.432 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.352 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.414 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4095ms rtt min/avg/max/mdev = 0.325/0.438/0.668/0.121 ms
Step 4: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
mark=12Show output
udp 17 24 src=127.0.0.1 dst=127.0.0.1 sport=58385 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=58385 packets=0 bytes=0 mark=0 use=1 udp 17 24 src=127.0.0.1 dst=127.0.0.1 sport=46703 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=46703 packets=0 bytes=0 mark=0 use=1 icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=428 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=428 packets=5 bytes=420 mark=12 use=1 conntrack v1.4.7 (conntrack-tools): 3 flow entries have been shown.
Step 5: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 copy tos connmark set traffic policy POLICY_IN rule 1 copy tos extra-connmark 1
Step 6: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 tos 12 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.319 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.319 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.273 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.535 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.343 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4075ms rtt min/avg/max/mdev = 0.273/0.357/0.535/0.091 ms
Step 7: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
emark1=12Show output
udp 17 27 src=127.0.0.1 dst=127.0.0.1 sport=49389 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=49389 packets=0 bytes=0 mark=0 use=1 udp 17 27 src=127.0.0.1 dst=127.0.0.1 sport=57945 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=57945 packets=0 bytes=0 mark=0 use=1 icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=429 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=429 packets=5 bytes=420 mark=0 emark1=12 use=1 conntrack v1.4.7 (conntrack-tools): 3 flow entries have been shown.
Test Policy Set
Description
In this scenario, an egress traffic policy
is configured
in DUT0 (‘eth0’ interface) to mark outgoing packets
using ToS and CoS fields.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN set traffic policy POLICY_OUT rule 1 set tos 12
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Run command traffic dump monitor detail interface eth0 filter "host 10.0.0.2"
at DUT1
.
Step 4: Ping IP address 10.0.0.2
from DUT0
:
admin@DUT0$ ping 10.0.0.2 count 1 size 56 timeout 1Show output
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.775 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.775/0.775/0.775/0.000 ms
Step 5: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_OUT rule 1 set tos set traffic policy POLICY_OUT rule 1 set cos 5
Step 6: Run command traffic dump monitor detail interface eth0 filter "host 10.0.0.2"
at DUT1
.
Step 7: Ping IP address 10.0.0.2
from DUT0
:
admin@DUT0$ ping 10.0.0.2 count 1 size 56 timeout 1Show output
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.607 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.607/0.607/0.607/0.000 ms
Test Policy Set Conntrack Values
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). Different set
actions are
configured to change the conntrack mark, the app-id and the
VRF.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 set connmark 15 set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.503 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.350 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.409 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.326 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.398 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4033ms rtt min/avg/max/mdev = 0.326/0.397/0.503/0.061 ms
Step 4: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
mark=15Show output
udp 17 26 src=127.0.0.1 dst=127.0.0.1 sport=46245 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=46245 packets=0 bytes=0 mark=0 use=1 udp 17 26 src=127.0.0.1 dst=127.0.0.1 sport=48351 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=48351 packets=0 bytes=0 mark=0 use=1 icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=430 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=430 packets=5 bytes=420 mark=15 use=1 conntrack v1.4.7 (conntrack-tools): 3 flow entries have been shown.
Step 5: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 set connmark set traffic policy POLICY_IN rule 1 set app-id custom 80
Step 6: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.356 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.364 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.364 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.299 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.351 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4015ms rtt min/avg/max/mdev = 0.299/0.346/0.364/0.024 ms
Step 7: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
appdetect[U:80]Show output
udp 17 27 src=127.0.0.1 dst=127.0.0.1 sport=57330 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=57330 packets=0 bytes=0 mark=0 use=1 icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=431 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=431 packets=5 bytes=420 mark=0 use=1 appdetect[U:80] udp 17 27 src=127.0.0.1 dst=127.0.0.1 sport=59724 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=59724 packets=0 bytes=0 mark=0 use=1 conntrack v1.4.7 (conntrack-tools): 3 flow entries have been shown.
Step 8: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 set app-id set interfaces ethernet eth0 vif 100 vrf RED set system vrf RED set traffic policy POLICY_IN rule 1 set vrf RED
Step 9: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.593 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.471 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.330 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.401 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.484 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4014ms rtt min/avg/max/mdev = 0.330/0.455/0.593/0.087 ms
Step 10: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
vrf=REDShow output
icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=432 vrf=RED packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=432 vrf=RED packets=5 bytes=420 mark=0 use=1 conntrack v1.4.7 (conntrack-tools): 1 flow entries have been shown.
Test Policy Log
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). The log
option is configured to
show system messages that help debug and analyze the
network status.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 log level err set traffic policy POLICY_IN rule 1 log prefix DEBUG- set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.674 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.674/0.674/0.674/0.000 ms
Step 4: Run command system journal show | tail
at DUT0
and check if output contains the following tokens:
[DEBUG--1] ACCEPT IN=eth0Show output
May 12 00:36:50.170256 osdx OSDxCLI[242344]: User 'admin' added a new cfg line: 'set traffic policy POLICY_OUT'. May 12 00:36:50.291863 osdx OSDxCLI[242344]: User 'admin' added a new cfg line: 'set traffic policy POLICY_IN rule 1 log prefix "DEBUG-"'. May 12 00:36:50.390111 osdx OSDxCLI[242344]: User 'admin' added a new cfg line: 'set traffic policy POLICY_IN rule 1 log level err'. May 12 00:36:50.505878 osdx OSDxCLI[242344]: User 'admin' added a new cfg line: 'show working'. May 12 00:36:50.691050 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0 May 12 00:36:50.735557 osdx (udev-worker)[443366]: Network interface NamePolicy= disabled on kernel command line. May 12 00:36:50.916121 osdx cfgd[1244]: [242344]Completed change to active configuration May 12 00:36:50.952937 osdx OSDxCLI[242344]: User 'admin' committed the configuration. May 12 00:36:50.979523 osdx OSDxCLI[242344]: User 'admin' left the configuration menu. May 12 00:36:52.022550 osdx kernel: [DEBUG--1] ACCEPT IN=eth0.100 OUT= MAC=de:ad:be:ef:6c:00:de:ad:be:ef:6c:10:08:00:45:00:00:54 SRC=10.0.0.2 DST=10.0.0.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=2533 DF PROTO=ICMP TYPE=8 CODE=0 ID=433 SEQ=1
Test Policy Advisor
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). The advisor
option is
configured to enable/disable the rule depending on
the advisor status. If the rule is enabled, incoming traffic
will be dropped.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system advisor ADV test false set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 action drop set traffic policy POLICY_IN rule 1 advisor ADV set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.507 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.507/0.507/0.507/0.000 ms
Step 4: Modify the following configuration lines in DUT0
:
set system advisor ADV test true
Step 5: Expect a failure in the following command:
Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. --- 10.0.0.1 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms
Step 6: Modify the following configuration lines in DUT0
:
set system advisor ADV test false
Step 7: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.307 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms