What is the difference between tun2proxy and tun2socks?

[piqihaha]

What is the difference between tun2proxy and tun2socks? Why does the test version have tun2proxy option?

[piqihaha]

ime="2025-01-16T12:33:45Z" level=warning msg="[TCP] dial 1.1.1.1:53: CONNECT: connection not allowed by ruleset"
time="2025-01-16T12:33:46Z" level=warning msg="[TCP] dial 1.1.1.1:53: CONNECT: connection not allowed by ruleset"
time="2025-01-16T12:33:46Z" level=info msg="[TCP] 198.18.0.1:32872 <-> 1.1.1.1:53"
time="2025-01-16T12:33:46Z" level=info msg="[TCP] 198.18.0.1:32870 <-> 1.1.1.1:53"
time="2025-01-16T12:33:47Z" level=info msg="[TCP] 198.18.0.1:32886 <-> 1.1.1.1:53"
time="2025-01-16T12:33:47Z" level=warning msg="[TCP] dial 1.1.1.1:53: CONNECT: connection not allowed by ruleset"
time="2025-01-16T12:33:47Z" level=info msg="[TCP] 198.18.0.1:53798 <-> 172.67.70.165:443"
time="2025-01-16T12:33:48Z" level=warning msg="[TCP] dial 1.0.0.1:53: CONNECT: connection not allowed by ruleset"
time="2025-01-16T12:33:48Z" level=warning msg="[TCP] dial 172.253.62.99:443: CONNECT: connection not allowed by ruleset"
time="2025-01-16T12:33:49Z" level=info msg="[TCP] 198.18.0.1:55562 <-> 1.0.0.1:53"
time="2025-01-16T12:34:05Z" level=info msg="[TCP] 198.18.0.1:44796 <-> 1.1.1.1:53"
time="2025-01-16T12:34:05Z" level=warning msg="[TCP] dial 172.67.70.165:443: CONNECT: connection not allowed by ruleset"

Use tun2socks
He keeps having this problem. I changed the DNS server. For example, 8.8.8.8 8.8.4.4. Still the same. Is there something wrong with the IP of the proxy service?

[engageub]

Hello,
Tun2Proxy and Tun2socks are both containers designed to redirect traffic from the container to a proxy server. You have the flexibility to use either of these in the test branch.

Please note that with older kernel versions, Tun2socks may not function as expected. In such cases, it is recommended to switch to Tun2Proxy for optimal performance.

Additionally, when logging is enabled in the properties.conf file, it is set to debug mode by default

Regarding the warning message it seems like you're encountering a "connection not allowed by ruleset" error, possibly when trying to access a service or network.
It is clear from the logs that DNS over HTTPS is being used.
Either your proxy is blocking the requests or cloudflare is not sending the response as expected or your application is using a different method while connecting.

Log Breakdown and Troubleshooting Steps

The log entries you provided suggest that there's an issue with making a TCP connection to a remote DNS server (1.1.1.1 on port 53). The error message indicates that the connection is being blocked due to a "ruleset" issue. Below is a breakdown of the log and potential causes and solutions.

Log Breakdown:

1. Warnings (level=warning):

   • The warning messages indicate that a connection attempt was made to 1.1.1.1:53 (DNS service) but was rejected due to a "ruleset" restriction.
   • Error Message: [TCP] dial 1.1.1.1:53: CONNECT: connection not allowed by ruleset

2. Info Messages (level=info):

   • Despite the warnings, there are successful connections to the DNS server on port 53 from the internal IP 198.18.0.1. This indicates that some connections are succeeding, while others are being blocked.
   • Example: [TCP] 198.18.0.1:32872 <-> 1.1.1.1:53

3. Repeated Warnings:

   • The repeated warnings suggest that while some connection attempts are successful, others are intermittently being blocked.

Potential Causes and Solutions:

1. Firewall Rules:

   • A firewall on your system or network might be blocking connections to port 53 for specific IP addresses or protocols.
   • Solution: Check your firewall rules to ensure that outgoing connections to 1.1.1.1:53 are allowed. Also, check for any restrictive rules related to CONNECT or TCP traffic.

2. Proxy or Security Policies:

   • If you're using a proxy or security software (e.g., a network gateway with a ruleset), it might be blocking certain types of connections, especially CONNECT requests.
   • Solution: Review your proxy server or security software's rules. Ensure that TCP connections to external DNS servers (port 53) are allowed. If using a web proxy, make sure it allows DNS traffic.

3. DNS Server Issues:

   • Although unlikely (due to both successful and unsuccessful connection attempts), there may be temporary issues or rate limiting with the DNS server you're trying to contact (1.1.1.1).
   • Solution: Test using a different DNS server (e.g., Google's 8.8.8.8) to see if the issue persists.

4. Application-Specific Restrictions:

   • The application you're using might have its own set of rules or restrictions on outgoing connections.
   • Solution: If this is occurring in a specific application (e.g., a VPN or network tool), check its settings or documentation to identify any restrictions or connection limits.

5. Network Configuration (Router or NAT):

   • If you're behind a router or NAT (Network Address Translation), it could be filtering or blocking outgoing DNS requests.
   • Solution: Check your router or network configuration to ensure that outgoing DNS queries are not being blocked.

6. TLS/SSL Tunneling (if using CONNECT method):

   • If you're using SSL/TLS tunneling (common for HTTPS connections via proxies), some proxies may block CONNECT requests to certain destinations unless explicitly configured.
   • Solution: If you're using an HTTPS proxy or VPN, make sure it's configured to allow CONNECT on port 53 for DNS requests.