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.

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

Client warning 'No valid topology' #343

Closed
sgeisler opened this issue Sep 18, 2020 · 0 comments · Fixed by #505
Closed

Client warning 'No valid topology' #343

sgeisler opened this issue Sep 18, 2020 · 0 comments · Fixed by #505

Comments

@sgeisler
Copy link

When running the native client with the socks service provider I'm getting a lot of these warnings sometimes (not always, but many when it happens):

2020-09-18T13:37:58.748 WARN  client_core::client::real_messages_control::real_traffic_stream > No valid topology detected - won't send any loop cover message this time                                                                                    

and a few of these in between:

2020-09-18T13:37:58.595 WARN  client_core::client::cover_traffic_stream                       > No valid topology detected - won't send any loop cover message this time                                                                                    

Idk what triggers it, is this normal/ok? What's the cause?

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

Successfully merging a pull request may close this issue.

1 participant