-
Notifications
You must be signed in to change notification settings - Fork 5
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
Support system proxy #115
Comments
?? What do you mean by ICMP ping? I don't think melnode uses ICMP ping anywhere. The |
That's weird. If it's HTTP traffic, then proxychain4 should be able to do the proxy, but I failed when I tried. The log: [2023-03-07TXX:XX:XXZ WARN melnet2::swarm] [melnode] get more routes failed from 224.0.0.1:41814: ping failed
[2023-03-07TXX:XX:XXZ WARN melblkidx] indexing failed with error during network communication: transport-level error: connection closed before message completed, restarting The command: The proxychains4 configuration is correct and works well with other applications. That's why I thought "ping" was using the ICMP protocol. Well, since "ping" in melnet2 uses http, there may be some compatibility issues between proxychains4 and melnode. Anyway, I think it's good to have the parameter "whether to use the system proxy". Or specify the proxy directly in the parameter. |
Details
In some countries with network restrictions, it is not possible to send ICMP packets to some machines via ping. But melnode only supports ICMP ping, and normal proxies do not support network layer protocols.
If melnode can support TCPing and inherit the system proxy (or proxy parameters), then it is possible to bypass these network restrictions.
The text was updated successfully, but these errors were encountered: