Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: ip colocation is parameterizable. If set to 0, it is disabled #2323

Merged
merged 1 commit into from
Jan 2, 2024

Conversation

Ivansete-status
Copy link
Collaborator

Description

The "ip colocation" concept refers to the maximum allowed peers from the same IP address. We allow disable this limit when the node works behing a reverse proxy.

How to test

  1. Run one node with ip-colocation-limit set to 0.
  2. The node set in 1. can accept multiple connections from nodes run locally (127.0.0.1)

  1. Run one node with ip-colocation-limit set to 2.
  2. The node set in 1. only accepts two peers from 127.0.0.1.

ℹ️ in both cases remember to set rest-admin = true so that you can check the peers with curl -X GET 127.0.0.1:8645/admin/v1/peers.

Issue

closes #2306

The "ip colocation" concept refers to the maximum allowed peers
from the same IP address. We allow disable this limit when the
node works behing a reverse proxy.
Copy link

This PR may contain changes to configuration options of one of the apps.

If you are introducing a breaking change (i.e. the set of options in latest release would no longer be applicable) make sure the original option is preserved with a deprecation note for 2 following releases before it is actually removed.

Please also make sure the label release-notes is added to make sure any changes to the user interface are properly announced in changelog and release notes.

Copy link

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2323

Built from 8360201

@Ivansete-status Ivansete-status self-assigned this Dec 29, 2023
@Ivansete-status Ivansete-status marked this pull request as ready for review December 30, 2023 11:49
@gabrielmer gabrielmer added the release-notes Issue/PR needs to be evaluated for inclusion in release notes highlights or upgrade instructions label Jan 2, 2024
Copy link
Contributor

@gabrielmer gabrielmer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! Thanks so much!

Copy link
Contributor

@NagyZoltanPeter NagyZoltanPeter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Great, I hope it also helps Filter subscriptions flood, tested by @chaitanyaprem.
Due that scenario will not work out if PeerManager can be configured to limit peers per IP.

@Ivansete-status Ivansete-status merged commit ebad038 into master Jan 2, 2024
9 of 10 checks passed
@Ivansete-status Ivansete-status deleted the ip-colocation-configurable branch January 2, 2024 13:01
@SionoiS SionoiS added this to the Release 0.24.0 milestone Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes Issue/PR needs to be evaluated for inclusion in release notes highlights or upgrade instructions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

chore: make the ip colocation parameter configurable
4 participants