-
Notifications
You must be signed in to change notification settings - Fork 152
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
Raw packet relay feature (performance) #67
Comments
This was referenced Apr 22, 2014
I've begun working on this. |
Awesome. 👍 |
@SGrondin, please work off of the okTurtles forks, they have a lot of improvements (especially in native-dns-packet) @tjfontaine said he would review the PRs I sent him (but I'm guessing he just needs to find the time for it):
|
Noted, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are many ways to implement the following (and they should all be explored), but the main idea is that always having to parse and repack every packet creates a DNS library that unnecessarily slow when only a relay is desired.
The goal of this feature is to put as little latency on the receiving and sending of a DNS question/response when the goal is to simply act as a bridge/relay for another DNS server.
The text was updated successfully, but these errors were encountered: