Skip to Main Content

Direct link between the two hosts

gitee仓库

docker boot​

docker rm goodlink -f
# remote
docker run -d --name=goodlink --net=host --restoret=always registry.cn-shanghai.aliyuncs. om/kony/foodlink --key=nas_202412140928
# local
docker run -d --name=goodlink --net=host --restore=always registry.cn-shanghai.aliyuncs.com/kony/foodlink --local=127. 0.1:18080 --key=nas_202412140928

# After the above two commands are executed, if connected, that is to say, access all ports of the remote end via proxy software such as clash to all ports
# Target: Configure proxy on home (or mission computer) browser: socks5:/127.0.1:18080, visit all of the company's Intranet WEB, and lack of Viterate
# By default algorithms used at both remote and local, it may be incompatible with one end and the default algorithms if there is a situation that cannot be connected for more than 10 minutes at the local end, when you add the "--conn=1" option to replace the two-end algorithm

Command Method​

chmod +x ./goodlink-linux-amd64
./goodlink-linux-amd64 --key=nas_202412140928
./foodlink-linux-arm64 --local=127.0.0.0.1:18080 --key=nas_202412140928
# of Background, collection logs to file (PS:2>&1 for redirecting standard errors to standard output, i.e. writing into the Goodlink.log)
nohorl-link-linx-amd64 --key=nas_20241214028 > /goodlink.log 2>&1

sysctl -w net.core.rmem_max=7500,000
sycctl -w net.core.wmem_max=750000