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

Two node can using the same P2P port for start and even sync data. #2380

Closed
superboyiii opened this issue Mar 8, 2021 · 3 comments · Fixed by neo-project/neo-node#758
Closed
Assignees

Comments

@superboyiii
Copy link
Member

Describe the bug
I have two chain and two nodes for each. They're using the same Port and WsPort and within different magic. I can start nodeB after nodeA's running. And NodeB can also receive data although no connections showed on Console. There should be port conflict, right?

To Reproduce
Steps to reproduce the behavior:

  1. Run Node A for A chain.
  2. Make the same Port and WsPort for Node B.
  3. Run Node B for B chain.

Expected behavior
Node B can run and blocks can be received and increase but no connections and peers are showed on Console.

Screenshots
image

91a865e7eed5a40e45a282d2aa292f50.mp4

Platform:

  • OS: [e.g. Windows 10 x64]
  • Version [latest]
@shargon shargon self-assigned this Mar 8, 2021
@shargon
Copy link
Member

shargon commented Mar 8, 2021

I will take a look

@superboyiii
Copy link
Member Author

Set Console log to be true in config.json and see the error but doesn't interrupt block sync.
image

@shargon
Copy link
Member

shargon commented Mar 8, 2021

if the exception it's captured, it could be the expected behaviour 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants