Hi @ibauersachs,

I have a first working solution. master...tw-datascientist:dnsjava:master

Yes, I plan to refactor the changes into the IoClients. Handling UDP is tricky. I have to strip the SOCKS UDP header from the UDP reply. And the TCP connection to setup the UDP associate have to stay open till the UDP transmission has finished. Otherwise I get java.net.PortUnreachableException.

Oct  2 14:46:43 (1727880403.768883) sockd[33]: info: pass(1): tcp/accept [: 172.30.0.2.49904 172.30.0.3.1080
Oct  2 14:46:43 (1727880403.769914) sockd[16]: info: pass(1): udp/udpassociate [: 0.0.0.0.0 172.30.0.3.10000
Oct  2 14:46:43 (1727880403.774654) sockd[37]: info: pass(1): udp/udpassociate -: 172.30.0.2.60384 172.30.0.3.10000 -> 172.30.0.3.60384 1.1.1.1.53 (39)
Oct  2 14:46:43 (1727880403.785650) sockd[37]: info: pass(2): udp/udpreply -: 1.1.1.1.53 172.30.0.3.60384 -> 172.30.0.3.10000 172.30.0.2.60384 (55)
Oct  2 14:46:43 (1727880403.786366) sockd[37]: info: pass(1): udp/udpassociate ]: 65/1 -> 172.30.0.2.60384 172.30.0.3.10000 -> 49/1, 39/1 -> 172.30.0.3.60384 1.1.1.1.53 -> 55/1: local client closed.  Session duration: 0s
Oct  2 14:46:43 (1727880403.786378) sockd[37]: info: pass(1): tcp/accept ]: 65 -> 172.30.0.2.49904 172.30.0.3.1080 -> 39: local client closed.  Session duration: 0s

My guess is that the best approach is to move this logic into the processReadyKey method in NioUdpClient.java.

DNS over SOCKS #341

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions