| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
Added a unit test case for testing the condition when a veth interface
is added to br0 and then the veth interface is deleted from the
system and added back with the same name.
Signed-off-by: Ashish Varma <ashishvarma.ovs@gmail.com>
Signed-off-by: Ben Pfaff <blp@ovn.org>
Acked-by: Yi-Hung Wei <yihung.wei@gmail.com>
|
| |
|
|
|
|
|
| |
This also adds a new autotest file specifically for layer3 tunnels.
Signed-off-by: Eric Garver <e@erig.me>
Signed-off-by: Joe Stringer <joe@ovn.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First and second unit tests perform basic verification.
The third one is a triangular bridge setup test case. It tests dataplane
in non-PTAP and ptap bridges in conjunction with L2 and L3 GRE tunnels.
It uses veth ports, therefore requires root privileges.
A simplified version of the third test is added to system userspace unit tests.
GRE tunneling test setup for PTAP bridge
192.168.10.10 192.168.10.20 192.168.10.30
n1 n2 n3
| | |
+------o------+ +------o------+ +------o------+
| br-in1 | | br-in2 | | br-in3 |
| | | (PTAP) | | |
+------o------+ +------o------+ +------o------+
gre gre gre
10.0.0.1 (10.0.0.2) (10.0.0.3)
(20.0.0.1) 20.0.0.2 (20.0.0.3)
(30.0.0.1) LOCAL (30.0.0.2) LOCAL 30.0.0.3 LOCAL
+-----------o-+ +-----------o-+ +-----------o-+
| br-p1 | | br-p2 | | br-p3 |
+------o------+ +------o------+ +------o------+
p1-0 | | p2-0 | p3-0
p0-1 | | p0-2 | p0-3
+--o------------------------o-------------------------o--+
| br0 |
+--------------------------------------------------------+
GRE tunnel ports:
No Bridge Name Packet-Type Remote bridge & ports
-----------------------------------------------------------------------
1020 br-in1 gre-12 legacy-l2 br-in2 2010 (ptap)
1021 br-in1 gre-12_l3 legacy-l3 same
1030 br-in1 gre-13 legacy-l2 br-in3 3010 (l2)
2010 br-in2 gre-21 ptap br-in1 1020 (l2), 1021 (l3)
2030 br-in2 gre-23 ptap br-in3 3020 (l2), 3021 (l3)
3010 br-in1 gre-31 legacy-l2 br-in1 1030 (l2)
3020 br-in1 gre-32 legacy-l2 br-in2 2010 (ptap)
3021 br-in1 gre-32_l3 legacy-l3 same
Signed-off-by: Jan Scheurich <jan.scheurich@ericsson.com>
Signed-off-by: Ben Pfaff <blp@ovn.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This unit test adds a basic OVN NAT test that tests north-south
DNAT, south-north SNAT and east-west DNAT and SNAT. It uses network
namespaces connected to br-int using veth pairs to act as logical
ports. This test does not cover multi-host scenarios, so there is
a gap. But userspace OVN tests do multi-host scenarios (without NAT
testing), so it should still be a decent coverage.
Signed-off-by: Gurucharan Shetty <guru@ovn.org>
Acked-by: Joe Stringer <joe@ovn.org>
|
| |
|
|
|
|
|
|
| |
Reference thread in mailing list:
http://openvswitch.org/pipermail/discuss/2016-May/021339.html
Signed-off-by: Flavio Fernandes <flavio@flaviof.com>
Signed-off-by: Ben Pfaff <blp@ovn.org>
|
|
|
The new system-userspace-testsuite, which can be launched via
`make check-system-userspace`, reuses the kmod tests on the userspace
datapath.
The userspace datapath is already tested by the main testsuite (and
that's not going to change), but having also the
system-userspace-testsuite has the following advantages:
* More complicated tests are possible: real client and server
applications can be used.
* The same tests run on both kernel and userspace datapath: this gives
us an easy way to make sure that the behaviour is consistent (e.g.
with the upcoming connection tracker integration)
The userspace datapath is able to use system network interfaces via an
AF_PACKET socket.
Signed-off-by: Daniele Di Proietto <diproiettod@vmware.com>
Acked-by: Joe Stringer <joestringer@nicira.com>
|
