X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=utilities%2Fovs-vsctl.8.in;h=7c01d0bd749513a5ebb76cd4dd2d5e2d15d5abd3;hb=c532bf9dd4e684bc583debc9618e3210334f8081;hp=16fd8497438957539dba1688dfc54e3e15832270;hpb=5aa006354872e40c227b601f0e0deb4fd72eb9f6;p=openvswitch diff --git a/utilities/ovs-vsctl.8.in b/utilities/ovs-vsctl.8.in index 16fd8497..7c01d0bd 100644 --- a/utilities/ovs-vsctl.8.in +++ b/utilities/ovs-vsctl.8.in @@ -74,11 +74,9 @@ contacts to query or modify configuration. The default is \fBunix:@RUNDIR@/ovsdb\-server\fR. \fIserver\fR must take one of the following forms: .RS -.IP "\fBtcp:\fIip\fB:\fIport\fR" -Connect to the given TCP \fIport\fR on \fIip\fR. -.IP "\fBunix:\fIfile\fR" -Connect to the Unix domain server socket named \fIfile\fR. +.so ovsdb/remote-active.man .RE +. .IP "\fB\-\-no\-wait\fR" Prevents \fBovs\-vsctl\fR from waiting for \fBovs\-vswitchd\fR to reconfigure itself according to the the modified database. This @@ -114,6 +112,7 @@ zero will cause \fBovs\-vsctl\fR to wait forever. If the timeout expires, not used, \fBovs\-vsctl\fR uses a timeout of five seconds. (A timeout would normally happen only if the database cannot be contacted.) . +.so lib/ssl.man .so lib/vlog.man . .SH COMMANDS @@ -296,20 +295,9 @@ the following forms: . .RS .TP -\fBssl:\fIip\fR[\fB:\fIport\fR] -The specified SSL \fIport\fR (default: 6633) on the host at the given -\fIip\fR, which must be expressed as an IP address (not a DNS name). -SSL must be configured when this form is used (see \fBSSL -Configuration\fR, below). -. -.TP -\fBtcp:\fIip\fR[\fB:\fIport\fR] -The specified TCP \fIport\fR (default: 6633) on the host at the given -\fIip\fR, which must be expressed as an IP address (not a DNS name). -.TP -\fBunix:\fIfile\fR -The Unix domain server socket named \fIfile\fR. +.so lib/vconn-active.man .RE +. .ST "Controller Failure Settings" . When a controller is configured, it is, ordinarily, responsible for @@ -340,6 +328,60 @@ Deletes the configured failure mode. .IP "\fBset\-fail\-mode\fR [\fIbridge\fR] \fBstandalone\fR|\fBsecure\fR" Sets the configured failure mode. . +.SS "SSL Configuration" +When \fBovs\-vswitchd\fR is configured to connect over SSL for management or +controller connectivity, the following parameters are required: +.TP +\fBprivate-key\fR +Specifies a PEM file containing the private key used as the virtual +switch's identity for SSL connections to the controller. +.TP +\fBcertificate\fR +Specifies a PEM file containing a certificate, signed by the +certificate authority (CA) used by the controller and manager, that +certifies the virtual switch's private key, identifying a trustworthy +switch. +.TP +\fBca-cert\fR +Specifies a PEM file containing the CA certificate used to verify that +the virtual switch is connected to a trustworthy controller. +.PP +These files are read only once, at \fBovs\-vswitchd\fR startup time. If +their contents change, \fBovs\-vswitchd\fR must be killed and restarted. +.PP +These SSL settings apply to all SSL connections made by the virtual +switch. +. +.IP "\fBget\-ssl\fR" +Prints the SSL configuration. +. +.IP "\fBdel\-ssl\fR" +Deletes the current SSL configuration. +. +.IP "[\fB\-\-bootstrap\fR] \fBset\-ssl\fR \fIprivate-key\fR \fIcertificate\fR \fIca-cert\fR" +Sets the SSL configuration. The \fB\-\-bootstrap\fR option is described +below. +. +.ST "CA Certificate Bootstrap" +Ordinarily, all of the files named in the SSL configuration must exist +when \fBovs\-vswitchd\fR starts. However, if the \fB\-\-bootstrap\fR +option is given, then \fBovs\-vswitchd\fR will attempt to obtain the +CA certificate from the controller on its first SSL connection and +save it to the named PEM file. If it is successful, it will +immediately drop the connection and reconnect, and from then on all +SSL connections must be authenticated by a certificate signed by the +CA certificate thus obtained. +.PP +\fBThis option exposes the SSL connection to a man-in-the-middle +attack obtaining the initial CA certificate\fR, but it may be useful +for bootstrapping. +.PP +This option is only useful if the controller sends its CA certificate +as part of the SSL certificate chain. The SSL protocol does not +require the controller to send the CA certificate, but +\fBcontroller\fR(8) can be configured to do so with the +\fB--peer-ca-cert\fR option. +. .SH "EXAMPLES" Create a new bridge named br0 and add port eth0 to it: .IP