qjfoidnh / BaiduPCS-Go

iikira/BaiduPCS-Go原版基础上集成了分享链接/秒传链接转存功能
Apache License 2.0
2.91k stars 441 forks source link

Another question #187

Open boyodyang opened 2 years ago

boyodyang commented 2 years ago

Another question: 我抓到的包PA前面没有netdisk;P2SP;3.0.0.8;这一段。这一段需不需要加上去?我看你给的都有,默认配置也有。

boyodyang commented 2 years ago

看样子这是一个p2p的协议的支持

boyodyang commented 2 years ago

刚解禁一天,这次改了自己的手机的cookie和ua,拖下来1T,10几小时没事。10线程5任务

boyodyang commented 2 years ago

就是看系统里面有90多个网络连接,正常吗?

qjfoidnh commented 2 years ago

pan_ua推荐按照 #172 构建,从老版本升级来的话ua可能不会更新,要手动修改

90多个连接都是baidupcs-go的么?10线程数有13个左右连接是正常的

boyodyang commented 2 years ago

tcp ESTAB 0 0 192.168.1.72:39904 117.91.181.37:https
tcp ESTAB 0 0 192.168.1.72:39380 171.107.85.37:https
tcp ESTAB 0 0 192.168.1.72:42764 178.32.111.96:22067
tcp ESTAB 0 0 192.168.1.72:59360 125.64.104.37:https
tcp CLOSE-WAIT 12516 0 192.168.1.72:46794 58.20.204.46:https
tcp ESTAB 0 0 192.168.1.72:35844 219.153.113.37:https
tcp CLOSE-WAIT 17096 0 192.168.1.72:33582 1.71.157.37:https
tcp ESTAB 11153 0 192.168.1.72:60034 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:59136 121.32.228.37:https
tcp ESTAB 0 0 192.168.1.72:48532 36.103.236.37:https
tcp ESTAB 0 0 192.168.1.72:58186 119.167.143.63:https
tcp CLOSE-WAIT 17072 0 192.168.1.72:41128 171.107.86.37:https
tcp ESTAB 0 0 192.168.1.72:41556 171.107.86.37:https
tcp ESTAB 0 0 192.168.1.72:22330 94.130.218.54:https
tcp ESTAB 0 0 192.168.1.72:40256 124.236.104.37:https
tcp CLOSE-WAIT 16823 0 192.168.1.72:59630 113.113.73.46:https
tcp SYN-SENT 0 1 192.168.1.72:39664 113.113.67.28:https
tcp ESTAB 0 0 192.168.1.72:60322 113.113.73.46:https
tcp CLOSE-WAIT 16804 0 192.168.1.72:59896 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:51258 36.104.159.37:https
tcp ESTAB 0 0 192.168.1.72:46492 203.56.69.37:https
tcp ESTAB 0 268 192.168.1.72:39662 113.113.67.28:https
tcp CLOSE-WAIT 17064 0 192.168.1.72:44666 125.74.1.37:https
tcp CLOSE-WAIT 12562 0 192.168.1.72:59858 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:60946 125.72.219.37:https
tcp CLOSE-WAIT 17084 0 192.168.1.72:44706 121.227.7.37:https
tcp ESTAB 0 0 192.168.1.72:41536 171.107.86.37:https
tcp ESTAB 0 0 192.168.1.72:44796 117.34.37.37:https
tcp ESTAB 12536 0 192.168.1.72:59954 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:35868 175.6.206.37:https
tcp ESTAB 0 0 192.168.1.72:41552 123.184.220.37:https
tcp ESTAB 0 0 192.168.1.72:52450 118.112.225.37:https
tcp CLOSE-WAIT 16807 0 192.168.1.72:59904 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:40298 182.140.225.37:https
tcp ESTAB 0 0 192.168.1.72:55300 180.97.198.37:https
tcp ESTAB 0 0 192.168.1.72:microsoft-ds 192.168.1.126:2658
tcp ESTAB 0 0 192.168.1.72:55740 58.217.200.37:https
tcp ESTAB 0 0 192.168.1.72:44726 111.177.8.37:https
tcp ESTAB 0 0 192.168.1.72:46508 218.95.196.37:https
tcp ESTAB 17085 0 192.168.1.72:33622 218.93.204.37:https
tcp ESTAB 0 0 192.168.1.72:41570 123.184.220.37:https
tcp ESTAB 17048 0 192.168.1.72:34332 1.182.48.37:https
tcp ESTAB 0 0 192.168.1.72:35276 116.177.248.88:https
tcp ESTAB 0 0 192.168.1.72:44876 125.74.1.37:https
tcp ESTAB 0 0 192.168.1.72:60324 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:56096 125.74.40.37:https
tcp CLOSE-WAIT 16797 0 192.168.1.72:46694 58.20.204.46:https
tcp ESTAB 0 0 192.168.1.72:55116 182.201.240.37:https
tcp CLOSE-WAIT 12581 0 192.168.1.72:59756 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:52500 115.238.187.37:https
tcp CLOSE-WAIT 16792 0 192.168.1.72:59620 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:49960 114.80.30.37:https
tcp ESTAB 0 0 192.168.1.72:35468 111.174.1.37:https
tcp ESTAB 16800 0 192.168.1.72:60300 113.113.73.46:https
tcp SYN-SENT 0 1 192.168.1.72:39666 113.113.67.28:https
tcp ESTAB 0 0 192.168.1.72:42978 49.79.225.37:https
tcp ESTAB 0 1603 192.168.1.72:59958 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:45244 36.103.246.37:https
tcp CLOSE-WAIT 17104 0 192.168.1.72:46434 182.107.80.37:https
tcp ESTAB 0 0 192.168.1.72:50522 122.228.115.37:https
tcp ESTAB 0 0 192.168.1.72:53606 182.242.54.37:https
tcp CLOSE-WAIT 17087 0 192.168.1.72:48370 36.103.236.37:https
tcp ESTAB 0 3808 192.168.1.117:ssh 192.168.1.126:ripd
tcp ESTAB 0 0 192.168.1.72:44868 14.215.89.37:https
tcp LAST-ACK 0 25 192.168.1.72:33812 1.71.157.37:https
tcp ESTAB 0 0 192.168.1.72:44836 121.227.7.37:https
tcp ESTAB 0 2991 192.168.1.72:37210 115.238.242.37:https
tcp ESTAB 0 0 192.168.1.72:39374 171.107.85.37:https
tcp CLOSE-WAIT 12618 0 192.168.1.72:59732 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:42340 175.6.53.37:https
tcp ESTAB 0 183 192.168.1.72:60320 113.113.73.46:https
tcp ESTAB 0 0 192.168.1.72:52324 180.101.38.37:https
tcp ESTAB 0 0 192.168.1.72:51110 123.52.189.37:https
tcp ESTAB 0 0 192.168.1.72:60534 60.190.116.37:https
tcp CLOSE-WAIT 16761 0 192.168.1.72:46690 58.20.204.46:https
tcp ESTAB 8472 0 192.168.1.72:41496 27.148.188.37:https

