利用Cloudflare Tunnel 进行内网穿透

ubuntu@ubuntu:~$ cloudflared loginPlease open the following URL and log in with your Cloudflare account:
https://dash.cloudflare.com/argotunnel?callback=https%3A%2F%2Flogin.cloudflareaccess.org%2FRl3hix8lZBOXDNuSgnGsRNsKoM98SsecBz_S7dSxtyg%3D
Leave cloudflared running to download the cert automatically.You have successfully logged in.If you wish to copy your credentials to a server, they have been saved to:/home/ubuntu/.cloudflared/cert.pem

ubuntu@ubuntu:~$ cloudflared tunnel create testTunnel credentials written to /home/ubuntu/.cloudflared/9a9001bf-0015-4047-b196-9568ccff947a.json. cloudflared chose this file based on where your origin certificate was found. Keep this file secret. To revoke these credentials, delete the tunnel.
Created tunnel test with id 9a9001bf-0015-4047-b196-9568ccff947aubuntu@ubuntu:~$ cloudflared tunnel route dns 9a9001bf-0015-4047-b196-9568ccff947a test.y4er.com2022-09-27T09:49:04Z INF Added CNAME test.y4er.com which will route to this tunnel tunnelID=9a9001bf-0015-4047-b196-9568ccff947aubuntu@ubuntu:~$

cloudflared tunnel --name test --url rdp://127.0.0.1cloudflared tunnel --name test --url http://127.0.0.1:8080cloudflared tunnel --name test --url tcp://127.0.0.1:3306

ubuntu@ubuntu:~$ cloudflared tunnel --name test --url rdp://127.0.0.12022-09-27T09:52:52Z INF Reusing existing tunnel with this name tunnelID=9a9001bf-0015-4047-b196-9568ccff947a2022-09-27T09:52:52Z INF Starting tunnel tunnelID=9a9001bf-0015-4047-b196-9568ccff947a2022-09-27T09:52:52Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]2022-09-27T09:52:52Z INF Version 2022.9.12022-09-27T09:52:52Z INF GOOS: linux, GOVersion: go1.18.6, GoArch: amd642022-09-27T09:52:52Z INF Settings: map[n:test name:test url:rdp://127.0.0.1]2022-09-27T09:52:52Z INF cloudflared will not automatically update when run from the shell. To enable auto-updates, run cloudflared as a service: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/run-tunnel/as-a-service/2022-09-27T09:52:52Z INF Generated Connector ID: a1da23e2-cdfc-44db-a0b0-2428e8c4a85a2022-09-27T09:52:52Z INF Initial protocol quic2022-09-27T09:52:52Z INF Starting metrics server on 127.0.0.1:45235/metrics2022/09/27 09:52:52 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.2022-09-27T09:52:53Z INF Connection de1df8d6-3983-4944-8a70-6c62ed96404b registered connIndex=0 ip=198.41.200.33 location=SJC2022-09-27T09:52:55Z INF Connection 815b9bee-5b7b-4abd-badc-3dc397143278 registered connIndex=2 ip=198.41.200.73 location=SJC2022-09-27T09:52:55Z INF Connection 842a5dc0-698c-454c-8a92-7bb0c9560b0e registered connIndex=3 ip=198.41.192.107 location=LAX2022-09-27T09:52:58Z WRN Failed to create new quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=1 ip=198.41.192.2272022-09-27T09:52:58Z INF Retrying connection in up to 2s seconds connIndex=1 ip=198.41.192.2272022-09-27T09:52:58Z WRN Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=1

cloudflared access rdp --hostname test.y4er.com --listener 127.0.0.1:3389

[program:cloudflared]command=cloudflared tunnel --name test --url rdp://127.0.0.1dircetory=/usr/local/bin/     #进程目录autostart=true     #在supervisord启动的时候是否自动启动autorestart=true     #程序退出后是否自动重启#日志输出stderr_logfile=/tmp/client_stderr.logstdout_logfile=/tmp/client_stdout.loguser=ubuntu

cloudflared service install

cloudflared tunnel --name test --bastion

cloudflared access tcp --hostname test.y4er.com --listener 127.0.0.1:3389 --destination 127.0.0.1:3389