mirror of
https://github.com/openvswitch/ovs
synced 2025-08-22 01:51:26 +00:00
49f299313d
SSL protocol family is not actually being used or supported in OVS. What we use is actually TLS. Terms "SSL" and "TLS" are often used interchangeably in modern software and refer to the same thing, which is normally just TLS. Let's replace "SSL" with "SSL/TLS" in documentation and user-visible messages, where it makes sense. This may make it more clear what is meant for a less experienced user that may look for TLS support in OVS and not find much. We're not changing any actual code, because, for example, most of OpenSSL APIs are using just SSL, for historical reasons. And our database is using "SSL" table. We may consider migrating to "TLS" naming for user-visible configuration like command line arguments and database names, but that will require extra work on making sure upgrades can still work. In general, a slightly more clear documentation should be enough for now, especially since term SSL is still widely used in the industry. "SSL/TLS" is chosen over "TLS/SSL" simply because our user-visible configuration knobs are using "SSL" naming, e.g. '--ssl-cyphers' or 'ovs-vsctl set-ssl'. So, it might be less confusing this way. We may switch that, if we decide on re-working the user-visible commands towards "TLS" naming, or providing both alternatives. Some other projects did similar changes. For example, the python ssl library is now using "TLS/SSL" in the documentation whenever possible. Same goes for OpenSSL itself. Acked-by: Eelco Chaudron <echaudro@redhat.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
Here's an example configuration for your /etc/network/interfaces
using a simple ovsbr0 bridge for eth0, with dhcp for ipv4 and ipv6.
This was taken from https://bugs.debian.org/860786.
auto ovsbr0
iface ovsbr0 inet dhcp
ovs_type OVSBridge
ovs_ports eth0
auto ovsbr0
iface ovsbr0 inet6 dhcp
ovs_type OVSBridge
ovs_ports eth0
autobr0 eth0
iface eth0 inet manual
ovs_bridge ovsbr0
ovs_type OVSPort
However, this didn't work for me. Instead, this worked:
auto br0
iface br0 inet dhcp
ovs_type OVSBridge
ovs_port enp0s3
auto enp0s3
iface enp0s3 inet manual
ovs_bridge br0
ovs_type OVSPort
up ip address add 0/0 dev enp0s3
up ip link set enp0s3 up
up dhclient br0
down ip link set enp0s3 down
-- Antoine Beaupré <anarcat@debian.org>, Wed, 22 Jun 2022 12:02:39 -0400