Dynamic Port Forwarding not work

[mrzhou166]

Dynamic Port Forwarding not work

[kingToolbox]

Duplicate of #26

WindTerm_2.7.0_Prerelease_3 fixes the bug where dynamic port forwarding couldn't proxy DNS lookups. Please download and use it. Thank you.

[mrzhou166]

Thank you！

[DesistDaydream]

Not working with WindTerm Dynamic forwarding

I turned on dynamic forwarding

I configured the proxy as follows

But the session cannot be connected normally

Version 2.7.0 still has the same problem

---

Normally working program

If I use xShell or SecureCRT to enable dynamic forwarding, I can connect normally.

Additional

What other logs can I look at to get information about when the session connects?

Ref

#1364

#318

[kingToolbox]

Based on the data in the image, I think WindTerm is only binding to an IPv6 port, while SecureCrt is binding to both IPv6 and IPv4 ports. The proxy address you entered is 127.0.0.1 (IPv4), so WindTerm can't proxy. Try changing the proxy address to ::1 and see if that works.

[DesistDaydream]

The situation is the same when using ipv6

And there are some problems with the powshell command in my previous screenshot, ipv4 is also listening

[DesistDaydream]

Another issue in 2.7.0. after opening the tunnel and closing the tunnel and then closing the program, the background process still exists and the CPU usage is not low

[kingToolbox]

Could you try using a browser with a proxy set to port 1080 to see if you can access the network correctly? Or, try setting up the proxy through securecrt to see if it can access the network correctly. I need to confirm whether the port forwarding module or the proxy itself is the problem.

Based on the information you've provided, the port is being bound correctly, which likely means the port forwarding module is not the issue. Also, the proxy works fine through dynamic port forwarding with xshell or securecrt, so the proxy module itself seems okay. But the problem arises when the two are combined - is my understanding correct?

As for the lingering processes after closing the application, I will try to reproduce this separately later.

[DesistDaydream]

I have tried using the forwarding function on the browser, and the same problem occurs.

For example, this configuration of secureCRT can be opened normally.

But the same forwarding does not work in our WindTerm

---

The description of the second part is correct. The proxy itself is functioning normally, the main problem should be in the tunnel creation function

[kingToolbox]

Could you please provide a screenshot of the error page that appears in the second image when Chrome fails to open localhost:30443, to see if there's any error information or code? Also, why does your PowerShell screenshot only show IPv6 addresses and not IPv4 addresses?

[DesistDaydream]

I am also very curious why the tunnel opened by WindTerm now only has IPv6. I cannot reproduce the situation where I can open IPv4.

By the way. Is there any log I can view?