Uploaded image for project: 'ONOS'
  1. ONOS
  2. ONOS-3511

ONOS if enableOFTLS, only can have single switch connection

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.4.0
    • Component/s: None
    • Labels:
    • Environment:

      commit b1f1625636836003562cdff55deb9328ca1176b0
      Author: Sho SHIMIZU <sshimizu@us.fujitsu.com>
      Date: Wed Nov 25 23:03:16 2015 -0800

    • Story Points:
      2
    • Epic Link:
    • Sprint:
      Emu Sprint 4 (11/23-12/18)

      Description

      when configure ovs to connect to ONOS via ssl, only the first br can connect. As soon as the second br is connected, ONOS closes all I/O workers connections:

          • HelloRequest (empty)
            New I/O worker #2, WRITE: TLSv1.2 Handshake, length = 40
            New I/O worker #2, READ: TLSv1 Handshake, length = 290
            New I/O worker #2, fatal error: 40: ciphertext sanity check failed
            javax.crypto.BadPaddingException: ciphertext sanity check failed
            %% Invalidated: [Session-1, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA]
            New I/O worker #2, SEND TLSv1.2 ALERT: fatal, description = handshake_failure
            New I/O worker #2, WRITE: TLSv1.2 Alert, length = 32
            New I/O worker #2, fatal: engine already closed. Rethrowing javax.net.ssl.SSLHandshakeException: ciphertext sanity check failed
            New I/O worker #2, called closeOutbound()
            New I/O worker #2, closeOutboundInternal()
            New I/O worker #2, called closeInbound()
            New I/O worker #2, fatal: engine already closed. Rethrowing javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
            New I/O worker #2, called closeOutbound()
            New I/O worker #2, closeOutboundInternal()
            New I/O worker #3, called closeOutbound()
            New I/O worker #3, closeOutboundInternal()
            New I/O worker #4, called closeOutbound()
            New I/O worker #4, closeOutboundInternal()
            New I/O worker #1, called closeOutbound()
            New I/O worker #1, closeOutboundInternal()
            New I/O worker #1, called closeInbound()
            New I/O worker #1, closeInboundInternal()
            New I/O worker #5, called closeOutbound()
            New I/O worker #5, closeOutboundInternal()
            New I/O worker #6, called closeOutbound()
            New I/O worker #6, closeOutboundInternal()
            New I/O worker #7, called closeOutbound()
            New I/O worker #7, closeOutboundInternal()
            New I/O worker #8, called closeOutbound()
            New I/O worker #8, closeOutboundInternal()
            New I/O worker #9, called closeOutbound()
            New I/O worker #9, closeOutboundInternal()
            New I/O worker #10, called closeOutbound()
            New I/O worker #10, closeOutboundInternal()
            New I/O worker #11, called closeOutbound()
            New I/O worker #11, closeOutboundInternal()

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              ash ash
              Reporter:
              suibin suibin
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: