2009-07-08 13:19:16 -07:00
|
|
|
bin_PROGRAMS += \
|
|
|
|
utilities/ovs-appctl \
|
2014-08-15 10:32:50 -07:00
|
|
|
utilities/ovs-testcontroller \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-dpctl \
|
|
|
|
utilities/ovs-ofctl \
|
2010-05-26 10:25:19 -07:00
|
|
|
utilities/ovs-vsctl
|
2014-10-14 00:51:52 -07:00
|
|
|
bin_SCRIPTS += utilities/ovs-docker \
|
|
|
|
utilities/ovs-pki
|
ofproto: Add "ofproto/trace" command to help debugging flow tables.
With an appropriate flow table, output from a command like this:
ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010
80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000
0000000
resembles the following:
Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x
0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138
Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080
6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Rule: cookie=0 in_port=65534
OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan
Resubmitted flow: unchanged
Rule: cookie=0 in_port=1
OpenFlow actions=resubmit:3,resubmit:4
Resubmitted flow: unchanged
No match
Resubmitted flow: unchanged
No match
Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d:
5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
No match
Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t
ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
|
|
|
if HAVE_PYTHON
|
2010-12-07 18:49:28 -08:00
|
|
|
bin_SCRIPTS += \
|
2013-09-13 15:50:48 -07:00
|
|
|
utilities/ovs-dpctl-top \
|
2012-06-28 15:52:40 -07:00
|
|
|
utilities/ovs-l3ping \
|
2012-10-15 12:42:48 -07:00
|
|
|
utilities/ovs-parse-backtrace \
|
2010-12-07 18:49:28 -08:00
|
|
|
utilities/ovs-pcap \
|
2016-06-08 17:49:55 -04:00
|
|
|
utilities/ovs-tcpdump \
|
2010-12-07 18:49:28 -08:00
|
|
|
utilities/ovs-tcpundump \
|
2011-10-31 14:56:08 -07:00
|
|
|
utilities/ovs-test \
|
2010-12-07 18:49:28 -08:00
|
|
|
utilities/ovs-vlan-test
|
ofproto: Add "ofproto/trace" command to help debugging flow tables.
With an appropriate flow table, output from a command like this:
ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010
80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000
0000000
resembles the following:
Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x
0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138
Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080
6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Rule: cookie=0 in_port=65534
OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan
Resubmitted flow: unchanged
Rule: cookie=0 in_port=1
OpenFlow actions=resubmit:3,resubmit:4
Resubmitted flow: unchanged
No match
Resubmitted flow: unchanged
No match
Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d:
5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
No match
Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t
ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
|
|
|
endif
|
2012-05-01 15:36:44 -07:00
|
|
|
scripts_SCRIPTS += \
|
|
|
|
utilities/ovs-check-dead-ifs \
|
|
|
|
utilities/ovs-ctl \
|
|
|
|
utilities/ovs-save
|
2011-12-08 23:36:05 -08:00
|
|
|
scripts_DATA += utilities/ovs-lib
|
2009-07-08 13:19:16 -07:00
|
|
|
|
2015-03-18 14:32:23 -07:00
|
|
|
completion_SCRIPTS += \
|
|
|
|
utilities/ovs-appctl-bashcomp.bash \
|
|
|
|
utilities/ovs-vsctl-bashcomp.bash
|
|
|
|
|
2015-02-11 11:08:57 -08:00
|
|
|
check_SCRIPTS += \
|
|
|
|
utilities/ovs-appctl-bashcomp.bash \
|
|
|
|
utilities/ovs-vsctl-bashcomp.bash
|
2014-11-24 11:15:45 -08:00
|
|
|
|
2018-05-17 12:31:45 -07:00
|
|
|
EXTRA_DIST += utilities/ovs-sim.in
|
2015-06-16 08:38:46 -07:00
|
|
|
noinst_SCRIPTS += utilities/ovs-sim
|
|
|
|
|
2013-11-19 11:02:08 -08:00
|
|
|
utilities/ovs-lib: $(top_builddir)/config.status
|
|
|
|
|
2009-07-08 13:19:16 -07:00
|
|
|
EXTRA_DIST += \
|
utilities: Add some GDB macros for ovs-vswitchd
This commit adds basic GDB macro's for ovs-vswitchd:
- ovs_dump_bridge [ports|wanted]
- ovs_dump_bridge_ports <struct bridge *>
- ovs_dump_dp_netdev [ports]
- ovs_dump_dp_netdev_ports <struct dp_netdev *>
- ovs_dump_netdev
These dump functions show limited info, but you can simply cut/paste
the address and get the full structure info. For example:
(gdb) ovs_dump_netdev
(struct netdev *) 0x555771ed89e0: name = ovs-netdev , auto_classified = false, netdev_class = 0x5557714413c0 <netdev_tap_class>
(struct netdev *) 0x555771fc62a0: name = ovs_pvp_br0 , auto_classified = false, netdev_class = 0x5557714413c0 <netdev_tap_class>
(struct netdev *) 0x555771fc9660: name = vnet0 , auto_classified = true , netdev_class = 0x555771445e00 <netdev_linux_class>
(struct netdev *) 0x555771fc78d0: name = virbr0 , auto_classified = true , netdev_class = 0x555771445e00 <netdev_linux_class>
(struct netdev *) 0x7fbefffb5540: name = dpdk0 , auto_classified = false, netdev_class = 0x5557714419e0 <dpdk_class>
(struct netdev *) 0x555771fc98b0: name = em3 , auto_classified = true , netdev_class = 0x555771445e00 <netdev_linux_class>
(struct netdev *) 0x7fbea0a31c40: name = vhost0 , auto_classified = false, netdev_class = 0x555771442040 <dpdk_vhost_client_class>
(gdb) p *((struct netdev *) 0x7fbefffb5540)
$1 = {name = 0x555771ecef70 "dpdk0", netdev_class = 0x5557714419e0 <dpdk_class>, auto_classified = false, mtu_user_config = true, ref_cnt = 2, change_seq = 12,
reconfigure_seq = 0x555771ecf2e0, last_reconfigure_seq = 110, n_txq = 2, n_rxq = 1, node = 0x555771efafe0, saved_flags_list = {prev = 0x7fbefffb5580, next = 0x7fbefffb5580}}
Signed-off-by: Eelco Chaudron <echaudro@redhat.com>
Signed-off-by: Ben Pfaff <blp@ovn.org>
2018-05-09 13:47:26 +02:00
|
|
|
utilities/gdb/ovs_gdb.py \
|
2015-02-10 11:06:11 -08:00
|
|
|
utilities/ovs-appctl-bashcomp.bash \
|
2015-03-26 12:52:42 -07:00
|
|
|
utilities/ovs-check-dead-ifs.in \
|
2011-10-26 16:06:37 -07:00
|
|
|
utilities/ovs-ctl.in \
|
2013-07-06 18:55:45 -07:00
|
|
|
utilities/ovs-dev.py \
|
2014-10-14 00:51:52 -07:00
|
|
|
utilities/ovs-docker \
|
2013-09-13 15:50:48 -07:00
|
|
|
utilities/ovs-dpctl-top.in \
|
2012-06-28 15:52:40 -07:00
|
|
|
utilities/ovs-l3ping.in \
|
2011-12-08 23:36:05 -08:00
|
|
|
utilities/ovs-lib.in \
|
2012-10-15 12:42:48 -07:00
|
|
|
utilities/ovs-parse-backtrace.in \
|
2011-10-26 16:06:37 -07:00
|
|
|
utilities/ovs-pcap.in \
|
2015-03-26 12:52:42 -07:00
|
|
|
utilities/ovs-pipegen.py \
|
2011-10-26 16:06:37 -07:00
|
|
|
utilities/ovs-pki.in \
|
|
|
|
utilities/ovs-save \
|
2016-06-08 17:49:55 -04:00
|
|
|
utilities/ovs-tcpdump.in \
|
2011-10-26 16:06:37 -07:00
|
|
|
utilities/ovs-tcpundump.in \
|
2011-10-31 14:56:08 -07:00
|
|
|
utilities/ovs-test.in \
|
2015-03-05 13:42:04 -08:00
|
|
|
utilities/ovs-vlan-test.in \
|
2015-03-26 12:52:42 -07:00
|
|
|
utilities/ovs-vsctl-bashcomp.bash \
|
2016-03-31 10:45:35 -04:00
|
|
|
utilities/checkpatch.py
|
2011-10-26 16:06:37 -07:00
|
|
|
MAN_ROOTS += \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-appctl.8.in \
|
2014-08-15 10:32:50 -07:00
|
|
|
utilities/ovs-testcontroller.8.in \
|
2011-10-26 16:06:37 -07:00
|
|
|
utilities/ovs-ctl.8 \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-dpctl.8.in \
|
2013-09-13 15:50:48 -07:00
|
|
|
utilities/ovs-dpctl-top.8.in \
|
2012-06-28 15:52:40 -07:00
|
|
|
utilities/ovs-l3ping.8.in \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-ofctl.8.in \
|
2012-10-15 12:42:48 -07:00
|
|
|
utilities/ovs-parse-backtrace.8 \
|
ofproto: Add "ofproto/trace" command to help debugging flow tables.
With an appropriate flow table, output from a command like this:
ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010
80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000
0000000
resembles the following:
Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x
0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138
Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080
6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Rule: cookie=0 in_port=65534
OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan
Resubmitted flow: unchanged
Rule: cookie=0 in_port=1
OpenFlow actions=resubmit:3,resubmit:4
Resubmitted flow: unchanged
No match
Resubmitted flow: unchanged
No match
Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d:
5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
No match
Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t
ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
|
|
|
utilities/ovs-pcap.1.in \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-pki.8.in \
|
2016-06-08 17:49:55 -04:00
|
|
|
utilities/ovs-tcpdump.8.in \
|
ofproto: Add "ofproto/trace" command to help debugging flow tables.
With an appropriate flow table, output from a command like this:
ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010
80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000
0000000
resembles the following:
Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x
0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138
Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080
6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Rule: cookie=0 in_port=65534
OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan
Resubmitted flow: unchanged
Rule: cookie=0 in_port=1
OpenFlow actions=resubmit:3,resubmit:4
Resubmitted flow: unchanged
No match
Resubmitted flow: unchanged
No match
Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d:
5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
No match
Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t
ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
|
|
|
utilities/ovs-tcpundump.1.in \
|
Support vlan_group workaround implemented in XenServer kernels.
Some Linux network drivers support a feature called "VLAN acceleration",
associated with a data structure called a "vlan_group". A vlan_group is,
abstractly, a dictionary that maps from a VLAN ID (in the range 0...4095)
to a VLAN device, that is, a Linux network device associated with a
particular VLAN, e.g. "eth0.9" for VLAN 9 on eth0.
Some drivers that support VLAN acceleration have bugs that fall roughly
into the following categories:
* Some NICs strip VLAN tags on receive if no vlan_group is registered,
so that the tag is completely lost.
* Some drivers size their receive buffers based on whether a vlan_group
is enabled, meaning that a maximum size packet with a VLAN tag will
not fit if a vlan_group is not configured.
* On transmit some drivers expect that VLAN acceleration will be used
if it is available (which can only be done if a vlan_group is
configured). In these cases, the driver may fail to parse the packet
and correctly setup checksum offloading and/or TSO.
The correct long term solution is to fix these driver bugs. To cope until
then, we have prepared a patch to the Linux kernel network stack that works
around these problems. This commit adds support for the workaround
implemented by that patch.
Signed-off-by: Ben Pfaff <blp@nicira.com>
Acked-by: Jesse Gross <jesse@nicira.com>
2011-03-16 14:39:17 -07:00
|
|
|
utilities/ovs-vlan-bug-workaround.8.in \
|
2009-12-08 17:18:12 -08:00
|
|
|
utilities/ovs-vsctl.8.in
|
2011-08-24 10:45:32 -07:00
|
|
|
MAN_FRAGMENTS += utilities/ovs-vlan-bugs.man
|
2017-02-13 17:20:56 -08:00
|
|
|
CLEANFILES += \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-appctl.8 \
|
2011-06-17 12:24:31 -07:00
|
|
|
utilities/ovs-ctl \
|
2012-05-10 09:37:11 -07:00
|
|
|
utilities/ovs-check-dead-ifs \
|
2014-08-15 10:32:50 -07:00
|
|
|
utilities/ovs-testcontroller.8 \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-dpctl.8 \
|
2013-09-13 15:50:48 -07:00
|
|
|
utilities/ovs-dpctl-top \
|
|
|
|
utilities/ovs-dpctl-top.8 \
|
2012-06-28 15:52:40 -07:00
|
|
|
utilities/ovs-l3ping \
|
|
|
|
utilities/ovs-l3ping.8 \
|
2011-12-08 23:36:05 -08:00
|
|
|
utilities/ovs-lib \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-ofctl.8 \
|
2012-10-15 12:42:48 -07:00
|
|
|
utilities/ovs-parse-backtrace \
|
ofproto: Add "ofproto/trace" command to help debugging flow tables.
With an appropriate flow table, output from a command like this:
ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010
80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000
0000000
resembles the following:
Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x
0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138
Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080
6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Rule: cookie=0 in_port=65534
OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan
Resubmitted flow: unchanged
Rule: cookie=0 in_port=1
OpenFlow actions=resubmit:3,resubmit:4
Resubmitted flow: unchanged
No match
Resubmitted flow: unchanged
No match
Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d:
5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
No match
Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t
ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
|
|
|
utilities/ovs-pcap \
|
|
|
|
utilities/ovs-pcap.1 \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-pki \
|
|
|
|
utilities/ovs-pki.8 \
|
2015-06-23 07:31:41 -07:00
|
|
|
utilities/ovs-sim \
|
2016-06-08 17:49:55 -04:00
|
|
|
utilities/ovs-tcpdump \
|
|
|
|
utilities/ovs-tcpdump.8 \
|
ofproto: Add "ofproto/trace" command to help debugging flow tables.
With an appropriate flow table, output from a command like this:
ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010
80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000
0000000
resembles the following:
Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x
0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138
Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080
6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Rule: cookie=0 in_port=65534
OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan
Resubmitted flow: unchanged
Rule: cookie=0 in_port=1
OpenFlow actions=resubmit:3,resubmit:4
Resubmitted flow: unchanged
No match
Resubmitted flow: unchanged
No match
Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d:
5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
No match
Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t
ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
|
|
|
utilities/ovs-tcpundump \
|
|
|
|
utilities/ovs-tcpundump.1 \
|
2011-10-31 14:56:08 -07:00
|
|
|
utilities/ovs-test \
|
2010-12-07 18:49:28 -08:00
|
|
|
utilities/ovs-vlan-test \
|
2011-03-22 18:55:53 -07:00
|
|
|
utilities/ovs-vlan-bug-workaround.8 \
|
2009-09-14 10:05:13 -07:00
|
|
|
utilities/ovs-vsctl.8
|
2009-07-08 13:19:16 -07:00
|
|
|
|
|
|
|
man_MANS += \
|
|
|
|
utilities/ovs-appctl.8 \
|
2014-05-01 08:10:20 -07:00
|
|
|
utilities/ovs-ctl.8 \
|
2014-08-15 10:32:50 -07:00
|
|
|
utilities/ovs-testcontroller.8 \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-dpctl.8 \
|
2013-09-13 15:50:48 -07:00
|
|
|
utilities/ovs-dpctl-top.8 \
|
2012-06-28 15:52:40 -07:00
|
|
|
utilities/ovs-l3ping.8 \
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities/ovs-ofctl.8 \
|
2012-10-15 12:42:48 -07:00
|
|
|
utilities/ovs-parse-backtrace.8 \
|
ofproto: Add "ofproto/trace" command to help debugging flow tables.
With an appropriate flow table, output from a command like this:
ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010
80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000
0000000
resembles the following:
Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x
0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138
Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080
6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Rule: cookie=0 in_port=65534
OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan
Resubmitted flow: unchanged
Rule: cookie=0 in_port=1
OpenFlow actions=resubmit:3,resubmit:4
Resubmitted flow: unchanged
No match
Resubmitted flow: unchanged
No match
Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d:
5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
No match
Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t
ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
|
|
|
utilities/ovs-pcap.1 \
|
2009-09-14 10:05:13 -07:00
|
|
|
utilities/ovs-pki.8 \
|
2016-06-08 17:49:55 -04:00
|
|
|
utilities/ovs-tcpdump.8 \
|
ofproto: Add "ofproto/trace" command to help debugging flow tables.
With an appropriate flow table, output from a command like this:
ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010
80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000
0000000
resembles the following:
Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x
0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138
Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080
6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Rule: cookie=0 in_port=65534
OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan
Resubmitted flow: unchanged
Rule: cookie=0 in_port=1
OpenFlow actions=resubmit:3,resubmit:4
Resubmitted flow: unchanged
No match
Resubmitted flow: unchanged
No match
Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d:
5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
No match
Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t
ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0
Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
|
|
|
utilities/ovs-tcpundump.1 \
|
2011-03-16 15:45:25 -07:00
|
|
|
utilities/ovs-vlan-bug-workaround.8 \
|
2009-09-14 10:05:13 -07:00
|
|
|
utilities/ovs-vsctl.8
|
2009-07-08 13:19:16 -07:00
|
|
|
|
|
|
|
utilities_ovs_appctl_SOURCES = utilities/ovs-appctl.c
|
2014-03-04 13:23:53 -08:00
|
|
|
utilities_ovs_appctl_LDADD = lib/libopenvswitch.la
|
2009-07-08 13:19:16 -07:00
|
|
|
|
2014-08-15 10:32:50 -07:00
|
|
|
utilities_ovs_testcontroller_SOURCES = utilities/ovs-testcontroller.c
|
|
|
|
utilities_ovs_testcontroller_LDADD = lib/libopenvswitch.la $(SSL_LIBS)
|
|
|
|
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities_ovs_dpctl_SOURCES = utilities/ovs-dpctl.c
|
2014-03-04 13:23:53 -08:00
|
|
|
utilities_ovs_dpctl_LDADD = lib/libopenvswitch.la
|
2009-07-08 13:19:16 -07:00
|
|
|
|
|
|
|
utilities_ovs_ofctl_SOURCES = utilities/ovs-ofctl.c
|
2011-04-11 15:08:19 -07:00
|
|
|
utilities_ovs_ofctl_LDADD = \
|
2013-12-13 18:54:28 +01:00
|
|
|
ofproto/libofproto.la \
|
2014-03-04 13:23:53 -08:00
|
|
|
lib/libopenvswitch.la
|
2009-07-08 13:19:16 -07:00
|
|
|
|
2012-03-15 17:10:41 -07:00
|
|
|
utilities_ovs_vsctl_SOURCES = utilities/ovs-vsctl.c
|
2014-03-04 13:23:53 -08:00
|
|
|
utilities_ovs_vsctl_LDADD = lib/libopenvswitch.la
|
2009-12-08 17:18:12 -08:00
|
|
|
|
2014-01-23 15:35:22 -08:00
|
|
|
if LINUX
|
Support vlan_group workaround implemented in XenServer kernels.
Some Linux network drivers support a feature called "VLAN acceleration",
associated with a data structure called a "vlan_group". A vlan_group is,
abstractly, a dictionary that maps from a VLAN ID (in the range 0...4095)
to a VLAN device, that is, a Linux network device associated with a
particular VLAN, e.g. "eth0.9" for VLAN 9 on eth0.
Some drivers that support VLAN acceleration have bugs that fall roughly
into the following categories:
* Some NICs strip VLAN tags on receive if no vlan_group is registered,
so that the tag is completely lost.
* Some drivers size their receive buffers based on whether a vlan_group
is enabled, meaning that a maximum size packet with a VLAN tag will
not fit if a vlan_group is not configured.
* On transmit some drivers expect that VLAN acceleration will be used
if it is available (which can only be done if a vlan_group is
configured). In these cases, the driver may fail to parse the packet
and correctly setup checksum offloading and/or TSO.
The correct long term solution is to fix these driver bugs. To cope until
then, we have prepared a patch to the Linux kernel network stack that works
around these problems. This commit adds support for the workaround
implemented by that patch.
Signed-off-by: Ben Pfaff <blp@nicira.com>
Acked-by: Jesse Gross <jesse@nicira.com>
2011-03-16 14:39:17 -07:00
|
|
|
sbin_PROGRAMS += utilities/ovs-vlan-bug-workaround
|
|
|
|
utilities_ovs_vlan_bug_workaround_SOURCES = utilities/ovs-vlan-bug-workaround.c
|
2014-03-04 13:23:53 -08:00
|
|
|
utilities_ovs_vlan_bug_workaround_LDADD = lib/libopenvswitch.la
|
Support vlan_group workaround implemented in XenServer kernels.
Some Linux network drivers support a feature called "VLAN acceleration",
associated with a data structure called a "vlan_group". A vlan_group is,
abstractly, a dictionary that maps from a VLAN ID (in the range 0...4095)
to a VLAN device, that is, a Linux network device associated with a
particular VLAN, e.g. "eth0.9" for VLAN 9 on eth0.
Some drivers that support VLAN acceleration have bugs that fall roughly
into the following categories:
* Some NICs strip VLAN tags on receive if no vlan_group is registered,
so that the tag is completely lost.
* Some drivers size their receive buffers based on whether a vlan_group
is enabled, meaning that a maximum size packet with a VLAN tag will
not fit if a vlan_group is not configured.
* On transmit some drivers expect that VLAN acceleration will be used
if it is available (which can only be done if a vlan_group is
configured). In these cases, the driver may fail to parse the packet
and correctly setup checksum offloading and/or TSO.
The correct long term solution is to fix these driver bugs. To cope until
then, we have prepared a patch to the Linux kernel network stack that works
around these problems. This commit adds support for the workaround
implemented by that patch.
Signed-off-by: Ben Pfaff <blp@nicira.com>
Acked-by: Jesse Gross <jesse@nicira.com>
2011-03-16 14:39:17 -07:00
|
|
|
|
2010-05-26 10:25:19 -07:00
|
|
|
noinst_PROGRAMS += utilities/nlmon
|
2009-07-08 13:19:16 -07:00
|
|
|
utilities_nlmon_SOURCES = utilities/nlmon.c
|
2014-03-04 13:23:53 -08:00
|
|
|
utilities_nlmon_LDADD = lib/libopenvswitch.la
|
2010-05-26 10:25:19 -07:00
|
|
|
endif
|
2011-07-06 10:43:03 -07:00
|
|
|
|
2016-03-31 10:45:35 -04:00
|
|
|
FLAKE8_PYFILES += utilities/ovs-pcap.in \
|
2016-06-08 17:49:55 -04:00
|
|
|
utilities/checkpatch.py utilities/ovs-dev.py \
|
2018-03-13 15:58:59 -04:00
|
|
|
utilities/ovs-tcpdump.in \
|
|
|
|
utilities/ovs-pipegen.py
|
2015-12-21 20:24:34 -05:00
|
|
|
|
2011-07-06 10:43:03 -07:00
|
|
|
include utilities/bugtool/automake.mk
|