2015-08-04 19:00:16 +01:00
|
|
|
# DEL_NAMESPACES(ns [, ns ... ])
|
|
|
|
#
|
|
|
|
# Delete namespaces from the running OS
|
|
|
|
m4_define([DEL_NAMESPACES],
|
|
|
|
[m4_foreach([ns], [$@],
|
|
|
|
[ip netns del ns
|
|
|
|
])
|
|
|
|
]
|
|
|
|
)
|
2015-08-07 19:40:35 +01:00
|
|
|
|
2015-08-04 19:00:16 +01:00
|
|
|
# ADD_NAMESPACES(ns [, ns ... ])
|
|
|
|
#
|
|
|
|
# Add new namespaces, if ns exists, the old one
|
|
|
|
# will be remove before new ones are installed.
|
|
|
|
m4_define([ADD_NAMESPACES],
|
|
|
|
[m4_foreach([ns], [$@],
|
|
|
|
[DEL_NAMESPACES(ns)
|
2016-03-04 08:31:56 +03:00
|
|
|
AT_CHECK([ip netns add ns || return 77])
|
|
|
|
on_exit 'DEL_NAMESPACES(ns)'
|
2016-05-04 18:01:03 -07:00
|
|
|
ip netns exec ns sysctl -w net.netfilter.nf_conntrack_helper=0
|
2015-08-04 19:00:16 +01:00
|
|
|
])
|
|
|
|
]
|
|
|
|
)
|
|
|
|
|
2015-08-07 19:40:35 +01:00
|
|
|
# NS_EXEC([namespace], [command])
|
|
|
|
#
|
|
|
|
# Execute 'command' in 'namespace'
|
|
|
|
m4_define([NS_EXEC],
|
2015-08-12 14:01:26 -07:00
|
|
|
[ip netns exec $1 sh << NS_EXEC_HEREDOC
|
|
|
|
$2
|
|
|
|
NS_EXEC_HEREDOC])
|
2015-08-07 19:40:35 +01:00
|
|
|
|
|
|
|
# NS_CHECK_EXEC([namespace], [command], other_params...)
|
|
|
|
#
|
|
|
|
# Wrapper for AT_CHECK that executes 'command' inside 'namespace'.
|
|
|
|
# 'other_params' as passed as they are to AT_CHECK.
|
|
|
|
m4_define([NS_CHECK_EXEC],
|
|
|
|
[ AT_CHECK([NS_EXEC([$1], [$2])], m4_shift(m4_shift($@))) ]
|
|
|
|
)
|
|
|
|
|
2015-08-12 14:01:28 -07:00
|
|
|
# ADD_BR([name], [vsctl-args])
|
|
|
|
#
|
|
|
|
# Expands into the proper ovs-vsctl commands to create a bridge with the
|
|
|
|
# appropriate type, and allows additional arguments to be passed.
|
|
|
|
m4_define([ADD_BR], [ovs-vsctl _ADD_BR([$1]) -- $2])
|
|
|
|
|
2015-11-07 12:00:00 -08:00
|
|
|
# ADD_INT([port], [namespace], [ovs-br], [ip_addr])
|
|
|
|
#
|
|
|
|
# Add an internal port to 'ovs-br', then shift it into 'namespace' and
|
|
|
|
# configure it with 'ip_addr' (specified in CIDR notation).
|
|
|
|
m4_define([ADD_INT],
|
|
|
|
[ AT_CHECK([ovs-vsctl add-port $3 $1 -- set int $1 type=internal])
|
|
|
|
AT_CHECK([ip link set $1 netns $2])
|
|
|
|
NS_CHECK_EXEC([$2], [ip addr add $4 dev $1])
|
|
|
|
NS_CHECK_EXEC([$2], [ip link set dev $1 up])
|
|
|
|
]
|
|
|
|
)
|
|
|
|
|
2016-07-11 02:55:59 -07:00
|
|
|
# ADD_VETH([port], [namespace], [ovs-br], [ip_addr] [mac_addr [gateway]])
|
2015-08-04 19:00:16 +01:00
|
|
|
#
|
|
|
|
# Add a pair of veth ports. 'port' will be added to name space 'namespace',
|
|
|
|
# and "ovs-'port'" will be added to ovs bridge 'ovs-br'.
|
|
|
|
#
|
|
|
|
# The 'port' in 'namespace' will be brought up with static IP address
|
|
|
|
# with 'ip_addr' in CIDR notation.
|
|
|
|
#
|
2016-07-11 02:55:59 -07:00
|
|
|
# Optionally, one can specify the 'mac_addr' for 'port' and the default
|
|
|
|
# 'gateway'.
|
|
|
|
#
|
2015-08-04 19:00:16 +01:00
|
|
|
# The existing 'port' or 'ovs-port' will be removed before new ones are added.
|
|
|
|
#
|
|
|
|
m4_define([ADD_VETH],
|
2016-03-04 08:31:56 +03:00
|
|
|
[ AT_CHECK([ip link add $1 type veth peer name ovs-$1 || return 77])
|
system-tests: Disable offloads in userspace tests.
The system userspace testsuite uses the userspace datapath with
netdev-linux devices, connected to veth pairs with the AF_PACKET socket:
(veth pair) (AF_PACKET)
TCP stack -> p0 ---> ovs-p0 -------------> netdev-linux (userspace OVS)
Unfortunately this configuration has some problems with offloads: a
packet generated by the TCP stack maybe sent to p0 without being
checksummed or segmented. The AF_PACKET socket, by default, ignores the
offloads and just transmits the data of the packets to userspace, but:
1. The packet may need GSO, so the data will be too big to be received
by the userspace datapath
2. The packet might have incomplete checksums, so it will likely be
discarded by the receiver.
Problem 1 causes TCP connections to see a congestion window smaller than
the MTU, which hurts performance but doesn't prevent communication.
Problem 2 was hidden in the testsuite by a Linux kernel bug, fixed by
commit ce8c839b74e3("veth: don’t modify ip_summed; doing so treats
packets with bad checksums as good"). In the kernels that include the
fix, the userspace datapath is able to process pings, but not tcp or udp
data.
Unfortunately I couldn't find a way to ask the AF_PACKET to perform
offloads in kernel. A possible fix would be to use the PACKET_VNET_HDR
sockopt and perform the offloads in userspace.
Until a proper fix is worked out for netdev-linux, this commit disables
offloads on the non-OVS side of the veth pair, as a workaround.
Signed-off-by: Daniele Di Proietto <diproiettod@vmware.com>
Acked-by: Joe Stringer <joe@ovn.org>
Acked-by: Flavio Leitner <fbl@sysclose.org>
2016-04-15 13:17:50 -07:00
|
|
|
CONFIGURE_VETH_OFFLOADS([$1])
|
2015-08-04 19:00:16 +01:00
|
|
|
AT_CHECK([ip link set $1 netns $2])
|
|
|
|
AT_CHECK([ip link set dev ovs-$1 up])
|
2015-08-07 19:40:36 +01:00
|
|
|
AT_CHECK([ovs-vsctl add-port $3 ovs-$1])
|
2015-08-07 19:40:35 +01:00
|
|
|
NS_CHECK_EXEC([$2], [ip addr add $4 dev $1])
|
|
|
|
NS_CHECK_EXEC([$2], [ip link set dev $1 up])
|
2016-07-11 02:55:59 -07:00
|
|
|
if test -n "$5"; then
|
|
|
|
NS_CHECK_EXEC([$2], [ip link set dev $1 address $5])
|
|
|
|
fi
|
|
|
|
if test -n "$6"; then
|
|
|
|
NS_CHECK_EXEC([$2], [ip route add default via $6])
|
|
|
|
fi
|
2015-09-09 10:26:11 -07:00
|
|
|
on_exit 'ip link del ovs-$1'
|
2015-08-04 19:00:16 +01:00
|
|
|
]
|
|
|
|
)
|
|
|
|
|
|
|
|
# ADD_VLAN([port], [namespace], [vlan-id], [ip-addr])
|
|
|
|
#
|
|
|
|
# Add a VLAN device named 'port' within 'namespace'. It will be configured
|
|
|
|
# with the ID 'vlan-id' and the address 'ip-addr'.
|
|
|
|
m4_define([ADD_VLAN],
|
2015-08-07 19:40:35 +01:00
|
|
|
[ NS_CHECK_EXEC([$2], [ip link add link $1 name $1.$3 type vlan id $3])
|
|
|
|
NS_CHECK_EXEC([$2], [ip link set dev $1.$3 up])
|
|
|
|
NS_CHECK_EXEC([$2], [ip addr add dev $1.$3 $4])
|
2015-08-04 19:00:16 +01:00
|
|
|
]
|
|
|
|
)
|
2015-08-12 14:01:27 -07:00
|
|
|
|
2015-08-12 14:01:30 -07:00
|
|
|
# ADD_OVS_TUNNEL([type], [bridge], [port], [remote-addr], [overlay-addr])
|
|
|
|
#
|
|
|
|
# Add an ovs-based tunnel device in the root namespace, with name 'port' and
|
|
|
|
# type 'type'. The tunnel device will be configured as point-to-point with the
|
|
|
|
# 'remote-addr' as the underlay address of the remote tunnel endpoint.
|
|
|
|
#
|
|
|
|
# 'port will be configured with the address 'overlay-addr'.
|
|
|
|
#
|
|
|
|
m4_define([ADD_OVS_TUNNEL],
|
|
|
|
[AT_CHECK([ovs-vsctl add-port $2 $3 -- \
|
|
|
|
set int $3 type=$1 options:remote_ip=$4])
|
|
|
|
AT_CHECK([ip addr add dev $2 $5])
|
|
|
|
AT_CHECK([ip link set dev $2 up])
|
|
|
|
AT_CHECK([ip link set dev $2 mtu 1450])
|
2015-09-09 10:26:11 -07:00
|
|
|
on_exit 'ip addr del dev $2 $5'
|
2015-08-12 14:01:30 -07:00
|
|
|
]
|
|
|
|
)
|
|
|
|
|
|
|
|
# ADD_NATIVE_TUNNEL([type], [port], [namespace], [remote-addr], [overlay-addr],
|
|
|
|
# [link-args])
|
|
|
|
#
|
|
|
|
# Add a native tunnel device within 'namespace', with name 'port' and type
|
|
|
|
# 'type'. The tunnel device will be configured as point-to-point with the
|
|
|
|
# 'remote-addr' as the underlay address of the remote tunnel endpoint (as
|
|
|
|
# viewed from the perspective of that namespace).
|
|
|
|
#
|
|
|
|
# 'port' will be configured with the address 'overlay-addr'. 'link-args' is
|
|
|
|
# made available so that additional arguments can be passed to "ip link",
|
|
|
|
# for instance to configure the vxlan destination port.
|
|
|
|
#
|
|
|
|
m4_define([ADD_NATIVE_TUNNEL],
|
|
|
|
[NS_CHECK_EXEC([$3], [ip link add dev $2 type $1 remote $4 $6])
|
|
|
|
NS_CHECK_EXEC([$3], [ip addr add dev $2 $5])
|
|
|
|
NS_CHECK_EXEC([$3], [ip link set dev $2 up])
|
|
|
|
NS_CHECK_EXEC([$3], [ip link set dev $2 mtu 1450])
|
|
|
|
]
|
|
|
|
)
|
|
|
|
|
2015-08-12 14:01:27 -07:00
|
|
|
# FORMAT_PING([])
|
|
|
|
#
|
|
|
|
# Strip variant pieces from ping output so the output can be reliably compared.
|
|
|
|
#
|
|
|
|
m4_define([FORMAT_PING], [grep "transmitted" | sed 's/time.*ms$/time 0ms/'])
|
Add support for connection tracking.
This patch adds a new action and fields to OVS that allow connection
tracking to be performed. This support works in conjunction with the
Linux kernel support merged into the Linux-4.3 development cycle.
Packets have two possible states with respect to connection tracking:
Untracked packets have not previously passed through the connection
tracker, while tracked packets have previously been through the
connection tracker. For OpenFlow pipeline processing, untracked packets
can become tracked, and they will remain tracked until the end of the
pipeline. Tracked packets cannot become untracked.
Connections can be unknown, uncommitted, or committed. Packets which are
untracked have unknown connection state. To know the connection state,
the packet must become tracked. Uncommitted connections have no
connection state stored about them, so it is only possible for the
connection tracker to identify whether they are a new connection or
whether they are invalid. Committed connections have connection state
stored beyond the lifetime of the packet, which allows later packets in
the same connection to be identified as part of the same established
connection, or related to an existing connection - for instance ICMP
error responses.
The new 'ct' action transitions the packet from "untracked" to
"tracked" by sending this flow through the connection tracker.
The following parameters are supported initally:
- "commit": When commit is executed, the connection moves from
uncommitted state to committed state. This signals that information
about the connection should be stored beyond the lifetime of the
packet within the pipeline. This allows future packets in the same
connection to be recognized as part of the same "established" (est)
connection, as well as identifying packets in the reply (rpl)
direction, or packets related to an existing connection (rel).
- "zone=[u16|NXM]": Perform connection tracking in the zone specified.
Each zone is an independent connection tracking context. When the
"commit" parameter is used, the connection will only be committed in
the specified zone, and not in other zones. This is 0 by default.
- "table=NUMBER": Fork pipeline processing in two. The original instance
of the packet will continue processing the current actions list as an
untracked packet. An additional instance of the packet will be sent to
the connection tracker, which will be re-injected into the OpenFlow
pipeline to resume processing in the specified table, with the
ct_state and other ct match fields set. If the table is not specified,
then the packet is submitted to the connection tracker, but the
pipeline does not fork and the ct match fields are not populated. It
is strongly recommended to specify a table later than the current
table to prevent loops.
When the "table" option is used, the packet that continues processing in
the specified table will have the ct_state populated. The ct_state may
have any of the following flags set:
- Tracked (trk): Connection tracking has occurred.
- Reply (rpl): The flow is in the reply direction.
- Invalid (inv): The connection tracker couldn't identify the connection.
- New (new): This is the beginning of a new connection.
- Established (est): This is part of an already existing connection.
- Related (rel): This connection is related to an existing connection.
For more information, consult the ovs-ofctl(8) man pages.
Below is a simple example flow table to allow outbound TCP traffic from
port 1 and drop traffic from port 2 that was not initiated by port 1:
table=0,priority=1,action=drop
table=0,arp,action=normal
table=0,in_port=1,tcp,ct_state=-trk,action=ct(commit,zone=9),2
table=0,in_port=2,tcp,ct_state=-trk,action=ct(zone=9,table=1)
table=1,in_port=2,ct_state=+trk+est,tcp,action=1
table=1,in_port=2,ct_state=+trk+new,tcp,action=drop
Based on original design by Justin Pettit, contributions from Thomas
Graf and Daniele Di Proietto.
Signed-off-by: Joe Stringer <joestringer@nicira.com>
Acked-by: Jarno Rajahalme <jrajahalme@nicira.com>
Acked-by: Ben Pfaff <blp@nicira.com>
2015-08-11 10:56:09 -07:00
|
|
|
|
2015-11-02 14:24:54 -08:00
|
|
|
# FORMAT_CT([ip-addr])
|
|
|
|
#
|
|
|
|
# Strip content from the piped input which would differ from test to test
|
|
|
|
# and limit the output to the rows containing 'ip-addr'.
|
Add support for connection tracking.
This patch adds a new action and fields to OVS that allow connection
tracking to be performed. This support works in conjunction with the
Linux kernel support merged into the Linux-4.3 development cycle.
Packets have two possible states with respect to connection tracking:
Untracked packets have not previously passed through the connection
tracker, while tracked packets have previously been through the
connection tracker. For OpenFlow pipeline processing, untracked packets
can become tracked, and they will remain tracked until the end of the
pipeline. Tracked packets cannot become untracked.
Connections can be unknown, uncommitted, or committed. Packets which are
untracked have unknown connection state. To know the connection state,
the packet must become tracked. Uncommitted connections have no
connection state stored about them, so it is only possible for the
connection tracker to identify whether they are a new connection or
whether they are invalid. Committed connections have connection state
stored beyond the lifetime of the packet, which allows later packets in
the same connection to be identified as part of the same established
connection, or related to an existing connection - for instance ICMP
error responses.
The new 'ct' action transitions the packet from "untracked" to
"tracked" by sending this flow through the connection tracker.
The following parameters are supported initally:
- "commit": When commit is executed, the connection moves from
uncommitted state to committed state. This signals that information
about the connection should be stored beyond the lifetime of the
packet within the pipeline. This allows future packets in the same
connection to be recognized as part of the same "established" (est)
connection, as well as identifying packets in the reply (rpl)
direction, or packets related to an existing connection (rel).
- "zone=[u16|NXM]": Perform connection tracking in the zone specified.
Each zone is an independent connection tracking context. When the
"commit" parameter is used, the connection will only be committed in
the specified zone, and not in other zones. This is 0 by default.
- "table=NUMBER": Fork pipeline processing in two. The original instance
of the packet will continue processing the current actions list as an
untracked packet. An additional instance of the packet will be sent to
the connection tracker, which will be re-injected into the OpenFlow
pipeline to resume processing in the specified table, with the
ct_state and other ct match fields set. If the table is not specified,
then the packet is submitted to the connection tracker, but the
pipeline does not fork and the ct match fields are not populated. It
is strongly recommended to specify a table later than the current
table to prevent loops.
When the "table" option is used, the packet that continues processing in
the specified table will have the ct_state populated. The ct_state may
have any of the following flags set:
- Tracked (trk): Connection tracking has occurred.
- Reply (rpl): The flow is in the reply direction.
- Invalid (inv): The connection tracker couldn't identify the connection.
- New (new): This is the beginning of a new connection.
- Established (est): This is part of an already existing connection.
- Related (rel): This connection is related to an existing connection.
For more information, consult the ovs-ofctl(8) man pages.
Below is a simple example flow table to allow outbound TCP traffic from
port 1 and drop traffic from port 2 that was not initiated by port 1:
table=0,priority=1,action=drop
table=0,arp,action=normal
table=0,in_port=1,tcp,ct_state=-trk,action=ct(commit,zone=9),2
table=0,in_port=2,tcp,ct_state=-trk,action=ct(zone=9,table=1)
table=1,in_port=2,ct_state=+trk+est,tcp,action=1
table=1,in_port=2,ct_state=+trk+new,tcp,action=drop
Based on original design by Justin Pettit, contributions from Thomas
Graf and Daniele Di Proietto.
Signed-off-by: Joe Stringer <joestringer@nicira.com>
Acked-by: Jarno Rajahalme <jrajahalme@nicira.com>
Acked-by: Ben Pfaff <blp@nicira.com>
2015-08-11 10:56:09 -07:00
|
|
|
#
|
|
|
|
m4_define([FORMAT_CT],
|
2016-06-20 18:51:06 -07:00
|
|
|
[[grep "dst=$1" | sed -e 's/port=[0-9]*/port=<cleared>/g' -e 's/id=[0-9]*/id=<cleared>/g' -e 's/state=[0-9_A-Z]*/state=<cleared>/g' | sort | uniq]])
|
Add support for connection tracking.
This patch adds a new action and fields to OVS that allow connection
tracking to be performed. This support works in conjunction with the
Linux kernel support merged into the Linux-4.3 development cycle.
Packets have two possible states with respect to connection tracking:
Untracked packets have not previously passed through the connection
tracker, while tracked packets have previously been through the
connection tracker. For OpenFlow pipeline processing, untracked packets
can become tracked, and they will remain tracked until the end of the
pipeline. Tracked packets cannot become untracked.
Connections can be unknown, uncommitted, or committed. Packets which are
untracked have unknown connection state. To know the connection state,
the packet must become tracked. Uncommitted connections have no
connection state stored about them, so it is only possible for the
connection tracker to identify whether they are a new connection or
whether they are invalid. Committed connections have connection state
stored beyond the lifetime of the packet, which allows later packets in
the same connection to be identified as part of the same established
connection, or related to an existing connection - for instance ICMP
error responses.
The new 'ct' action transitions the packet from "untracked" to
"tracked" by sending this flow through the connection tracker.
The following parameters are supported initally:
- "commit": When commit is executed, the connection moves from
uncommitted state to committed state. This signals that information
about the connection should be stored beyond the lifetime of the
packet within the pipeline. This allows future packets in the same
connection to be recognized as part of the same "established" (est)
connection, as well as identifying packets in the reply (rpl)
direction, or packets related to an existing connection (rel).
- "zone=[u16|NXM]": Perform connection tracking in the zone specified.
Each zone is an independent connection tracking context. When the
"commit" parameter is used, the connection will only be committed in
the specified zone, and not in other zones. This is 0 by default.
- "table=NUMBER": Fork pipeline processing in two. The original instance
of the packet will continue processing the current actions list as an
untracked packet. An additional instance of the packet will be sent to
the connection tracker, which will be re-injected into the OpenFlow
pipeline to resume processing in the specified table, with the
ct_state and other ct match fields set. If the table is not specified,
then the packet is submitted to the connection tracker, but the
pipeline does not fork and the ct match fields are not populated. It
is strongly recommended to specify a table later than the current
table to prevent loops.
When the "table" option is used, the packet that continues processing in
the specified table will have the ct_state populated. The ct_state may
have any of the following flags set:
- Tracked (trk): Connection tracking has occurred.
- Reply (rpl): The flow is in the reply direction.
- Invalid (inv): The connection tracker couldn't identify the connection.
- New (new): This is the beginning of a new connection.
- Established (est): This is part of an already existing connection.
- Related (rel): This connection is related to an existing connection.
For more information, consult the ovs-ofctl(8) man pages.
Below is a simple example flow table to allow outbound TCP traffic from
port 1 and drop traffic from port 2 that was not initiated by port 1:
table=0,priority=1,action=drop
table=0,arp,action=normal
table=0,in_port=1,tcp,ct_state=-trk,action=ct(commit,zone=9),2
table=0,in_port=2,tcp,ct_state=-trk,action=ct(zone=9,table=1)
table=1,in_port=2,ct_state=+trk+est,tcp,action=1
table=1,in_port=2,ct_state=+trk+new,tcp,action=drop
Based on original design by Justin Pettit, contributions from Thomas
Graf and Daniele Di Proietto.
Signed-off-by: Joe Stringer <joestringer@nicira.com>
Acked-by: Jarno Rajahalme <jrajahalme@nicira.com>
Acked-by: Ben Pfaff <blp@nicira.com>
2015-08-11 10:56:09 -07:00
|
|
|
|
|
|
|
# NETNS_DAEMONIZE([namespace], [command], [pidfile])
|
|
|
|
#
|
|
|
|
# Run 'command' as a background process within 'namespace' and record its pid
|
|
|
|
# to 'pidfile' to allow cleanup on exit.
|
|
|
|
#
|
|
|
|
m4_define([NETNS_DAEMONIZE],
|
|
|
|
[ip netns exec $1 $2 & echo $! > $3
|
|
|
|
echo "kill \`cat $3\`" >> cleanup
|
|
|
|
]
|
|
|
|
)
|
2015-12-22 16:47:26 -08:00
|
|
|
|
|
|
|
# OVS_CHECK_VXLAN()
|
|
|
|
#
|
|
|
|
# Do basic check for vxlan functionality, skip the test if it's not there.
|
|
|
|
m4_define([OVS_CHECK_VXLAN],
|
|
|
|
[AT_SKIP_IF([! ip link add foo type vxlan help 2>&1 | grep dstport >/dev/null])])
|
2016-04-20 16:07:51 -07:00
|
|
|
|
|
|
|
# OVS_CHECK_GRE()
|
|
|
|
m4_define([OVS_CHECK_GRE],
|
|
|
|
[AT_SKIP_IF([! ip link add foo type gretap help 2>&1 | grep gre >/dev/null])])
|
2016-04-20 16:07:52 -07:00
|
|
|
|
|
|
|
# OVS_CHECK_GENEVE()
|
|
|
|
m4_define([OVS_CHECK_GENEVE],
|
|
|
|
[AT_SKIP_IF([! ip link add foo type geneve help 2>&1 | grep geneve >/dev/null])])
|