-S2 -S1 parameter tcp transfer is invalid under window, but there is no problem under linux

[chenxudong2020]

-S2 -S1 parameter tcp transfer is invalid under window, but there is no problem under Linux. I read the previous issue and found that it is not supported. However, the secondary development of Star Network n2n can indeed support it. Can you refer to their code to support window?

[hamishcoleman]

I have not heard of Star Network, nor can I find any URL for that project (the name is too generic to easily google for), however, the n3n project (that most of the n2n developers have moved on to) has started supporting TCP mode under Windows (see n42n/n3n#59)

[chenxudong2020]

https://www.starvpn.cn this is the website. 星空组网 I looked at their documentation and software and it seems that the client starts TCP and UDP monitoring at the same time. As long as one client changes to UDP transfer or TCP transfer is restarted, the other clients will also switch. This is their document introduction link https: //doc.starvpn.cn/#/windows

[hamishcoleman]

Thanks for the website - I would love to look at their code, but it appears that they have no code available and are violating the license - it is clearly based on n2n (even though their docs never mention it, their binaries have n2n strings throughout them) and was forked from 3.1.1-71-g9618512

[chenxudong2020]

Can the n3n project release a beta public test version? Is this n2n v3 version still updated?

[hamishcoleman]

There are public beta binaries for a n3n that has TCP support on Windows in the Artifacts at the bottom of https://github.com/hamishcoleman/n3n/actions/runs/12254985061

As for n2n - the two active developers left the n2n project about a year ago, and nobody from the corporate owner seems to be updating anything