From 2264b0323b01e4e22c955a7b6b752508ef15c46f Mon Sep 17 00:00:00 2001 From: Marius Kittler Date: Tue, 23 Jan 2024 17:06:56 +0100 Subject: [PATCH] Document debugging problematic connections in the GRE network * As it was done in https://progress.opensuse.org/issues/152389 * See https://progress.opensuse.org/issues/135914 --- docs/Networking.asciidoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/Networking.asciidoc b/docs/Networking.asciidoc index fd10be7f64d..87fd09c1874 100644 --- a/docs/Networking.asciidoc +++ b/docs/Networking.asciidoc @@ -245,7 +245,9 @@ After this it should be possible to reach other hosts. You may also launch a 2nd VM to see whether the VMs can talk to each other. You may conduct ping tests similar to the `ping_client` test mentioned in the previous section (see the https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/cc3a5b32527c4c8bb810c8bce9b1449a891ef74b/lib/utils.pm#L2901[utility function in openSUSE tests] -for details). +for details). When running ping you can add/remove machines to/from the GRE +network to bisect problematic hosts/connections (via `ovs-vsctl add-port …` and +`ovs-vsctl del-port …`). === Debugging Open vSwitch Configuration Boot sequence with wicked (version 0.6.23 and newer):