![]() So you have to check the capabilities of your proxifier tool to see if it supports UDP or not. And there are other tunnel/proxy protocols as well, which may or may not have their on UDP capabilities. HTTP/FTP proxies do not support UDP at all (since HTTP/FTP are TCP-based protocols). That is a LOT more work for a UDP proxifier to do compared to TCP.Īnd that is just for SOCKS. Different proxy types can be mixed in the same chain. Proxifier alternative for linux using redsocks. Supports HTTP, SOCKS4 and SOCKS5 proxy servers. Allows TCP and DNS tunneling through proxies. And because UDP is connection-less, the proxifier would have to also implement a timeout mechanism on its SOCKS v5 TCP connection to the proxy so it can eventually be closed after a period of UDP traffic being idle. A software like Proxifier for linux linuxproxysocks-proxy 41,167 Yes you can use proxychain About proxychains tool: It's a proxifier. Every outbound UDP packet would have to be intercepted, then the proxifier would have to check if it already has its own SOCKS v5 TCP connection associated with the packet's local/remote tuple and if not then create a new one and send the necessary UDP forwarding handshake, then encapsulate every outbound UDP packet for that tuple and send it to the proxy's outbound IP/Port, and receive every matching inbound UDP packet for that tuple from the proxy so it can be de-encapsulated and forwarded to the app's local IP/Port that sent out the original outbound UDP packet. It would be much harder to implement, since there is no outgoing connection to redirect. Once the TCP connection has been established, the proxifier does not need to do anything more with the connection since the app is now talking directly to the proxy. Tools like CCProxy, Proxycap, Proxifier, etc work (for TCP, anyway) by intercepting outgoing TCP conections and redirecting them to the proxy server, transparently handling any proxy handshaking to set up forwarding, before then allowing any application data to flow through the TCP connection. However, it requires the requesting app to establish a TCP connection to the SOCKS proxy and ask it to forward UDP packets on the app's behalf until that TCP connection is closed. On Linux, it is also possible to add the lines below to the /etc/ld.so. LDPRELOAD'libdl.so libdsocks.so' export LDPRELOAD. SOCKS v4 does not support UDP (or IPv6), but SOCKS v5 does. For the Bourne shell/bash, the following lines can be added to the appropriate startup files, such as /etc/profile, /.profile, or /.bashrc. That also allows the proxy to know who is requesting the forwarding so it can route matching inbound packets back to that same requester. Tools like CCProxy, Proxycap, Proxifier, etc work (for TCP, anyway) by intercepting outgoing TCP conections and redirecting them to the proxy server, transparently handling any proxy handshaking to set up forwarding, before then allowing any application data to flow through the TCP connection. Any kind of proxy, whether it is for TCP or UDP, needs to be told where to forward outgoing packets to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |