ConnectionManager::get_own_endpoints returns 0 as port #207

benjaminbollen · 2015-07-28T16:23:52Z

CRUSTv0.2.0

when populating the accepting_on endpoints in routing, I find that I get eg

local_endpoints: [Tcp(V4(127.0.0.1:0)), Tcp(V4(192.168.0.32:0)), Tcp(V4(172.17.42.1:0))]

so on the receiving end of the connect_request message, the connect_manager.connect() call is not effective, and routing can't establish a new connection between the two nodes.

fixes #207 get_own_endpoints returns correct port

Viv-Rajkumar added the bug label Jul 28, 2015

chandraprakash self-assigned this Jul 28, 2015

chandraprakash added the in progress label Jul 28, 2015

chandraprakash closed this as completed in d7ccb42 Jul 29, 2015

vinipsmaker added a commit that referenced this issue Jul 29, 2015

Merge pull request #210 from chandraprakash/bugfix_207

e98a51e

fixes #207 get_own_endpoints returns correct port

chandraprakash removed the in progress label Jul 29, 2015

S-Coyle unassigned chandraprakash Mar 18, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ConnectionManager::get_own_endpoints returns 0 as port #207

ConnectionManager::get_own_endpoints returns 0 as port #207

benjaminbollen commented Jul 28, 2015

ConnectionManager::get_own_endpoints returns 0 as port #207

ConnectionManager::get_own_endpoints returns 0 as port #207

Comments

benjaminbollen commented Jul 28, 2015