diff options
| author | Ben Pfaff <blp@ovn.org> | 2017-06-01 07:21:41 -0700 |
|---|---|---|
| committer | Ben Pfaff <blp@ovn.org> | 2017-06-01 07:21:41 -0700 |
| commit | 0b2c7e690a0ad1efda5487f828690db64133980e (patch) | |
| tree | 6ab42ce058d52a668e1bd83e52765af06908c039 /Documentation/howto/dpdk.rst | |
| parent | e2d12c07df97fc19c01f076be0a2bbb388e84c52 (diff) | |
| download | openvswitch-0b2c7e690a0ad1efda5487f828690db64133980e.tar.gz | |
Replace most uses of and references to "ifconfig" by "ip".
It's becoming more common that OSes include "ip" but not "ifconfig", so
it's best to avoid using the latter. This commit removes most references
to "ifconfig" and replaces them by "ip". It also adds a build-time check
to make it harder to introduce new uses of "ifconfig".
There are important differences between "ifconfig" and "ip":
- An "ifconfig" command that sets an IP address also brings the interface
up, but a similar "ip addr add" command does not, so it is often necessary
(or at least precautionary) to add an "ip link set <dev> up" command.
- "ifconfig" can infer a netmask from an IP adddress, but "ip" always
assumes /32 if none is given.
- "ifconfig" with address 0.0.0.0 removes any configured IP address, but
"ip addr add" does not, so "ifconfig <dev> 0.0.0.0" must be replaced by
"ip addr del" or "ip addr flush".
Signed-off-by: Ben Pfaff <blp@ovn.org>
Diffstat (limited to 'Documentation/howto/dpdk.rst')
| -rw-r--r-- | Documentation/howto/dpdk.rst | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/Documentation/howto/dpdk.rst b/Documentation/howto/dpdk.rst index 7c06239d3..f3c7aff1f 100644 --- a/Documentation/howto/dpdk.rst +++ b/Documentation/howto/dpdk.rst @@ -262,7 +262,7 @@ vHost ports: and CRC lengths (i.e. 18B) from the max supported frame size. So, to set the MTU for a 9018B Jumbo Frame:: - $ ifconfig eth1 mtu 9000 + $ ip link set eth1 mtu 9000 When Jumbo Frames are enabled, the size of a DPDK port's mbuf segments are increased, such that a full Jumbo Frame of a specific size may be accommodated @@ -564,8 +564,10 @@ testcase and packet forwarding using DPDK testpmd application in the Guest VM. For users wishing to do packet forwarding using kernel stack below, you need to run the below commands on the guest:: - $ ifconfig eth1 1.1.1.2/24 - $ ifconfig eth2 1.1.2.2/24 + $ ip addr add 1.1.1.2/24 dev eth1 + $ ip addr add 1.1.2.2/24 dev eth2 + $ ip link set eth1 up + $ ip link set eth2 up $ systemctl stop firewalld.service $ systemctl stop iptables.service $ sysctl -w net.ipv4.ip_forward=1 @@ -655,8 +657,10 @@ devices to bridge ``br0``. Once complete, follow the below steps: Configure IP and enable interfaces:: - $ ifconfig eth0 5.5.5.1/24 up - $ ifconfig eth1 90.90.90.1/24 up + $ ip addr add 5.5.5.1/24 dev eth0 + $ ip addr add 90.90.90.1/24 dev eth1 + $ ip link set eth0 up + $ ip link set eth1 up Configure IP forwarding and add route entries:: |