Skip to content
This repository has been archived by the owner on Oct 28, 2021. It is now read-only.

aleth / aleth-bootnode log wrong IP address port #5415

Closed
halfalicious opened this issue Jan 4, 2019 · 0 comments · Fixed by #5609
Closed

aleth / aleth-bootnode log wrong IP address port #5415

halfalicious opened this issue Jan 4, 2019 · 0 comments · Fixed by #5609

Comments

@halfalicious
Copy link
Contributor

halfalicious commented Jan 4, 2019

Both aleth and aleth-bootnode log their IP address (as a part of the enode URL) after the network has been started successfully. For example:

C:\Users\nilse\Documents\Code\aleth\build\aleth-bootnode\Debug>aleth-bootnode.exe -v4
aleth-bootnode, a C++ Ethereum bootnode implementation
INFO  01-03 20:43:10 main net    Id: ##90c2a961…
INFO  01-03 20:43:10 p2p  info   UPnP device not found.
TRACE 01-03 20:43:10 p2p  net    Listening on local port 30303 (public: 0.0.0.0:0)
DEBUG 01-03 20:43:10 p2p  net    p2p.started id: ##90c2a961…
Node ID: enode://90c2a9617bd4de4bebf571dae43c8f1f00e8d56c44239e1bd0ed86a6020ac239a39d546c70862e59d810a561b33909b60f5a787bcf2039b1d20f99c5542d4762@0.0.0.0:0

However, the port information included in the enode URL is incorrect - it should be 30303 rather than 0

@halfalicious halfalicious changed the title aleth / aleth-bootnode log wrong IP address aleth / aleth-bootnode log wrong IP address port Jan 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant