force_local_traffic_through_external_ethernet_cable_by_using_ip_namespaces

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
force_local_traffic_through_external_ethernet_cable_by_using_ip_namespaces [10.02.2018 10:45] – Pascal Suterforce_local_traffic_through_external_ethernet_cable_by_using_ip_namespaces [10.02.2018 10:47] (current) – Pascal Suter
Line 34: Line 34:
   ip netns exec ns_client iperf -c 10.0.0.1 -d -P 20 -t 99999   ip netns exec ns_client iperf -c 10.0.0.1 -d -P 20 -t 99999
 ''-d'' uses bidirectional transfers, ''-P 20'' runs 20 processes in parallel and ''-t 99999'' runs for 99999 seconds ''-d'' uses bidirectional transfers, ''-P 20'' runs 20 processes in parallel and ''-t 99999'' runs for 99999 seconds
 +
 +===== cleaning up =====
 +once you are done, simply run 
 +  ip netns del ns_server
 +  ip netns del ns_client
 +and all your settings including the ip addresses etc. are gone. your interfaces will be back in the default namespace
  
  • force_local_traffic_through_external_ethernet_cable_by_using_ip_namespaces.txt
  • Last modified: 10.02.2018 10:47
  • by Pascal Suter