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.

Sign up for GitHub

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

Jump to bottom

Socks5_Client crashes at 'failed to extract peer address' #470

Closed
rachyandco opened this issue Nov 25, 2020 · 3 comments
Closed

Socks5_Client crashes at 'failed to extract peer address' #470

rachyandco opened this issue Nov 25, 2020 · 3 comments

Comments

@rachyandco
Copy link
Contributor

The following set up is to be considered:

on server: Nym-client and nym-network-requestor with flag -o are running.
on laptop: nym-socks5-client is running
All are version 0.9.1

Firefox on the laptop is configured to connect to the local proxy.

the nym-socks5-client crashes

See the following output:

Laptop:

$ ./nym-socks5-client run --id nym


      _ __  _   _ _ __ ___
     | '_ \| | | | '_ \ _ \
     | | | | |_| | | | | | |
     |_| |_|\__, |_| |_| |_|
            |___/

             (socks5 proxy - version 0.9.1)

    
 2020-11-25T13:55:25.266 INFO  nym_socks5_client::client > Starting nym client
 2020-11-25T13:55:25.308 INFO  nym_socks5_client::client > Obtaining initial network topology from http://testnet-validator1.nymtech.net:8081
 2020-11-25T13:55:28.558 INFO  nym_socks5_client::client > Starting topology refresher...
 2020-11-25T13:55:28.558 INFO  nym_socks5_client::client > Starting received messages buffer controller...
 2020-11-25T13:55:28.667 INFO  nym_socks5_client::client > Starting mix traffic controller...
 2020-11-25T13:55:28.667 INFO  nym_socks5_client::client > Starting real traffic stream...
 2020-11-25T13:55:28.667 INFO  nym_socks5_client::client > Starting loop cover traffic stream...
 2020-11-25T13:55:28.667 INFO  nym_socks5_client::client > Starting socks5 listener...
 2020-11-25T13:55:28.668 INFO  nym_socks5_client::socks::server > Listening on 127.0.0.1:1080
 2020-11-25T13:55:28.668 INFO  nym_socks5_client::client        > Client startup finished!
 2020-11-25T13:55:28.668 INFO  nym_socks5_client::client        > The address of this client is: 9S3S8ZTHcArjWGdxKVkDdhQkRagR1QeTCShWcPmEjfJS.GjZtrinwmYnrX6UaxL1mXUNgioejQJiFrpiZK62VXgwY@5nrYxPR8gt2Gzo2BbHtsGf66KAEQY91WmM1eW78EphNy
 2020-11-25T13:55:28.668 INFO  nym_socks5_client::socks::server > Serving Connections...
 2020-11-25T13:57:05.353 INFO  nym_socks5_client::socks::client > Starting proxy for 185.19.29.19:443 (id: 4857928407678432070)
 2020-11-25T13:57:05.570 INFO  nym_socks5_client::socks::client > Starting proxy for 172.217.168.46:443 (id: 7956951777250370748)
 2020-11-25T13:57:09.345 INFO  nym_socks5_client::socks::client > Starting proxy for 104.20.20.236:443 (id: 5318083858678748683)
 2020-11-25T13:57:12.876 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 3 (set id: 1610880839)
 2020-11-25T13:57:18.410 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 12 (set id: 303380592)
 2020-11-25T13:57:18.417 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 7 (set id: 303380592)
 2020-11-25T13:57:19.351 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 13 (set id: 303380592)
 2020-11-25T13:57:19.377 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 9 (set id: 1905980343)
 2020-11-25T13:57:19.432 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 5 (set id: 1905980343)
 2020-11-25T13:57:19.514 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 9 (set id: 303380592)
 2020-11-25T13:57:19.914 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 13 (set id: 1905980343)
 2020-11-25T13:57:20.667 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 6 (set id: 303380592)
 2020-11-25T13:57:20.772 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 3 (set id: 303380592)
 2020-11-25T13:57:21.193 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 11 (set id: 1905980343)
 2020-11-25T13:57:21.312 INFO  nym_socks5_client::socks::client   > Proxy for 185.19.29.19:443 is finished (id: 4857928407678432070)
 2020-11-25T13:57:21.383 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 2 (set id: 1905980343)
 2020-11-25T13:57:21.483 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 16 (set id: 1905980343)
 2020-11-25T13:57:21.509 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 16 (set id: 1905980343)
 2020-11-25T13:57:21.819 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 13 (set id: 1905980343)
 2020-11-25T13:57:21.840 INFO  nym_socks5_client::socks::client   > Starting proxy for 40.115.22.134:443 (id: 11607561059318248824)
 2020-11-25T13:57:21.975 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 18 (set id: 1905980343)
 2020-11-25T13:57:22.230 WARN  nymsphinx_chunking::reconstruction > duplicate fragment received! - frag - 14 (set id: 1905980343)
 2020-11-25T13:57:22.260 INFO  nym_socks5_client::socks::client   > Starting proxy for 13.224.93.116:443 (id: 4629107109442226166)
 2020-11-25T13:57:22.846 INFO  nym_socks5_client::socks::client   > Starting proxy for 216.58.215.227:443 (id: 1495064729541379594)
 2020-11-25T13:57:24.268 INFO  nym_socks5_client::socks::client   > Starting proxy for 216.58.215.227:443 (id: 5863211421181878158)
thread 'tokio-runtime-worker' panicked at 'failed to extract peer address: Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" }', clients/socks5/src/socks/client.rs:241:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted (core dumped)

On the server:

Nov 25 12:50:42 nym systemd[1]: Started NYM client service.
Nov 25 12:50:42 nym nym-client[21601]:       _ __  _   _ _ __ ___
Nov 25 12:50:42 nym nym-client[21601]:      | '_ \| | | | '_ \ _ \
Nov 25 12:50:42 nym nym-client[21601]:      | | | | |_| | | | | | |
Nov 25 12:50:42 nym nym-client[21601]:      |_| |_|\__, |_| |_| |_|
Nov 25 12:50:42 nym nym-client[21601]:             |___/
Nov 25 12:50:42 nym nym-client[21601]:              (client - version 0.9.1)
Nov 25 12:50:42 nym nym-client[21601]:     
Nov 25 12:50:42 nym nym-client[21601]:  2020-11-25T12:50:42.250 INFO  nym_client::client > Starting nym client
Nov 25 12:50:42 nym nym-client[21601]:  2020-11-25T12:50:42.286 INFO  nym_client::client > Obtaining initial network topology from http://testnet-validator1.nymtech.net:8081
Nov 25 12:50:45 nym nym-client[21601]:  2020-11-25T12:50:45.475 INFO  nym_client::client > Starting topology refresher...
Nov 25 12:50:45 nym nym-client[21601]:  2020-11-25T12:50:45.475 INFO  nym_client::client > Starting received messages buffer controller...
Nov 25 12:50:45 nym nym-client[21601]:  2020-11-25T12:50:45.531 INFO  nym_client::client > Starting mix traffic controller...
Nov 25 12:50:45 nym nym-client[21601]:  2020-11-25T12:50:45.531 INFO  nym_client::client > Starting real traffic stream...
Nov 25 12:50:45 nym nym-client[21601]:  2020-11-25T12:50:45.532 INFO  nym_client::client > Starting loop cover traffic stream...
Nov 25 12:50:45 nym nym-client[21601]:  2020-11-25T12:50:45.532 INFO  nym_client::client > Starting websocket listener...
Nov 25 12:50:45 nym nym-client[21601]:  2020-11-25T12:50:45.532 INFO  nym_client::websocket::listener > Running websocket on "127.0.0.1:1977"
Nov 25 12:50:45 nym nym-client[21601]:  2020-11-25T12:50:45.532 INFO  nym_client::client              > Client startup finished!
Nov 25 12:50:45 nym nym-client[21601]:  2020-11-25T12:50:45.532 INFO  nym_client::client              > The address of this client is: 9MJ3dEepmjKznuJScrWBQSWUfLwr4i8vuvsaeLFvCieR.HK9eZx1Nc2zKVJqoGvVLi5PwZEsG4xawGNSf9mVYoNSJ@DiYR9o8KgeQ81woKPYVAu4LNaAEg8SWkiufDCahNnPov
Nov 25 12:54:45 nym nym-client[21601]:  2020-11-25T12:54:45.922 WARN  nym_client::websocket::handler  > failed to obtain message from websocket stream! stopping connection handler: WebSocket protocol error: Connection reset without closing handshake
Nov 25 12:55:01 nym systemd[1]: Started NYM network requester service.
Nov 25 12:55:01 nym nym-network-requester[21673]: YOU HAVE STARTED IN 'OPEN PROXY' MODE. ANYONE WITH YOUR CLIENT ADDRESS CAN MAKE REQUESTS FROM YOUR MACHINE. PLEASE QUIT IF YOU DON'T UNDERSTAND WHAT YOU'RE DOING.
Nov 25 12:55:01 nym nym-network-requester[21673]: Starting socks5 service provider:
Nov 25 12:55:01 nym nym-network-requester[21673]:  2020-11-25T12:55:01.562 INFO  nym_network_requester::core > * connected to local websocket server at ws://localhost:1977
Nov 25 12:55:01 nym nym-network-requester[21673]: All systems go. Press CTRL-C to stop the server.
Nov 25 12:57:05 nym nym-network-requester[21673]:  2020-11-25T12:57:05.807 INFO  nym_network_requester::core > Starting proxy for 185.19.29.19:443 (currently there are 1 proxies being handled)
Nov 25 12:57:08 nym nym-network-requester[21673]:  2020-11-25T12:57:08.164 INFO  nym_network_requester::core > Starting proxy for 172.217.168.46:443 (currently there are 2 proxies being handled)
Nov 25 12:57:09 nym nym-network-requester[21673]:  2020-11-25T12:57:09.957 INFO  nym_network_requester::core > Starting proxy for 104.20.20.236:443 (currently there are 3 proxies being handled)
Nov 25 12:57:19 nym nym-network-requester[21673]:  2020-11-25T12:57:19.249 INFO  nym_network_requester::core > Proxy for 185.19.29.19:443 is finished  (currently there are 2 proxies being handled)
Nov 25 12:57:22 nym nym-network-requester[21673]:  2020-11-25T12:57:22.942 WARN  proxy_helpers::connection_controller > Received a 'Send' before 'Connect' - going to buffer the data
Nov 25 12:57:23 nym nym-network-requester[21673]:  2020-11-25T12:57:23.615 WARN  proxy_helpers::connection_controller > Received a 'Send' before 'Connect' - going to buffer the data
Nov 25 12:57:24 nym nym-network-requester[21673]:  2020-11-25T12:57:24.510 INFO  nym_network_requester::core          > Starting proxy for 216.58.215.227:443 (currently there are 3 proxies being handled)
Nov 25 12:57:34 nym nym-network-requester[21673]:  2020-11-25T12:57:34.518 INFO  nym_network_requester::core          > Proxy for 216.58.215.227:443 is finished  (currently there are 2 proxies being handled)
@jstuczyn
Copy link
Contributor

Is this issue persistent through multiple launches or did it only happen once? Also, if you don't mind, what website did you happen to visit when this occured?

@rachyandco
Copy link
Contributor Author

it happend once. I could not say if a specific website was used then.

@tommyv1987
Copy link
Contributor

I'm going to close this ticket as it's become stale and now we have mainnet binaries. Lot's of releases have happened since, so we expect these issues above to have been addressed.

@2g4y1 2g4y1 mentioned this issue Dec 19, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rachyandco @jstuczyn @tommyv1987