Can we listen all ports in listenTcp

[xialvjun]

I mean, like, build a tunnel proxy service.

Bind the virtual tun/tap interface to a real tun/tap interface, then listen to all ports, get all tcp connections the browser or other clients like curl want to create.

[gregnr]

Hey @xialvjun this is interesting. The answer is likely "not today" but something I think tcpip should support depending on what your use case is. There are many layers so just to make sure I understand your scenario:

• Where are you running tcpip.js? Browser / node.js / both?
• If browser, are you tunnelling the connection to the server somehow (e.g. websockets)?
• Where does curl fit in - just a regular curl client hitting an HTTP server or is this running in a v86 VM?

Any other details on the big picture of what you're building would be useful. One feature that I've been brainstorming is NAT/port forwarding which could act as a general purpose proxy for this use case. Happy to chat through my thoughts there if you're interested.