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.

[xialvjun]

Sorry for not replying sooner.

I want to use tcpip.js in nodejs. I want to start a tun interface with packages like appium-ios-tuntap or utun , treat it like a normal socket object or Duplex stream. Then

const utun = new UTUN(xxx):
const utunSocket = customFunction(utun);

const tunInterface = await stack.interfaces.createTun({
  ip: '192.168.1.1/24',
});

// First call `pipeTo()` to begin listening
tunInterface.readable.pipeTo(utunSocket.writable);
utunSocket.readable.pipeTo(tunInterface.writable);

const allTcpConnections = await stack.tcp.listenAll();

for await (const connection of allTcpConnections) {
  // Process incoming connection
}

With this, I needn't to parse and split and construct IpPacket.