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

Separate NICs must be used for Client-to-Node and Node-to-Node communication

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Complete
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.4
    • Component/s: None
    • Labels:

      Description

      We do have at least one requirement related to DDoS that we really need to address, which is that we need to be able to bind listeners in indy-node to a specific NIC. (I am told that, although we can declare in config that we’re binding to a specific NIC, logs reveal that we always bind to all NICs. This may be inaccurate, but if it is, we should teach people how to do it right, because apparently nobody is.) The reason I feel like this is urgent is that a major DDoS mitigation strategy for MGL was the requirement that all validators should have 2 NICs--one dedicated to consensus with other validators, and one dedicated to clients. If we have bad clients doing DDoS, but we have two NICs, then we shouldn’t be able to defeat consensus on the other NIC.

      We need to make sure that we support using two separate NICs and provide detailed instructions on how it can be achieved.

      We should explore working capacity of 2 NIC node configuration before we will configure persistent pool this way because now both node and client IPs bind to 0.0.0.0.

      • Will node work with 2 NIC and different IPs for node and client in pool ledger?
      • Will pool work with 1 / f+1 / n-f / n nodes configured this way?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              VladimirWork Vladimir Shishkin
              Reporter:
              ashcherbakov Alexander Shcherbakov
              Watchers:
              Alexander Shcherbakov, Axel Nennker, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: