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

Consider using net.PacketConn instead of *net.UDPConn #16

Open
ainar-g opened this issue Jan 13, 2023 · 0 comments
Open

Consider using net.PacketConn instead of *net.UDPConn #16

ainar-g opened this issue Jan 13, 2023 · 0 comments

Comments

@ainar-g
Copy link
Contributor

ainar-g commented Jan 13, 2023

The current (v2) version of the module requires the packet connection to be a *net.UDPConn, while the TCP part is abstracted behind net.Listener. That is done so that dns.SessionUDP could be used, but it has a limited interface. An example of a thing that could be done with a custom net.PacketConn is getting the original destination address along with the source (remote) address, which is useful when listening on 0.0.0.0.

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

No branches or pull requests

1 participant