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

Add detection of possible firewall issues #52

clemahieu opened this issue Feb 2, 2017 · 2 comments


3 participants
Copy link

commented Feb 2, 2017

If no TCP session has succeeded, there might be a client side block of outbound TCP.

@rkeene rkeene added this to the V18.0 milestone Aug 23, 2018

@rkeene rkeene added the question label Aug 23, 2018

@rkeene rkeene self-assigned this Aug 23, 2018


This comment has been minimized.

Copy link

commented Aug 23, 2018

I'm not sure we can do anything if there are firewall or network connectivity issues -- I'll try to discover what the plan was for this.

@zhyatt zhyatt added this to Unscheduled in V18 Dec 27, 2018

@rkeene rkeene moved this from Unscheduled to CP 0 in V18 Dec 31, 2018


This comment has been minimized.

Copy link

commented Jan 9, 2019

Team determined this wasn't worth pursuing.

@zhyatt zhyatt closed this Jan 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.