Skip to content
This repository has been archived by the owner on Dec 20, 2022. It is now read-only.

Question about reachable node status #13

Open
porcupinenick opened this issue Dec 25, 2019 · 4 comments
Open

Question about reachable node status #13

porcupinenick opened this issue Dec 25, 2019 · 4 comments

Comments

@porcupinenick
Copy link

I have an active channel to this node:

PubKey: 03aaa4b0410d6b7ca72f71fc3b9334e7389778a7b98a7e52600979f249c2d387f6
Alias: AnriBTC

However, the reachable status icon is red. I'm not sure why the visualizer is stating that this node is not reachable/not active.

@bmancini55
Copy link
Member

This tool only checks IPv4 based addresses to determine if a node is reachable. TOR and IPv6 addresses are not currently supported.

@porcupinenick
Copy link
Author

Could I possibly work on supporting TOR and IPv6?

@bmancini55
Copy link
Member

Sure thing!

I mispoke on IPv6. I just took a look at the code to refresh my memory. It looks like the peer-service.js uses Node.js socket client in the net package. So this should support both IPv4 and IPv6 lookups out of the box.

TOR is still unsupported however. I think a package like socks5-http-client (https://www.npmjs.com/package/socks5-http-client) would be use useful for that.

@porcupinenick
Copy link
Author

Ok, I'll look into it. Thanks Brian!

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

No branches or pull requests

2 participants