Skip to content
This repository has been archived by the owner on Sep 29, 2024. It is now read-only.

On TCP, no PUSH_REPLY unless PUSH_REQUEST is sent repeatedly #73

Closed
keeshux opened this issue Mar 22, 2019 · 2 comments
Closed

On TCP, no PUSH_REPLY unless PUSH_REQUEST is sent repeatedly #73

keeshux opened this issue Mar 22, 2019 · 2 comments
Assignees
@keeshux
Labels
bug Something isn't working
Milestone
1.6.2

Comments

@keeshux
Copy link
Member

keeshux commented Mar 22, 2019

Even if it's supposed to be a reliable link. Gotta understand better what OpenVPN expects under the hood.
@keeshux keeshux added the bug Something isn't working label Mar 22, 2019
@keeshux keeshux self-assigned this Mar 22, 2019
@keeshux keeshux added this to the 1.5.2 milestone Mar 22, 2019
@keeshux
Copy link
Member Author

keeshux commented Mar 22, 2019

Not 100% sure but it might be the culprit behind #67 and #71.

@keeshux keeshux removed this from the 1.5.2 milestone Apr 1, 2019
@keeshux
Copy link
Member Author

keeshux commented Apr 15, 2019

#67 proved to be unrelated.

@keeshux keeshux added this to the 1.6.2 milestone Apr 16, 2019
keeshux added a commit that referenced this issue Apr 16, 2019
@keeshux
Loop pulling plain text from TLS
6fd6d22 
There might be more data to read.

Fixes #71, #73
@keeshux keeshux closed this as completed Apr 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@keeshux keeshux

Labels
bug Something isn't working
Projects
None yet
Milestone
1.6.2
Development

No branches or pull requests
1 participant
@keeshux