莱卡云香港的CN2 GIA测试数据

-

 -------------------- A Bench.sh Script By Teddysun -------------------

 Version            : v2023-06-10

 Usage              : wget -qO- bench.sh | bash

----------------------------------------------------------------------

 CPU Model          : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz

 CPU Cores          : 2 @ 2299.996 MHz

 CPU Cache          : 46080 KB

 AES-NI             : Enabled

 VM-x/AMD-V         : Enabled

 Total Disk         : 38.1 GB (3.4 GB Used)

 Total Mem          : 3.8 GB (714.1 MB Used)

 Total Swap         : 975.0 MB (0 Used)

 System uptime      : 0 days, 15 hour 31 min

 Load average       : 0.06, 0.02, 0.00

 OS                 : Debian GNU/Linux 11

 Arch               : x86_64 (64 Bit)

 Kernel             : 5.10.0-22-amd64

 TCP CC             : cubic

 Virtualization     : KVM

 IPv4/IPv6          : Online / Offline

 Organization       : AS64050 BGPNET Global ASN

 Location           : Hong Kong / HK

 Region             : Central and Western

----------------------------------------------------------------------

 I/O Speed(1st run) : 256 MB/s

 I/O Speed(2nd run) : 224 MB/s

 I/O Speed(3rd run) : 203 MB/s

 I/O Speed(average) : 227.7 MB/s

----------------------------------------------------------------------

 Node Name        Upload Speed      Download Speed      Latency     

 Speedtest.net    4.72 Mbps         9.56 Mbps           31.03 ms    

 Los Angeles, US  4.69 Mbps         10.00 Mbps          149.10 ms   

 Dallas, US       4.82 Mbps         9.67 Mbps           175.67 ms   

 Montreal, CA     4.73 Mbps         9.89 Mbps           211.52 ms   

 Paris, FR        4.76 Mbps         9.97 Mbps           243.11 ms   

 Amsterdam, NL    4.77 Mbps         10.21 Mbps          250.33 ms   

 Shanghai, CN     4.70 Mbps         9.52 Mbps           57.44 ms    

 Nanjing, CN      4.75 Mbps         9.82 Mbps           97.84 ms    

 Hongkong, CN     4.75 Mbps         9.54 Mbps           1.70 ms     

 Singapore, SG    4.57 Mbps         10.06 Mbps          36.00 ms    

 Tokyo, JP        4.68 Mbps         9.89 Mbps           101.54 ms   

----------------------------------------------------------------------

 Finished in        : 4 min 26 sec

 Timestamp          : 2023-08-10 20:48:09 EDT

----------------------------------------------------------------------

root@debian:~# curl -sL yabs.sh | bash

# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

#              Yet-Another-Bench-Script              #

#                     v2023-04-23                    #

# https://github.com/masonr/yet-another-bench-script #

# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #


Thu 10 Aug 2023 08:48:31 PM EDT


Basic System Information:

---------------------------------

Uptime     : 0 days, 15 hours, 36 minutes

Processor  : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz

CPU cores  : 2 @ 2299.996 MHz

AES-NI     : ✔ Enabled

VM-x/AMD-V : ✔ Enabled

RAM        : 3.8 GiB

Swap       : 975.0 MiB

Disk       : 38.1 GiB

Distro     : Debian GNU/Linux 11 (bullseye)

Kernel     : 5.10.0-22-amd64

VM Type    : KVM

IPv4/IPv6  : ✔ Online / ❌ Offline


IPv4 Network Information:

---------------------------------

ISP        : Network Limited Co., Ltd

ASN        : AS64050 BGPNET Global ASN

Host       : BGP Network Limited Co., Ltd

Location   : Chai Wan, Eastern (HEA)

Country    : Hong Kong


fio Disk Speed Tests (Mixed R/W 50/50):

---------------------------------

Block Size | 4k            (IOPS) | 64k           (IOPS)

  ------   | ---            ----  | ----           ---- 

