Fix client hashing #11
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replies to messages from `192.168.0.2:1234` will be forwarded to a client on `192.168.0.21:234`. Similar with `1.1.1.12:1` and `1.1.11.2:1`
|
Looks good, thanks for the bugfix. I'll merge and deploy a new version at some point this week. |
icawebdesign
pushed a commit
to icawebdesign/node-udp-proxy
that referenced
this pull request
Aug 31, 2020
Fix client hashing as per PR: gildean#11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replies to messages from
192.168.0.2:1234will be forwarded to a client on192.168.0.21:234. Similar with1.1.1.12:1and1.1.11.2:1