/openflow-pki
/openflow-pki-server
/openflow-switch
+/openflow-switch-config
/openflow-switch.copyright
/openflow-switchmon
/openflow-switchmon.copyright
/openflow-switchmon.dirs
/openflow-switchmon.init
/openflow-switchmon.install
+/rules.ext
Package: openflow-switch
Architecture: any
Suggests: openflow-datapath-module
-Depends: ${shlibs:Depends}, ${misc:Depends}, openflow-common, libwww-perl, libdigest-sha1-perl, dhcp3-client
+Depends: ${shlibs:Depends}, ${misc:Depends}, openflow-common, dhcp3-client
Description: OpenFlow switch implementations
openflow-switch provides the userspace components and utilities for
- the OpenFlow kernel-based switch. It also includes a userspace-only
- implementation of an OpenFlow switch.
+ the OpenFlow kernel-based switch.
+ .
+ OpenFlow is a protocol for flow-based control over network switching.
+
+Package: openflow-switch-config
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}, openflow-switch, libwww-perl, libdigest-sha1-perl
+Description: OpenFlow switch implementations
+ openflow-switch-config provides a utility for interactively configuring
+ the OpenFlow switch provided in the openflow-switch package.
.
OpenFlow is a protocol for flow-based control over network switching.
--- /dev/null
+/usr/share/lintian/overrides
--- /dev/null
+debian/ofp-switch-setup usr/sbin
--- /dev/null
+debian/ofp-switch-setup.8
--- /dev/null
+debconf-is-not-a-registry
--- /dev/null
+Template: openflow-switch/netdevs
+Type: multiselect
+_Choices: ${choices}
+_Description: OpenFlow switch network devices:
+ Choose the network devices that should become part of the OpenFlow
+ switch. At least two devices must be selected for this machine to be
+ a useful switch. Unselecting all network devices will disable the
+ OpenFlow switch entirely.
+ .
+ The network devices that you select should not be configured with IP
+ or IPv6 addresses, even if the switch contacts the controller over
+ one of the selected network devices. This is because a running
+ OpenFlow switch takes over network devices at a low level: they
+ become part of the switch and cannot be used for other purposes.
+
+Template: openflow-switch/no-netdevs
+Type: error
+_Description: No network devices were selected.
+ No network devices were selected for inclusion in the OpenFlow switch.
+ The switch will be disabled.
+
+Template: openflow-switch/configured-netdevs
+Type: note
+_Description: Some Network Devices Have IP or IPv6 Addresses
+ The following network devices selected to be part of the OpenFlow switch
+ have IP or IPv6 addresses configured:
+ .
+ ${configured-netdevs}
+ .
+ This is usually a mistake, even if the switch contacts the controller over
+ one of the selected network devices. This is because a running
+ OpenFlow switch takes over network devices at a low level: they
+ become part of the switch and cannot be used for other purposes.
+ .
+ If this is an unintentional mistake, move back and fix the selection,
+ or de-configure the IP or IPv6 from these network devices.
+
+Template: openflow-switch/mode
+Type: select
+_Choices: discovery, in-band, out-of-band
+Default: discovery
+_Description: Switch-to-controller access method:
+ The OpenFlow switch must be able to contact the OpenFlow controller over
+ the network. It can do so in one of three ways:
+ .
+ discovery: A single network is used for OpenFlow traffic and other
+ data traffic; that is, the switch contacts the controller over one of
+ the network devices selected as OpenFlow switch network devices in
+ the previous question. The switch automatically determines the
+ location of the controller using a DHCP request with an
+ OpenFlow-specific vendor option. This is the most common case.
+ .
+ in-band: As above, but the location of the controller is manually
+ configured.
+ .
+ out-of-band: OpenFlow traffic uses a network separate from the data traffic
+ that it controls. If this is the case, the control network must already
+ be configured on a network device other than one of those selected as
+ an OpenFlow switch netdev in the previous question.
+
+Template: openflow-switch/discover
+Type: note
+_Description: Preparing to discover controller.
+ The setup program will now attempt to discover the OpenFlow controller.
+ Controller discovery may take up to 30 seconds. Please be patient.
+ .
+ See secchan(8) for instructions on how to configure a DHCP server for
+ controller discovery.
+
+Template: openflow-switch/discovery-failure
+Type: error
+_Description: Controller discovery failed.
+ The controller's location could not be determined automatically.
+ .
+ Ensure that the OpenFlow DHCP server is properly configured. See
+ secchan(8) for instructions on how to configure a DHCP server for
+ controller discovery.
+
+Template: openflow-switch/discovery-success
+Type: boolean
+Default: true
+_Description: Use discovered settings?
+ Controller discovery obtained the following settings:
+ .
+ Controller location: ${controller-vconn}
+ .
+ PKI URL: ${pki-uri}
+ .
+ Please verify that these settings are correct.
+
+Template: openflow-switch/switch-ip
+Type: string
+Default: dhcp
+_Description: Switch IP address:
+ For in-band communication with the controller, the OpenFlow switch must
+ be able to determine its own IP address. Its IP address may be configured
+ statically or dynamically.
+ .
+ For static configuration, specify the switch's IP address as a string.
+ .
+ For dynamic configuration with DHCP (the most common case), specify "dhcp".
+ Configuration with DHCP will only work reliably if the network topology
+ allows the switch to contact the DHCP server before it connects to the
+ OpenFlow controller.
+
+Template: openflow-switch/switch-ip-error
+Type: error
+_Description: The switch IP address is invalid.
+ The switch IP address must specified as "dhcp" or a valid IP address in
+ dotted-octet form (e.g. "1.2.3.4").
+
+Template: openflow-switch/controller-vconn
+Type: string
+_Description: Controller location:
+ Specify how the OpenFlow switch should connect to the OpenFlow controller.
+ The value should be in form "ssl:HOST[:PORT]" to connect to the controller
+ over SSL (recommended for security) or "tcp:HOST[:PORT]" to connect over
+ cleartext TCP.
+
+Template: openflow-switch/controller-vconn-error
+Type: error
+_Description: The controller location is invalid.
+ The controller location must be specifed as "ssl:HOST[:PORT]" to
+ connect to the controller over SSL (recommended for security) or
+ "tcp:HOST[:PORT]" to connect over cleartext TCP.
+
+Template: openflow-switch/pki-uri
+Type: string
+_Description: OpenFlow PKI server host name or URL:
+ Specify a URL to the OpenFlow public key infrastructure (PKI). If a
+ host name or IP address is specified in place of a URL, then
+ http://<host>/openflow/pki/ will be used,
+ where <host> is the specified host name or IP address.
+ .
+ The OpenFlow PKI is usually on the same machine as the OpenFlow
+ controller.
+ .
+ The setup process will connect to the OpenFlow PKI server over
+ HTTP, using the system's configured default HTTP proxy (if any).
+
+Template: openflow-switch/fetch-cacert-failed
+Type: error
+_Description: The switch CA certificate could not be retrieved.
+ Retrieval of ${url} failed, with the following status: "${error}".
+ .
+ Ensure that the OpenFlow PKI server is correctly configured and
+ available at ${pki-uri}. If the system is configured to use an HTTP
+ proxy, also make sure that the HTTP proxy is available and that the
+ PKI server can be reached through it.
+
+Template: openflow-switch/verify-controller-ca
+Type: select
+_Choices: yes, no
+Default: yes
+_Description: Is ${fingerprint} the controller CA's fingerprint?
+ If a man-in-the-middle attack is possible in your network
+ environment, check that the controller CA's fingerprint is really
+ ${fingerprint}. Answer "yes" if it matches, "no" if
+ there is a discrepancy.
+ .
+ If a man-in-the-middle attack is not a concern, there is no need to
+ verify the fingerprint. Simply answer "yes".
+
+Template: openflow-switch/send-cert-req
+Type: select
+_Choices: yes, no
+Default: yes
+_Description: Send certificate request to switch CA?
+ Before it can connect to the controller over SSL, the OpenFlow
+ switch's key must be signed by the switch certificate authority (CA)
+ located on the OpenFlow PKI server, which is usually collocated with
+ the OpenFlow controller. A signing request can be sent to the PKI
+ server now.
+ .
+ Answer "yes" to send a signing request to the switch CA now. This is
+ ordinarily the correct choice. There is no harm in sending a given
+ signing request more than once.
+ .
+ Answer "no" to skip sending a signing request to the switch CA.
+ Unless the request has already been sent to the switch CA, manual
+ sending of the request and signing will be necessary.
+
+Template: openflow-switch/send-cert-req-failed
+Type: error
+_Description: The certificate request could not be sent.
+ Posting to ${url} failed, with the following status: "${error}".
+ .
+ Ensure that the OpenFlow PKI server is correctly configured and
+ available at ${pki-uri}.
+
+Template: openflow-switch/fetch-switch-cert
+Type: select
+_Choices: yes, no
+_Description: Fetch signed switch certificate from PKI server?
+ Before it can connect to the controller over SSL, the OpenFlow
+ switch's key must be signed by the switch certificate authority (CA)
+ located on the OpenFlow PKI server, which is usually collocated with
+ the OpenFlow controller.
+ .
+ At this point, a signing request has been sent to the switch CA (or
+ sending a request has been manually skipped), but the signed
+ certificate has not yet been retrieved. Manual action may need to be
+ taken at the PKI server to approve the signing request.
+ .
+ Answer "yes" to attempt to retrieve the signed switch certificate
+ from the switch CA. If the switch certificate request has been
+ signed at the PKI server, this is the correct choice.
+ .
+ Answer "no" to postpone switch configuration. The configuration
+ process must be restarted later, when the switch certificate request
+ has been signed.
+
+Template: openflow-switch/fetch-switch-cert-failed
+Type: error
+_Description: Signed switch certificate could not be retrieved.
+ The signed switch certificate could not be retrieved from the switch
+ CA: retrieval of ${url} failed, with the following status: "${error}".
+ .
+ This probably indicates that the switch's certificate request has not
+ yet been signed. If this is the problem, it may be fixed by signing
+ the certificate request at ${pki-uri}, then trying to fetch the
+ signed switch certificate again.
+
+Template: openflow-switch/complete
+Type: note
+_Description: OpenFlow Switch Setup Finished
+ Setup of this OpenFlow switch is finished. Complete the setup procedure
+ to enable the switch.
---------------------------------
* The switch must be configured before it can be used. To configure
- it interactively, run the ofp-switch-setup program. Alternatively,
- edit /etc/default/openflow-switch by hand, then start the switch
- manually with "/etc/init.d/openflow-switch start".
+ it interactively, install the openflow-switch-config package and run
+ the ofp-switch-setup program. Alternatively, edit
+ /etc/default/openflow-switch by hand, then start the switch manually
+ with "/etc/init.d/openflow-switch start".
* To use the Linux kernel-based switch implementation, you will need
to build and install the OpenFlow kernel module. To do so, install
# uncomment them. Afterward, the secure channel will come up
# automatically at boot time. It can be started immediately with
# /etc/init.d/openflow-switch start
-# Alternatively, use the ofp-switch-setup program to do everything
-# automatically.
+# Alternatively, use the ofp-switch-setup program (from the
+# openflow-switch-config package) to do everything automatically.
# NETDEVS: Which network devices should the OpenFlow switch include?
#
/etc/openflow-switch
-/usr/share/lintian/overrides
if test ! -e "$CACERT" && test "$CACERT_MODE" != bootstrap; then
echo "$CACERT: CA certificate missing (and CA certificate bootstrapping not enabled)" >&2
fi
- echo "Run ofp-switch-setup or edit /etc/default/openflow-switch to configure" >&2
+ echo "Run ofp-switch-setup (in the openflow-switch-config package) or edit /etc/default/openflow-switch to configure" >&2
if test "$MODE" = discovery; then
echo "You may also delete or rename $PRIVKEY to disable SSL requirement" >&2
fi
start)
if test -z "$NETDEVS"; then
echo "$default: No network devices configured, switch disabled" >&2
- echo "Run ofp-switch-setup or edit /etc/default/openflow-switch to configure" >&2
+ echo "Run ofp-switch-setup (in the openflow-switch-config package) or edit /etc/default/openflow-switch to configure" >&2
exit 0
fi
if test "$MODE" = discovery; then
elif test "$MODE" = in-band || test "$MODE" = out-of-band; then
if test -z "$CONTROLLER"; then
echo "$default: No controller configured and not configured for discovery, switch disabled" >&2
- echo "Run ofp-switch-setup or edit /etc/default/openflow-switch to configure" >&2
+ echo "Run ofp-switch-setup (in the openflow-switch-config package) or edit /etc/default/openflow-switch to configure" >&2
exit 0
fi
else
echo "$default: MODE must set to 'discovery', 'in-band', or 'out-of-band'" >&2
- echo "Run ofp-switch-setup or edit /etc/default/openflow-switch to configure" >&2
+ echo "Run ofp-switch-setup (in the openflow-switch-config package) or edit /etc/default/openflow-switch to configure" >&2
exit 1
fi
: ${PRIVKEY:=/etc/openflow-switch/of0-privkey.pem}
;;
*)
echo "$default: CONTROLLER must be in the form 'ssl:HOST[:PORT]' or 'tcp:HOST[:PORT]' when not in discovery mode" >&2
- echo "Run ofp-switch-setup or edit /etc/default/openflow-switch to configure" >&2
+ echo "Run ofp-switch-setup (in the openflow-switch-config package) or edit /etc/default/openflow-switch to configure" >&2
exit 1
esac
+++ /dev/null
-/usr/share/modass/packages/default.sh /usr/share/modass/packages/openflow-datapath-source
+++ /dev/null
-debconf-is-not-a-registry
+++ /dev/null
-Template: openflow-switch/netdevs
-Type: multiselect
-_Choices: ${choices}
-_Description: OpenFlow switch network devices:
- Choose the network devices that should become part of the OpenFlow
- switch. At least two devices must be selected for this machine to be
- a useful switch. Unselecting all network devices will disable the
- OpenFlow switch entirely.
- .
- The network devices that you select should not be configured with IP
- or IPv6 addresses, even if the switch contacts the controller over
- one of the selected network devices. This is because a running
- OpenFlow switch takes over network devices at a low level: they
- become part of the switch and cannot be used for other purposes.
-
-Template: openflow-switch/no-netdevs
-Type: error
-_Description: No network devices were selected.
- No network devices were selected for inclusion in the OpenFlow switch.
- The switch will be disabled.
-
-Template: openflow-switch/configured-netdevs
-Type: note
-_Description: Some Network Devices Have IP or IPv6 Addresses
- The following network devices selected to be part of the OpenFlow switch
- have IP or IPv6 addresses configured:
- .
- ${configured-netdevs}
- .
- This is usually a mistake, even if the switch contacts the controller over
- one of the selected network devices. This is because a running
- OpenFlow switch takes over network devices at a low level: they
- become part of the switch and cannot be used for other purposes.
- .
- If this is an unintentional mistake, move back and fix the selection,
- or de-configure the IP or IPv6 from these network devices.
-
-Template: openflow-switch/mode
-Type: select
-_Choices: discovery, in-band, out-of-band
-Default: discovery
-_Description: Switch-to-controller access method:
- The OpenFlow switch must be able to contact the OpenFlow controller over
- the network. It can do so in one of three ways:
- .
- discovery: A single network is used for OpenFlow traffic and other
- data traffic; that is, the switch contacts the controller over one of
- the network devices selected as OpenFlow switch network devices in
- the previous question. The switch automatically determines the
- location of the controller using a DHCP request with an
- OpenFlow-specific vendor option. This is the most common case.
- .
- in-band: As above, but the location of the controller is manually
- configured.
- .
- out-of-band: OpenFlow traffic uses a network separate from the data traffic
- that it controls. If this is the case, the control network must already
- be configured on a network device other than one of those selected as
- an OpenFlow switch netdev in the previous question.
-
-Template: openflow-switch/discover
-Type: note
-_Description: Preparing to discover controller.
- The setup program will now attempt to discover the OpenFlow controller.
- Controller discovery may take up to 30 seconds. Please be patient.
- .
- See secchan(8) for instructions on how to configure a DHCP server for
- controller discovery.
-
-Template: openflow-switch/discovery-failure
-Type: error
-_Description: Controller discovery failed.
- The controller's location could not be determined automatically.
- .
- Ensure that the OpenFlow DHCP server is properly configured. See
- secchan(8) for instructions on how to configure a DHCP server for
- controller discovery.
-
-Template: openflow-switch/discovery-success
-Type: boolean
-Default: true
-_Description: Use discovered settings?
- Controller discovery obtained the following settings:
- .
- Controller location: ${controller-vconn}
- .
- PKI URL: ${pki-uri}
- .
- Please verify that these settings are correct.
-
-Template: openflow-switch/switch-ip
-Type: string
-Default: dhcp
-_Description: Switch IP address:
- For in-band communication with the controller, the OpenFlow switch must
- be able to determine its own IP address. Its IP address may be configured
- statically or dynamically.
- .
- For static configuration, specify the switch's IP address as a string.
- .
- For dynamic configuration with DHCP (the most common case), specify "dhcp".
- Configuration with DHCP will only work reliably if the network topology
- allows the switch to contact the DHCP server before it connects to the
- OpenFlow controller.
-
-Template: openflow-switch/switch-ip-error
-Type: error
-_Description: The switch IP address is invalid.
- The switch IP address must specified as "dhcp" or a valid IP address in
- dotted-octet form (e.g. "1.2.3.4").
-
-Template: openflow-switch/controller-vconn
-Type: string
-_Description: Controller location:
- Specify how the OpenFlow switch should connect to the OpenFlow controller.
- The value should be in form "ssl:HOST[:PORT]" to connect to the controller
- over SSL (recommended for security) or "tcp:HOST[:PORT]" to connect over
- cleartext TCP.
-
-Template: openflow-switch/controller-vconn-error
-Type: error
-_Description: The controller location is invalid.
- The controller location must be specifed as "ssl:HOST[:PORT]" to
- connect to the controller over SSL (recommended for security) or
- "tcp:HOST[:PORT]" to connect over cleartext TCP.
-
-Template: openflow-switch/pki-uri
-Type: string
-_Description: OpenFlow PKI server host name or URL:
- Specify a URL to the OpenFlow public key infrastructure (PKI). If a
- host name or IP address is specified in place of a URL, then
- http://<host>/openflow/pki/ will be used,
- where <host> is the specified host name or IP address.
- .
- The OpenFlow PKI is usually on the same machine as the OpenFlow
- controller.
- .
- The setup process will connect to the OpenFlow PKI server over
- HTTP, using the system's configured default HTTP proxy (if any).
-
-Template: openflow-switch/fetch-cacert-failed
-Type: error
-_Description: The switch CA certificate could not be retrieved.
- Retrieval of ${url} failed, with the following status: "${error}".
- .
- Ensure that the OpenFlow PKI server is correctly configured and
- available at ${pki-uri}. If the system is configured to use an HTTP
- proxy, also make sure that the HTTP proxy is available and that the
- PKI server can be reached through it.
-
-Template: openflow-switch/verify-controller-ca
-Type: select
-_Choices: yes, no
-Default: yes
-_Description: Is ${fingerprint} the controller CA's fingerprint?
- If a man-in-the-middle attack is possible in your network
- environment, check that the controller CA's fingerprint is really
- ${fingerprint}. Answer "yes" if it matches, "no" if
- there is a discrepancy.
- .
- If a man-in-the-middle attack is not a concern, there is no need to
- verify the fingerprint. Simply answer "yes".
-
-Template: openflow-switch/send-cert-req
-Type: select
-_Choices: yes, no
-Default: yes
-_Description: Send certificate request to switch CA?
- Before it can connect to the controller over SSL, the OpenFlow
- switch's key must be signed by the switch certificate authority (CA)
- located on the OpenFlow PKI server, which is usually collocated with
- the OpenFlow controller. A signing request can be sent to the PKI
- server now.
- .
- Answer "yes" to send a signing request to the switch CA now. This is
- ordinarily the correct choice. There is no harm in sending a given
- signing request more than once.
- .
- Answer "no" to skip sending a signing request to the switch CA.
- Unless the request has already been sent to the switch CA, manual
- sending of the request and signing will be necessary.
-
-Template: openflow-switch/send-cert-req-failed
-Type: error
-_Description: The certificate request could not be sent.
- Posting to ${url} failed, with the following status: "${error}".
- .
- Ensure that the OpenFlow PKI server is correctly configured and
- available at ${pki-uri}.
-
-Template: openflow-switch/fetch-switch-cert
-Type: select
-_Choices: yes, no
-_Description: Fetch signed switch certificate from PKI server?
- Before it can connect to the controller over SSL, the OpenFlow
- switch's key must be signed by the switch certificate authority (CA)
- located on the OpenFlow PKI server, which is usually collocated with
- the OpenFlow controller.
- .
- At this point, a signing request has been sent to the switch CA (or
- sending a request has been manually skipped), but the signed
- certificate has not yet been retrieved. Manual action may need to be
- taken at the PKI server to approve the signing request.
- .
- Answer "yes" to attempt to retrieve the signed switch certificate
- from the switch CA. If the switch certificate request has been
- signed at the PKI server, this is the correct choice.
- .
- Answer "no" to postpone switch configuration. The configuration
- process must be restarted later, when the switch certificate request
- has been signed.
-
-Template: openflow-switch/fetch-switch-cert-failed
-Type: error
-_Description: Signed switch certificate could not be retrieved.
- The signed switch certificate could not be retrieved from the switch
- CA: retrieval of ${url} failed, with the following status: "${error}".
- .
- This probably indicates that the switch's certificate request has not
- yet been signed. If this is the problem, it may be fixed by signing
- the certificate request at ${pki-uri}, then trying to fetch the
- signed switch certificate again.
-
-Template: openflow-switch/complete
-Type: note
-_Description: OpenFlow Switch Setup Finished
- Setup of this OpenFlow switch is finished. Complete the setup procedure
- to enable the switch.
-[type: gettext/rfc822deb] openflow-switch.templates
+[type: gettext/rfc822deb] openflow-switch-config.templates
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: openflow-dev@lists.stanford.edu\n"
-"POT-Creation-Date: 2008-07-23 14:55-0700\n"
+"POT-Creation-Date: 2008-10-31 10:13-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
#. Type: multiselect
#. Choices
-#: ../openflow-switch.templates:1001
+#: ../openflow-switch-config.templates:1001
msgid "${choices}"
msgstr ""
#. Type: multiselect
#. Description
-#: ../openflow-switch.templates:1002
+#: ../openflow-switch-config.templates:1002
msgid "OpenFlow switch network devices:"
msgstr ""
#. Type: multiselect
#. Description
-#: ../openflow-switch.templates:1002
+#: ../openflow-switch-config.templates:1002
msgid ""
"Choose the network devices that should become part of the OpenFlow switch. "
"At least two devices must be selected for this machine to be a useful "
#. Type: multiselect
#. Description
-#: ../openflow-switch.templates:1002
+#: ../openflow-switch-config.templates:1002
msgid ""
"The network devices that you select should not be configured with IP or IPv6 "
"addresses, even if the switch contacts the controller over one of the "
#. Type: error
#. Description
-#: ../openflow-switch.templates:2001
+#: ../openflow-switch-config.templates:2001
msgid "No network devices were selected."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:2001
+#: ../openflow-switch-config.templates:2001
msgid ""
"No network devices were selected for inclusion in the OpenFlow switch. The "
"switch will be disabled."
#. Type: note
#. Description
-#: ../openflow-switch.templates:3001
+#: ../openflow-switch-config.templates:3001
msgid "Some Network Devices Have IP or IPv6 Addresses"
msgstr ""
#. Type: note
#. Description
-#: ../openflow-switch.templates:3001
+#: ../openflow-switch-config.templates:3001
msgid ""
"The following network devices selected to be part of the OpenFlow switch "
"have IP or IPv6 addresses configured:"
#. Type: note
#. Description
-#: ../openflow-switch.templates:3001
+#: ../openflow-switch-config.templates:3001
msgid "${configured-netdevs}"
msgstr ""
#. Type: note
#. Description
-#: ../openflow-switch.templates:3001
+#: ../openflow-switch-config.templates:3001
msgid ""
"This is usually a mistake, even if the switch contacts the controller over "
"one of the selected network devices. This is because a running OpenFlow "
#. Type: note
#. Description
-#: ../openflow-switch.templates:3001
+#: ../openflow-switch-config.templates:3001
msgid ""
"If this is an unintentional mistake, move back and fix the selection, or de-"
"configure the IP or IPv6 from these network devices."
#. Type: select
#. Choices
-#: ../openflow-switch.templates:4001
+#: ../openflow-switch-config.templates:4001
msgid "discovery, in-band, out-of-band"
msgstr ""
#. Type: select
#. Description
-#: ../openflow-switch.templates:4002
+#: ../openflow-switch-config.templates:4002
msgid "Switch-to-controller access method:"
msgstr ""
#. Type: select
#. Description
-#: ../openflow-switch.templates:4002
+#: ../openflow-switch-config.templates:4002
msgid ""
"The OpenFlow switch must be able to contact the OpenFlow controller over the "
"network. It can do so in one of three ways:"
#. Type: select
#. Description
-#: ../openflow-switch.templates:4002
+#: ../openflow-switch-config.templates:4002
msgid ""
"discovery: A single network is used for OpenFlow traffic and other data "
"traffic; that is, the switch contacts the controller over one of the network "
#. Type: select
#. Description
-#: ../openflow-switch.templates:4002
+#: ../openflow-switch-config.templates:4002
msgid ""
"in-band: As above, but the location of the controller is manually configured."
msgstr ""
#. Type: select
#. Description
-#: ../openflow-switch.templates:4002
+#: ../openflow-switch-config.templates:4002
msgid ""
"out-of-band: OpenFlow traffic uses a network separate from the data traffic "
"that it controls. If this is the case, the control network must already be "
#. Type: note
#. Description
-#: ../openflow-switch.templates:5001
+#: ../openflow-switch-config.templates:5001
msgid "Preparing to discover controller."
msgstr ""
#. Type: note
#. Description
-#: ../openflow-switch.templates:5001
+#: ../openflow-switch-config.templates:5001
msgid ""
"The setup program will now attempt to discover the OpenFlow controller. "
"Controller discovery may take up to 30 seconds. Please be patient."
#. Type: note
#. Description
-#: ../openflow-switch.templates:5001
+#: ../openflow-switch-config.templates:5001
msgid ""
"See secchan(8) for instructions on how to configure a DHCP server for "
"controller discovery."
#. Type: error
#. Description
-#: ../openflow-switch.templates:6001
+#: ../openflow-switch-config.templates:6001
msgid "Controller discovery failed."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:6001
+#: ../openflow-switch-config.templates:6001
msgid "The controller's location could not be determined automatically."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:6001
+#: ../openflow-switch-config.templates:6001
msgid ""
"Ensure that the OpenFlow DHCP server is properly configured. See secchan(8) "
"for instructions on how to configure a DHCP server for controller discovery."
#. Type: boolean
#. Description
-#: ../openflow-switch.templates:7001
+#: ../openflow-switch-config.templates:7001
msgid "Use discovered settings?"
msgstr ""
#. Type: boolean
#. Description
-#: ../openflow-switch.templates:7001
+#: ../openflow-switch-config.templates:7001
msgid "Controller discovery obtained the following settings:"
msgstr ""
#. Type: boolean
#. Description
-#: ../openflow-switch.templates:7001
+#: ../openflow-switch-config.templates:7001
msgid "Controller location: ${controller-vconn}"
msgstr ""
#. Type: boolean
#. Description
-#: ../openflow-switch.templates:7001
+#: ../openflow-switch-config.templates:7001
msgid "PKI URL: ${pki-uri}"
msgstr ""
#. Type: boolean
#. Description
-#: ../openflow-switch.templates:7001
+#: ../openflow-switch-config.templates:7001
msgid "Please verify that these settings are correct."
msgstr ""
#. Type: string
#. Description
-#: ../openflow-switch.templates:8001
+#: ../openflow-switch-config.templates:8001
msgid "Switch IP address:"
msgstr ""
#. Type: string
#. Description
-#: ../openflow-switch.templates:8001
+#: ../openflow-switch-config.templates:8001
msgid ""
"For in-band communication with the controller, the OpenFlow switch must be "
"able to determine its own IP address. Its IP address may be configured "
#. Type: string
#. Description
-#: ../openflow-switch.templates:8001
+#: ../openflow-switch-config.templates:8001
msgid "For static configuration, specify the switch's IP address as a string."
msgstr ""
#. Type: string
#. Description
-#: ../openflow-switch.templates:8001
+#: ../openflow-switch-config.templates:8001
msgid ""
"For dynamic configuration with DHCP (the most common case), specify \"dhcp"
"\". Configuration with DHCP will only work reliably if the network topology "
#. Type: error
#. Description
-#: ../openflow-switch.templates:9001
+#: ../openflow-switch-config.templates:9001
msgid "The switch IP address is invalid."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:9001
+#: ../openflow-switch-config.templates:9001
msgid ""
"The switch IP address must specified as \"dhcp\" or a valid IP address in "
"dotted-octet form (e.g. \"1.2.3.4\")."
#. Type: string
#. Description
-#: ../openflow-switch.templates:10001
+#: ../openflow-switch-config.templates:10001
msgid "Controller location:"
msgstr ""
#. Type: string
#. Description
-#: ../openflow-switch.templates:10001
+#: ../openflow-switch-config.templates:10001
msgid ""
"Specify how the OpenFlow switch should connect to the OpenFlow controller. "
"The value should be in form \"ssl:HOST[:PORT]\" to connect to the controller "
#. Type: error
#. Description
-#: ../openflow-switch.templates:11001
+#: ../openflow-switch-config.templates:11001
msgid "The controller location is invalid."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:11001
+#: ../openflow-switch-config.templates:11001
msgid ""
"The controller location must be specifed as \"ssl:HOST[:PORT]\" to connect "
"to the controller over SSL (recommended for security) or \"tcp:HOST[:PORT]\" "
#. Type: string
#. Description
-#: ../openflow-switch.templates:12001
+#: ../openflow-switch-config.templates:12001
msgid "OpenFlow PKI server host name or URL:"
msgstr ""
#. Type: string
#. Description
-#: ../openflow-switch.templates:12001
+#: ../openflow-switch-config.templates:12001
msgid ""
"Specify a URL to the OpenFlow public key infrastructure (PKI). If a host "
"name or IP address is specified in place of a URL, then http://<host>/"
#. Type: string
#. Description
-#: ../openflow-switch.templates:12001
+#: ../openflow-switch-config.templates:12001
msgid ""
"The OpenFlow PKI is usually on the same machine as the OpenFlow controller."
msgstr ""
#. Type: string
#. Description
-#: ../openflow-switch.templates:12001
+#: ../openflow-switch-config.templates:12001
msgid ""
"The setup process will connect to the OpenFlow PKI server over HTTP, using "
"the system's configured default HTTP proxy (if any)."
#. Type: error
#. Description
-#: ../openflow-switch.templates:13001
+#: ../openflow-switch-config.templates:13001
msgid "The switch CA certificate could not be retrieved."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:13001
+#: ../openflow-switch-config.templates:13001
msgid "Retrieval of ${url} failed, with the following status: \"${error}\"."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:13001
+#: ../openflow-switch-config.templates:13001
msgid ""
"Ensure that the OpenFlow PKI server is correctly configured and available at "
"${pki-uri}. If the system is configured to use an HTTP proxy, also make "
#. Choices
#. Type: select
#. Choices
-#: ../openflow-switch.templates:14001 ../openflow-switch.templates:15001
-#: ../openflow-switch.templates:17001
+#: ../openflow-switch-config.templates:14001
+#: ../openflow-switch-config.templates:15001
+#: ../openflow-switch-config.templates:17001
msgid "yes, no"
msgstr ""
#. Type: select
#. Description
-#: ../openflow-switch.templates:14002
+#: ../openflow-switch-config.templates:14002
msgid "Is ${fingerprint} the controller CA's fingerprint?"
msgstr ""
#. Type: select
#. Description
-#: ../openflow-switch.templates:14002
+#: ../openflow-switch-config.templates:14002
msgid ""
"If a man-in-the-middle attack is possible in your network environment, check "
"that the controller CA's fingerprint is really ${fingerprint}. Answer \"yes"
#. Type: select
#. Description
-#: ../openflow-switch.templates:14002
+#: ../openflow-switch-config.templates:14002
msgid ""
"If a man-in-the-middle attack is not a concern, there is no need to verify "
"the fingerprint. Simply answer \"yes\"."
#. Type: select
#. Description
-#: ../openflow-switch.templates:15002
+#: ../openflow-switch-config.templates:15002
msgid "Send certificate request to switch CA?"
msgstr ""
#. Type: select
#. Description
-#: ../openflow-switch.templates:15002
+#: ../openflow-switch-config.templates:15002
msgid ""
"Before it can connect to the controller over SSL, the OpenFlow switch's key "
"must be signed by the switch certificate authority (CA) located on the "
#. Type: select
#. Description
-#: ../openflow-switch.templates:15002
+#: ../openflow-switch-config.templates:15002
msgid ""
"Answer \"yes\" to send a signing request to the switch CA now. This is "
"ordinarily the correct choice. There is no harm in sending a given signing "
#. Type: select
#. Description
-#: ../openflow-switch.templates:15002
+#: ../openflow-switch-config.templates:15002
msgid ""
"Answer \"no\" to skip sending a signing request to the switch CA. Unless the "
"request has already been sent to the switch CA, manual sending of the "
#. Type: error
#. Description
-#: ../openflow-switch.templates:16001
+#: ../openflow-switch-config.templates:16001
msgid "The certificate request could not be sent."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:16001
+#: ../openflow-switch-config.templates:16001
msgid "Posting to ${url} failed, with the following status: \"${error}\"."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:16001
+#: ../openflow-switch-config.templates:16001
msgid ""
"Ensure that the OpenFlow PKI server is correctly configured and available at "
"${pki-uri}."
#. Type: select
#. Description
-#: ../openflow-switch.templates:17002
+#: ../openflow-switch-config.templates:17002
msgid "Fetch signed switch certificate from PKI server?"
msgstr ""
#. Type: select
#. Description
-#: ../openflow-switch.templates:17002
+#: ../openflow-switch-config.templates:17002
msgid ""
"Before it can connect to the controller over SSL, the OpenFlow switch's key "
"must be signed by the switch certificate authority (CA) located on the "
#. Type: select
#. Description
-#: ../openflow-switch.templates:17002
+#: ../openflow-switch-config.templates:17002
msgid ""
"At this point, a signing request has been sent to the switch CA (or sending "
"a request has been manually skipped), but the signed certificate has not yet "
#. Type: select
#. Description
-#: ../openflow-switch.templates:17002
+#: ../openflow-switch-config.templates:17002
msgid ""
"Answer \"yes\" to attempt to retrieve the signed switch certificate from the "
"switch CA. If the switch certificate request has been signed at the PKI "
#. Type: select
#. Description
-#: ../openflow-switch.templates:17002
+#: ../openflow-switch-config.templates:17002
msgid ""
"Answer \"no\" to postpone switch configuration. The configuration process "
"must be restarted later, when the switch certificate request has been signed."
#. Type: error
#. Description
-#: ../openflow-switch.templates:18001
+#: ../openflow-switch-config.templates:18001
msgid "Signed switch certificate could not be retrieved."
msgstr ""
#. Type: error
#. Description
-#: ../openflow-switch.templates:18001
+#: ../openflow-switch-config.templates:18001
msgid ""
"The signed switch certificate could not be retrieved from the switch CA: "
"retrieval of ${url} failed, with the following status: \"${error}\"."
#. Type: error
#. Description
-#: ../openflow-switch.templates:18001
+#: ../openflow-switch-config.templates:18001
msgid ""
"This probably indicates that the switch's certificate request has not yet "
"been signed. If this is the problem, it may be fixed by signing the "
#. Type: note
#. Description
-#: ../openflow-switch.templates:19001
+#: ../openflow-switch-config.templates:19001
msgid "OpenFlow Switch Setup Finished"
msgstr ""
#. Type: note
#. Description
-#: ../openflow-switch.templates:19001
+#: ../openflow-switch-config.templates:19001
msgid ""
"Setup of this OpenFlow switch is finished. Complete the setup procedure to "
"enable the switch."
dh_clean -k -s
dh_installdirs -s
$(MAKE) -C _debian DESTDIR=$(CURDIR)/debian/openflow install
- cp debian/openflow-switch.overrides debian/openflow-switch/usr/share/lintian/overrides/openflow-switch
+ cp debian/openflow-switch-config.overrides debian/openflow-switch-config/usr/share/lintian/overrides/openflow-switch-config
dh_install -s
# Must not depend on anything. This is to be called by
projects / openvswitch / commitdiff