Read       | 8.28 MB/s     (2.0k) | 130.00 MB/s   (2.0k)

Write      | 8.31 MB/s     (2.0k) | 130.68 MB/s   (2.0k)

Total      | 16.60 MB/s    (4.1k) | 260.69 MB/s   (4.0k)

           |                      |                     

Block Size | 512k          (IOPS) | 1m            (IOPS)

  ------   | ---            ----  | ----           ---- 

Read       | 226.86 MB/s    (443) | 197.56 MB/s    (192)

Write      | 238.91 MB/s    (466) | 210.72 MB/s    (205)

Total      | 465.77 MB/s    (909) | 408.28 MB/s    (397)


iperf3 Network Speed Tests (IPv4):

---------------------------------

Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           

-----           | -----                     | ----            | ----            | ----           

Performing IPv4 iperf3 send test to Clouvider (Attempt #1 of 3)Performing IPv4 iperf3 send test to Clouvider (Attempt #2 of 3)Performing IPv4 iperf3 send test to Clouvider (Attempt #3 of 3)Performing IPv4 iperf3 recv test from Clouvider (Attempt #1 of Performing IPv4 iperf3 recv test from Clouvider (Attempt #2 of Clouvider       | London, UK (10G)          | busy            | 9.26 Mbits/sec  | 238 ms         

Performing IPv4 iperf3 send test to Scaleway (Attempt #1 of 3).Performing IPv4 iperf3 send test to Scaleway (Attempt #2 of 3).Performing IPv4 iperf3 send test to Scaleway (Attempt #3 of 3).Performing IPv4 iperf3 recv test from Scaleway (Attempt #1 of 3Performing IPv4 iperf3 recv test from Scaleway (Attempt #2 of 3Performing IPv4 iperf3 recv test from Scaleway (Attempt #3 of 3Scaleway        | Paris, FR (10G)           | busy            | busy            | 249 ms         

Performing IPv4 iperf3 send test to NovoServe (Attempt #1 of 3)Performing IPv4 iperf3 send test to NovoServe (Attempt #2 of 3)Performing IPv4 iperf3 send test to NovoServe (Attempt #3 of 3)Performing IPv4 iperf3 recv test from NovoServe (Attempt #1 of Performing IPv4 iperf3 recv test from NovoServe (Attempt #2 of Performing IPv4 iperf3 recv test from NovoServe (Attempt #3 of NovoServe       | North Holland, NL (40G)   | busy            | busy            | 249 ms         

Performing IPv4 iperf3 send test to Uztelecom (Attempt #1 of 3)Performing IPv4 iperf3 send test to Uztelecom (Attempt #2 of 3)Performing IPv4 iperf3 send test to Uztelecom (Attempt #3 of 3)Performing IPv4 iperf3 recv test from Uztelecom (Attempt #1 of Performing IPv4 iperf3 recv test from Uztelecom (Attempt #2 of Performing IPv4 iperf3 recv test from Uztelecom (Attempt #3 of Uztelecom       | Tashkent, UZ (10G)        | busy            | busy            | 186 ms         

Performing IPv4 iperf3 send test to Clouvider (Attempt #1 of 3)Performing IPv4 iperf3 send test to Clouvider (Attempt #2 of 3)Performing IPv4 iperf3 send test to Clouvider (Attempt #3 of 3)Performing IPv4 iperf3 recv test from Clouvider (Attempt #1 of Performing IPv4 iperf3 recv test from Clouvider (Attempt #2 of Performing IPv4 iperf3 recv test from Clouvider (Attempt #3 of Clouvider       | NYC, NY, US (10G)         | busy            | 9.27 Mbits/sec  | 221 ms         

Performing IPv4 iperf3 send test to Clouvider (Attempt #1 of 3)Performing IPv4 iperf3 send test to Clouvider (Attempt #2 of 3)Performing IPv4 iperf3 recv test from Clouvider (Attempt #1 of Performing IPv4 iperf3 recv test from Clouvider (Attempt #2 of Performing IPv4 iperf3 recv test from Clouvider (Attempt #3 of Clouvider       | Dallas, TX, US (10G)      | 4.56 Mbits/sec  | 9.47 Mbits/sec  | 188 ms         

Performing IPv4 iperf3 send test to Clouvider (Attempt #1 of 3)Performing IPv4 iperf3 send test to Clouvider (Attempt #2 of 3)Performing IPv4 iperf3 recv test from Clouvider (Attempt #1 of Clouvider       | Los Angeles, CA, US (10G) | 4.57 Mbits/sec  | 9.40 Mbits/sec  | 158 ms         


Geekbench 6 Benchmark Test:

---------------------------------

Test            | Value                         

                |                               

Single Core     | 919                           

Multi Core      | 1640                          

Full Test       | https://browser.geekbench.com/v6/cpu/2221015


YABS completed in 18 min 48 sec

root@debian:~# wget -q route.f2k.pub -O route && bash route


[Info] Debian Update

Hit:1 http://deb.debian.org/debian bullseye InRelease

Hit:2 https://download.docker.com/linux/debian bullseye InRelease

Reading package lists... Done         

Building dependency tree... Done

Reading state information... Done

All packages are up to date.

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

The following NEW packages will be installed:

  traceroute

0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.

Need to get 55.7 kB of archives.

After this operation, 162 kB of additional disk space will be used.

Get:1 http://deb.debian.org/debian bullseye/main amd64 traceroute amd64 1:2.1.0-2+deb11u1 [55.7 kB]

Fetched 55.7 kB in 0s (907 kB/s)    

Selecting previously unselected package traceroute.

(Reading database ... 24329 files and directories currently installed.)

Preparing to unpack .../traceroute_1%3a2.1.0-2+deb11u1_amd64.deb ...


Progress: [  0%] [.........................................] 

Unpacking traceroute (1:2.1.0-2+deb11u1) ..................] 


Setting up traceroute (1:2.1.0-2+deb11u1) .................] 


[Info] KOS工具箱 

[Info] https://kostool.cn 


[Info] 你是第 25209 次运行该脚本的小伙伴

[Info] 开始测试，请稍后...

——————————————————————————————


目标:北京电信[219.141.136.10]   回程线路:电信CN2 GT(AS4134)


目标:北京联通[202.106.196.115]  回程线路:电信CN2 GT(AS4134)


目标:北京移动[211.136.28.231]   回程线路:电信CN2 GT(AS4134)


目标:上海电信[202.96.199.132]   回程线路:电信CN2 GIA(AS4809)


目标:上海联通[211.95.72.1]      回程线路:电信CN2 GT(AS4134)


目标:上海移动[211.136.112.50]   回程线路:电信CN2 GIA(AS4809)


目标:广州电信[61.144.56.100]    回程线路:电信CN2 GT(AS4134)


目标:广州联通[211.95.193.97]    回程线路:电信CN2 GIA(AS4809)


目标:广州移动[120.196.122.69]   回程线路:电信CN2 GT(AS4134)


——————————————————————————————


[Info] 测试完成，用时 96 秒。结果仅供参考


root@debian:~# wget -qO- git.io/besttrace | bash

--2023-08-10 21:09:53--  https://github.com/zq/shell/raw/master/besttrace2021

Resolving github.com (github.com)... 20.205.243.166

Connecting to github.com (github.com)|20.205.243.166|:443... connected.

HTTP request sent, awaiting response... 302 Found

----------------------------------------------------------------------

北京电信

traceroute to 219.141.147.210 (219.141.147.210), 30 hops max, 32 byte packets

 1  10.0.154.1  0.22 ms  http: 403  http: 403

 2  1.32.228.1  10.86 ms  http: 403  http: 403

 3  *

 4  172.20.13.60  22.09 ms  http: 403  http: 403

 5  203.34.194.93  0.71 ms  http: 403  http: 403

 6  203.22.177.201  1.30 ms  http: 403  http: 403

 7  203.22.178.102  33.81 ms  http: 403  http: 403

 8  59.43.181.245  36.90 ms  http: 403  http: 403

 9  59.43.19.93  43.67 ms  http: 403  http: 403

10  *

11  *

12  6.254.120.106.static.bjtelecom.net (106.120.254.6)  166.52 ms  http: 403  http: 403

13  bj141-147-210.bjtelecom.net (219.141.147.210)  43.30 ms  http: 403  http: 403


----------------------------------------------------------------------

上海电信

traceroute to 202.96.209.133 (202.96.209.133), 30 hops max, 32 byte packets

 1  10.0.154.1  0.18 ms  http: 403  http: 403

 2  1.32.228.1  0.54 ms  http: 403  http: 403

 3  10.10.10.105  0.55 ms  http: 403  http: 403

 4  172.20.13.60  0.56 ms  http: 403  http: 403

 5  203.34.194.93  0.66 ms  http: 403  http: 403

 6  203.22.177.225  2.86 ms  http: 403  http: 403

 7  203.22.178.86  23.52 ms  http: 403  http: 403

 8  59.43.39.165  25.22 ms  http: 403  http: 403

 9  59.43.159.97  25.51 ms  http: 403  http: 403

10  61.152.24.198  26.95 ms  http: 403  http: 403

11  101.95.89.162  24.80 ms  http: 403  http: 403

12  124.74.229.230  27.59 ms  http: 403  http: 403

13  ns-pd.online.sh.cn (202.96.209.133)  29.68 ms  http: 403  http: 403


----------------------------------------------------------------------

深圳电信

traceroute to 58.60.188.222 (58.60.188.222), 30 hops max, 32 byte packets

 1  10.0.154.1  0.18 ms  http: 403  http: 403

 2  1.32.228.1  8.86 ms  http: 403  http: 403

 3  *

 4  172.20.13.60  2.74 ms  http: 403  http: 403

 5  203.34.194.93  0.82 ms  http: 403  http: 403

 6  203.22.177.201  1.71 ms  http: 403  http: 403

 7  203.22.178.94  6.03 ms  http: 403  http: 403

 8  *

 9  *

10  59.43.132.118  16.24 ms  http: 403  http: 403

11  114.104.38.59.broad.fs.gd.dynamic.163data.com.cn (59.38.104.114)  16.31 ms  http: 403  http: 403

12  *

13  58.60.188.222  10.72 ms  http: 403  http: 403


----------------------------------------------------------------------

北京联通

traceroute to 202.106.50.1 (202.106.50.1), 30 hops max, 32 byte packets

 1  10.0.154.1  0.18 ms  http: 403  http: 403

 2  1.32.228.1  0.47 ms  http: 403  http: 403

 3  *

 4  172.20.13.142  14.26 ms  http: 403  http: 403

 5  203.34.194.93  2.03 ms  http: 403  http: 403

 6  203.22.177.197  3.51 ms  http: 403  http: 403

 7  203.22.178.102  36.25 ms  http: 403  http: 403

 8  59.43.249.54  37.43 ms  http: 403  http: 403

 9  59.43.132.17  42.41 ms  http: 403  http: 403

10  202.97.42.13  50.91 ms  http: 403  http: 403

11  *

12  219.158.44.113  38.03 ms  http: 403  http: 403

13  219.158.4.153  42.00 ms  http: 403  http: 403

14  *

15  202.106.50.1  38.90 ms  http: 403  http: 403


----------------------------------------------------------------------

上海联通

traceroute to 210.22.97.1 (210.22.97.1), 30 hops max, 32 byte packets

 1  10.0.154.1  0.15 ms  http: 403  http: 403

 2  1.32.228.1  11.78 ms  http: 403  http: 403

 3  *

 4  172.20.13.142  1.74 ms  http: 403  http: 403

 5  203.34.194.93  0.68 ms  http: 403  http: 403

 6  203.22.177.221  1.21 ms  http: 403  http: 403

 7  203.22.178.86  25.27 ms  http: 403  http: 403

 8  59.43.247.225  25.13 ms  http: 403  http: 403

 9  59.43.159.97  25.49 ms  http: 403  http: 403

10  219.158.38.241  36.19 ms  http: 403  http: 403

11  *

12  *

13  *

14  210.22.97.1  28.42 ms  http: 403  http: 403


----------------------------------------------------------------------

深圳联通

traceroute to 210.21.196.6 (210.21.196.6), 30 hops max, 32 byte packets

 1  10.0.154.1  0.17 ms  http: 403  http: 403

 2  1.32.228.1  0.44 ms  http: 403  http: 403

 3  10.10.10.105  0.45 ms  http: 403  http: 403

 4  172.20.13.142  1.59 ms  http: 403  http: 403

 5  203.34.194.93  3.00 ms  http: 403  http: 403

 6  69.194.165.153  1.84 ms  http: 403  http: 403

 7  *

 8  *

 9  *

10  219.158.40.169  14.54 ms  http: 403  http: 403

11  *

12  120.86.0.58  12.12 ms  http: 403  http: 403

13  120.80.147.254  19.07 ms  http: 403  http: 403

14  dns2-ftcg.gdsz.cncnet.net (210.21.196.6)  15.42 ms  http: 403  http: 403


----------------------------------------------------------------------

北京移动

traceroute to 221.179.155.161 (221.179.155.161), 30 hops max, 32 byte packets

 1  10.0.154.1  0.20 ms  http: 403  http: 403

 2  1.32.228.1  12.63 ms  http: 403  http: 403

 3  *

 4  172.20.13.60  6.69 ms  http: 403  http: 403

 5  203.34.194.93  4.45 ms  http: 403  http: 403

 6  203.22.177.201  4.00 ms  http: 403  http: 403

 7  203.22.178.102  38.41 ms  http: 403  http: 403

 8  59.43.249.54  38.30 ms  http: 403  http: 403

 9  59.43.132.17  44.80 ms  http: 403  http: 403

10  *

11  202.97.17.90  42.10 ms  http: 403  http: 403

12  221.183.86.49  38.90 ms  http: 403  http: 403

13  221.183.94.21  39.43 ms  http: 403  http: 403

14  *

15  *

16  cachedns03.bj.chinamobile.com (221.179.155.161)  44.57 ms  http: 403  http: 403


----------------------------------------------------------------------

上海移动

traceroute to 211.136.112.200 (211.136.112.200), 30 hops max, 32 byte packets

 1  10.0.154.1  0.26 ms  http: 403  http: 403

 2  1.32.228.1  0.33 ms  http: 403  http: 403

 3  *

 4  172.20.13.60  1.06 ms  http: 403  http: 403

 5  203.34.194.93  0.77 ms  http: 403  http: 403

 6  203.22.177.225  2.77 ms  http: 403  http: 403

 7  *

 8  59.43.39.161  23.60 ms  http: 403  http: 403

 9  59.43.159.97  25.58 ms  http: 403  http: 403

10  *

11  *

12  221.183.123.101  29.16 ms  http: 403  http: 403

13  221.183.90.241  29.25 ms  http: 403  http: 403

14  *

15  221.181.125.178  30.35 ms  http: 403  http: 403

16  211.136.112.252  29.44 ms  http: 403  http: 403

17  211.136.112.200  31.25 ms  http: 403  http: 403


----------------------------------------------------------------------

深圳移动

traceroute to 120.196.165.24 (120.196.165.24), 30 hops max, 32 byte packets

 1  10.0.154.1  0.82 ms  http: 403  http: 403

 2  1.32.228.1  4.21 ms  http: 403  http: 403

 3  *

 4  172.20.13.60  3.81 ms  http: 403  http: 403

 5  203.34.194.93  4.45 ms  http: 403  http: 403

 6  203.22.177.106  3.14 ms  http: 403  http: 403

 7  203.22.178.94  5.39 ms  http: 403  http: 403

 8  59.43.250.169  8.06 ms  http: 403  http: 403

 9  59.43.16.165  11.18 ms  http: 403  http: 403

10  *

11  *

12  *

13  *

14  221.183.71.78  37.06 ms  http: 403  http: 403

15  221.183.110.166  40.84 ms  http: 403  http: 403

16  ns6.gd.cnmobile.net (120.196.165.24)  38.91 ms  http: 403  http: 403


----------------------------------------------------------------------

成都教育网

traceroute to 202.112.14.151 (202.112.14.151), 30 hops max, 32 byte packets

 1  10.0.154.1  0.13 ms  http: 403  http: 403

 2  1.32.228.1  4.53 ms  http: 403  http: 403

 3  *

 4  172.20.13.60  2.43 ms  http: 403  http: 403

 5  203.34.194.93  2.11 ms  http: 403  http: 403

 6  203.22.177.225  10.05 ms  http: 403  http: 403

 7  *

 8  *

 9  *

10  *

11  202.97.29.154  44.99 ms  http: 403  http: 403

12  *

 [流媒体平台及游戏区域限制测试]


项目地址 https://github.com/lmc999/RegionRestrictionCheck 

BUG反馈或使用交流可加TG群组 https://t.me/gameaccelerate 

脚本适配OS: CentOS 6+, Ubuntu 14.04+, Debian 8+, MacOS, Android (Termux), iOS (iSH)

 [流媒体平台及游戏区域限制测试]


项目地址 https://github.com/lmc999/RegionRestrictionCheck 

BUG反馈或使用交流可加TG群组 https://t.me/gameaccelerate 

脚本适配OS: CentOS 6+, Ubuntu 14.04+, Debian 8+, MacOS, Android (Termux), iOS (iSH)


 ** 测试时间: Thu 10 Aug 2023 09:15:47 PM EDT


 ** 正在测试IPv4解锁情况 

--------------------------------

 ** 您的网络为: BGPNET Global (1.32.*.*) 



============[ Multination ]============

 Dazn:                                  No

 HotStar:                               No

 Disney+:                               Yes (Region: JP)

 Netflix:                               Yes (Region: JP)

 YouTube Premium:                       Yes (Region: SG)

 Amazon Prime Video:                    Yes (Region: JP)

 TVBAnywhere+:                          Yes

 iQyi Oversea Region:                   HK

 Viu.com:                               Yes (Region: SG)

 YouTube CDN:                           FPT in Hanoi 

 Netflix Preferred CDN:                 Singapore  

 Spotify Registration:                  No

 Steam Currency:                        SGD

 ChatGPT:                               Yes

=======================================

=============[ Hong Kong ]=============

 Now E:                                 Failed (Unexpected Result: )

 Viu.TV:                                No

 MyTVSuper:                             No

 HBO GO Asia:                           Yes (Region: SG)

 BiliBili Hongkong/Macau/Taiwan:        Yes

=======================================

当前主机不支持IPv6,跳过...


本次测试已结束，感谢使用此脚本 


检测脚本当天运行次数: 854; 共计运行次数: 6468961 


【AD No.1】

================================================

香港、新加坡、美国Epyc SSD BGP 服务器！


✅ 香港Epyc 7D12 4C8G 300GSSD数据盘 +200Mbps不限流量 = 129元/月

✅ 新加坡Epyc 7R12 4C8G 200GSSD数据盘 +200Mbps不限流量 = 89元/月

✅ 硅谷Epyc 7R12 4C8G 300GSSD数据盘 +300Mbps不限流量 = 59元/月

✅ 迪拜本地IP VPS Tiktok等电商业务首选


更多套餐优惠请访问 https://iPraft.com  或TG联系 @ipraft

================================================


【AD No.2】

================================================

流媒体家宽DNS解锁!


✅  日本

✅  韩国

✅  泰国

✅  台湾

✅  美国

✅  澳洲

✅  英国

✅  德国

✅  法国

✅  荷兰

✅  巴西

✅  智利

✅  印度

✅  加拿大

✅  土耳其

✅  阿根廷


以上区域均保证Netflix、Disney+及当地流媒体

了解详情请关注频道: https://t.me/LMT_Unblock

================================================

root@debian:~# 


评论

发表评论

此博客中的热门博文

始终免费的vps！甲骨文云（oracle）抢注册高性能ARM实例！一键脚本部署！

-
图片
  写在前面 前面给大家分享过如何注册甲骨文云（oracle）的账号！相信已经有很多小伙伴申请到了自己的免费甲骨文云vps。恭喜大家～ 相信大家也听说过甲骨文云有性能强悍的ARM资源，无奈资源紧张手动申请基本提示资源不足～ 今天就跟着小鑫一起用R探长编译的一键脚本，刷心仪的ARM机器资源！ 准备工作 1、一台vps，系统推荐Debian、Ubuntu 2、telegram账号一个，点击关注（ R探长 ）和（ R探长的小助理 ） 3、一个甲骨文云的账号 4、一键脚本（R探长GitHub项目地址）： 点击访问 获取tg、vps信息 我们打开 telegram，找到刚才关注的机器人，发送指令 /sart，开始！ 在输入框里面输入 /raninfo，为了防止误触，需要输入两次，机器人会返回两行字符串，这些是我们 VPS 的标识！ 记录机器人返回的字符串（配置 VPS 会用到），这些字符串是机器人和 VPS 沟通的key。 获取甲骨文 API 密钥 点击实例，甲骨文右上角的人头像（会员中心），来到会员中心（也就是更改密码的界面），找到左下角的 API 密钥，点击右边的添加 API 密钥。 点击的 “下载私有密钥”，并保存到本地设备，这样会得到一个 ****.pem 的文件，这个是我们的 API 密钥文件，请妥善保管！ 点击添加，会弹出 “配置文件预览” 的窗口，我们需要记录里面的：“配置文件预览”！ VPS 服务端部署 VPS 端的部署，就更为简单了，一键脚本搞定！ 先更新组建 apt update -y apt install -y curl tar wget 安装更新完毕以后，执行下面的一键安装脚本 wget -O gz_client_bot.tar.gz https://github.com/semicons/java_oci_manage/releases/latest/download/gz_client_bot.tar.gz && tar -zxvf gz_client_bot.tar.gz --exclude=client_config && tar -zxvf gz_client_bot.tar.gz --skip-old-files client_config && chmod +x sh_client_b
阅读全文

LINUX | 谷歌云开启SSH及设置root密码

-
 一、设置root密码 1.先选择从浏览器打开ssh连接服务器 2.切换到root账号 sudo -i 3.设置root密码 passwd 然后会要求输入新密码，然后再重复一次密码，输入密码的时候不会显示出来，所以直接输入密码，然后回车，再然后重复输入密码回车 二、开启SSH权限 ①方法一 1.修改SSH配置文件/etc/ssh/sshd_config vi /etc/ssh/sshd_config 2.然后再输”i”进入编辑模式 i 3.找到以下内容并修改 PermitRootLogin yes           //默认为no，需要开启root用户访问改为yes PasswordAuthentication yes    //默认为no，改为yes开启密码登陆 4.修改完成后，再下按 esc 键，然后再输入 :wq 5.重启SSH服务 service sshd restart ②方法二 centOS和Debian通用，输入以下两条命令 sed -i 's/PermitRootLogin no/PermitRootLogin yes/g' /etc/ssh/sshd_config sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/g' /etc/ssh/sshd_config ubuntu系统，输入以下两条命令 sed -i 's/#PermitRootLogin prohibit-password/PermitRootLogin yes/g' /etc/ssh/sshd_config sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/g' /etc/ssh/sshd_config 重启服务器 reboot
阅读全文