boyodyang commented 2 years ago

pan_ua推荐按照 #172 构建,从老版本升级来的话ua可能不会更新,要手动修改

90多个连接都是baidupcs-go的么?10线程数有13个左右连接是正常的

确定都是baidupcs-go的我关了就都没了 我最大下载设定是5

10线程5个task, 70到90个连接.跑了好几天了. 没事 我抓了我自己手机百度云盘的包, 在前面又加了netdisk;P2SP;3.0.0.8; 一开我家里路由都会卡。

qjfoidnh commented 2 years ago

不像。这里很多连接的远端ip都不是百度服务器,而且pcs-go访问的域名就两三个,因此对应ip也就两三个,不会这么多,里面应该混了其他应用的tcp连接

boyodyang commented 2 years ago

会不会是p2sp协议产生的连接?

qjfoidnh commented 2 years ago

pcs-go不支持p2p,代码里就没这部分功能

boyodyang commented 2 years ago

绝对是百度云的, 杀掉进程立刻消失.

qjfoidnh commented 2 years ago

百度网盘还是PCS-Go?这个确认下 用pcs-go的pid grep一下,杀进程这种看可能不准确

boyodyang commented 2 years ago

pcs-go的, 47个

BaiduPCS- 6860 root 3u IPv4 3144499 0t0 TCP L1Pro:52624->182.140.225.37:https (ESTABLISHED) BaiduPCS- 6860 root 8u IPv4 3142929 0t0 TCP L1Pro:44148->111.177.8.37:https (CLOSE_WAIT) BaiduPCS- 6860 root 9u IPv4 3147419 0t0 TCP L1Pro:55006->106.38.179.37:https (ESTABLISHED) BaiduPCS- 6860 root 10u IPv4 3147488 0t0 TCP L1Pro:53896->171.107.85.37:https (ESTABLISHED) BaiduPCS- 6860 root 14u IPv4 3140220 0t0 TCP L1Pro:56202->58.217.202.46:https (CLOSE_WAIT) BaiduPCS- 6860 root 16u IPv4 3137750 0t0 TCP L1Pro:43396->119.167.143.20:https (ESTABLISHED) BaiduPCS- 6860 root 17u IPv4 3147495 0t0 TCP L1Pro:56312->115.238.242.37:https (ESTABLISHED) BaiduPCS- 6860 root 18u IPv4 3145095 0t0 TCP L1Pro:53748->119.100.50.37:https (ESTABLISHED) BaiduPCS- 6860 root 19u IPv4 3141545 0t0 TCP L1Pro:58322->180.163.198.37:https (ESTABLISHED) BaiduPCS- 6860 root 20u IPv4 3145977 0t0 TCP L1Pro:37434->150.138.188.37:https (ESTABLISHED) BaiduPCS- 6860 root 22u IPv4 3140802 0t0 TCP L1Pro:45632->113.113.73.46:https (ESTABLISHED) BaiduPCS- 6860 root 24u IPv4 3140387 0t0 TCP L1Pro:43440->119.167.143.20:https (ESTABLISHED) BaiduPCS- 6860 root 25u IPv4 3137953 0t0 TCP L1Pro:43442->119.167.143.20:https (ESTABLISHED) BaiduPCS- 6860 root 27u IPv4 3147424 0t0 TCP L1Pro:49672->114.232.92.37:https (ESTABLISHED) BaiduPCS- 6860 root 29u IPv4 3138026 0t0 TCP L1Pro:53526->119.100.50.37:https (CLOSE_WAIT) BaiduPCS- 6860 root 30u IPv4 3145973 0t0 TCP L1Pro:48868->180.97.198.37:https (ESTABLISHED) BaiduPCS- 6860 root 31u IPv4 3136375 0t0 TCP L1Pro:56042->58.20.204.46:https (CLOSE_WAIT) BaiduPCS- 6860 root 33u IPv4 3137585 0t0 TCP L1Pro:45528->113.113.73.46:https (ESTABLISHED) BaiduPCS- 6860 root 35u IPv4 3145780 0t0 TCP L1Pro:51588->125.74.40.37:https (ESTABLISHED) BaiduPCS- 6860 root 36u IPv4 3144445 0t0 TCP L1Pro:53192->175.6.53.37:https (ESTABLISHED) BaiduPCS- 6860 root 37u IPv4 3144450 0t0 TCP L1Pro:38386->36.104.159.37:https (CLOSE_WAIT) BaiduPCS- 6860 root 38u IPv4 3145242 0t0 TCP L1Pro:50816->113.113.67.28:https (ESTABLISHED) BaiduPCS- 6860 root 39u IPv4 3144453 0t0 TCP L1Pro:50228->125.74.42.37:https (ESTABLISHED) BaiduPCS- 6860 root 40u IPv4 3145174 0t0 TCP L1Pro:36412->171.107.86.37:https (ESTABLISHED) BaiduPCS- 6860 root 41u IPv4 3144501 0t0 TCP L1Pro:52256->49.79.225.37:https (ESTABLISHED) BaiduPCS- 6860 root 42u IPv4 3147509 0t0 TCP L1Pro:50814->113.113.67.28:https (ESTABLISHED) BaiduPCS- 6860 root 43u IPv4 3135371 0t0 TCP L1Pro:43266->119.167.143.20:https (ESTABLISHED) BaiduPCS- 6860 root 45u IPv4 3136550 0t0 TCP L1Pro:45494->113.113.73.46:https (CLOSE_WAIT) BaiduPCS- 6860 root 46u IPv4 3145107 0t0 TCP L1Pro:33684->113.137.52.37:https (ESTABLISHED) BaiduPCS- 6860 root 47u IPv4 3145116 0t0 TCP L1Pro:54120->1.81.3.37:https (ESTABLISHED) BaiduPCS- 6860 root 48u IPv4 3141481 0t0 TCP L1Pro:52218->37.189.52.123.broad.ly.ha.dynamic.163data.com.cn:https (ESTABLISHED) BaiduPCS- 6860 root 49u IPv4 3145094 0t0 TCP L1Pro:40384->219.153.113.37:https (ESTABLISHED) BaiduPCS- 6860 root 50u IPv4 3144475 0t0 TCP L1Pro:37910->124.225.184.37:https (ESTABLISHED) BaiduPCS- 6860 root 51u IPv4 3145099 0t0 TCP L1Pro:58350->118.180.40.37:https (ESTABLISHED) BaiduPCS- 6860 root 52u IPv4 3145108 0t0 TCP L1Pro:55306->106.225.194.37:https (ESTABLISHED) BaiduPCS- 6860 root 53u IPv4 3145783 0t0 TCP L1Pro:48448->121.227.7.37:https (ESTABLISHED) BaiduPCS- 6860 root 54u IPv4 3145784 0t0 TCP L1Pro:38178->175.6.243.37:https (ESTABLISHED) BaiduPCS- 6860 root 55u IPv4 3145801 0t0 TCP L1Pro:51956->180.97.66.37:https (ESTABLISHED) BaiduPCS- 6860 root 56u IPv4 3145812 0t0 TCP L1Pro:44314->122.228.115.37:https (ESTABLISHED) BaiduPCS- 6860 root 57u IPv4 3145178 0t0 TCP L1Pro:58010->110.185.186.37:https (ESTABLISHED) BaiduPCS- 6860 root 58u IPv4 3145079 0t0 TCP L1Pro:34110->1.71.157.37:https (ESTABLISHED) BaiduPCS- 6860 root 59u IPv4 3141583 0t0 TCP L1Pro:58022->182.242.217.37:https (ESTABLISHED) BaiduPCS- 6860 root 60u IPv4 3145110 0t0 TCP L1Pro:42252->14.215.89.37:https (ESTABLISHED) BaiduPCS- 6860 root 61u IPv4 3144551 0t0 TCP L1Pro:39984->42.81.84.37:https (ESTABLISHED) BaiduPCS- 6860 root 62u IPv4 3147489 0t0 TCP L1Pro:49684->114.232.92.37:https (ESTABLISHED) BaiduPCS- 6860 root 63u IPv4 3144565 0t0 TCP L1Pro:50820->113.113.67.28:https (ESTABLISHED) BaiduPCS- 6860 root 64u IPv4 3145982 0t0 TCP L1Pro:57742->58.217.200.37:https (SYN_SENT)