Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-1332

Support binding on separate NICs for Client-to-Node and Node-to-Node communication

    XMLWordPrintable

Details

    • Task
    • Status: Complete
    • High
    • Resolution: Done
    • None
    • 1.4
    • None
    • None

    Description

      Now indy-plenum's and indy-node's listener sockets are always bound on 0.0.0.0, it is hard-coded, so that we listen all interfaces. We need to bind listener sockets on addresses specified for node stack and client stack for complete support of separate NICs.
      Also we need to be able to set different max queue sizes for node-to-node and client-to-node communications.

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. INDY-1249 Separate NICs must be used for Client-to-Node and Node-to-Node communication

          • Medium - Has the potential to affect progress.
          • Complete
          relates to

          Bug - A problem which impairs or prevents the functions of the product. INDY-1379 Migration fails in case of upgrade to version with new transactions format

          • Highest - This problem will block progress.
          • Complete

          Activity

            People

              VladimirWork Vladimir Shishkin
              sergey-shilov Sergey Shilov
              Axel Nennker, Sergey Shilov, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: