The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]



"wine+viber - No internet connection"
Версия для распечатки Пред. тема | След. тема
Форум Открытые системы на рабочей станции
Исходное сообщение [ Отслеживать ]

. "wine+viber - No internet connection" +/
Сообщение от anonymous (??), 17-Май-21, 18:26 
>> tcpdump показывает посылку и приём каких-то пакетиков
> Каких конкретно? - какие протоколы, номера портов.

Вот, вроде, удалось остановить все побочные сервисы, которые "фонили" в интернет, остался только вайбер:
Стартуем:

17:34:42.823530 IP 192.168.1.116.42414 > 192.168.1.100.53: 11358+ A? download.cdn.viber.com. (40)
17:34:42.823571 IP 192.168.1.116.42414 > 192.168.1.100.53: 9039+ AAAA? download.cdn.viber.com. (40)
17:34:43.250978 IP 192.168.1.100.53 > 192.168.1.116.42414: 9039 4/0/0 CNAME download.viber.com.edgesuite.net., CNAME a1883.dscd.akamai.net., AAAA 2a02:26f0:4800::215:5960, AAAA 2a02:26f0:4800::215:5959 (177)
17:34:43.258850 IP 192.168.1.100.53 > 192.168.1.116.42414: 11358 4/0/0 CNAME download.viber.com.edgesuite.net., CNAME a1883.dscd.akamai.net., A 2.19.205.43, A 2.19.205.33 (153)
17:34:43.260983 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [S], seq 2955871291, win 64240, options [mss 1460,sackOK,TS val 486536351 ecr 0,nop,wscale 7], length 0
17:34:43.293672 IP 2.19.205.43.443 > 192.168.1.116.50196: Flags [S.], seq 2414350598, ack 2955871292, win 28960, options [mss 1412,sackOK,TS val 497072310 ecr 486536351,nop,wscale 7], length 0
17:34:43.293728 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [.], ack 1, win 502, options [nop,nop,TS val 486536384 ecr 497072310], length 0
17:34:43.608743 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [P.], seq 1:234, ack 1, win 502, options [nop,nop,TS val 486536699 ecr 497072310], length 233
17:34:43.641225 IP 2.19.205.43.443 > 192.168.1.116.50196: Flags [.], ack 234, win 235, options [nop,nop,TS val 497072658 ecr 486536699], length 0
17:34:43.661142 IP 2.19.205.43.443 > 192.168.1.116.50196: Flags [.], seq 1:1401, ack 234, win 235, options [nop,nop,TS val 497072676 ecr 486536699], length 1400
17:34:43.661177 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [.], ack 1401, win 501, options [nop,nop,TS val 486536751 ecr 497072676], length 0
17:34:43.662342 IP 2.19.205.43.443 > 192.168.1.116.50196: Flags [.], seq 1401:2801, ack 234, win 235, options [nop,nop,TS val 497072676 ecr 486536699], length 1400
17:34:43.662356 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [.], ack 2801, win 501, options [nop,nop,TS val 486536753 ecr 497072676], length 0
17:34:43.662807 IP 2.19.205.43.443 > 192.168.1.116.50196: Flags [P.], seq 2801:3477, ack 234, win 235, options [nop,nop,TS val 497072676 ecr 486536699], length 676
17:34:43.662818 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [.], ack 3477, win 501, options [nop,nop,TS val 486536753 ecr 497072676], length 0
17:34:43.672565 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [P.], seq 234:360, ack 3477, win 501, options [nop,nop,TS val 486536763 ecr 497072676], length 126
17:34:43.705682 IP 2.19.205.43.443 > 192.168.1.116.50196: Flags [P.], seq 3477:3735, ack 360, win 235, options [nop,nop,TS val 497072722 ecr 486536763], length 258
17:34:43.705728 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [.], ack 3735, win 501, options [nop,nop,TS val 486536796 ecr 497072722], length 0
17:34:43.708731 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [F.], seq 360, ack 3735, win 501, options [nop,nop,TS val 486536799 ecr 497072722], length 0
17:34:43.741044 IP 2.19.205.43.443 > 192.168.1.116.50196: Flags [P.], seq 3735:3766, ack 361, win 235, options [nop,nop,TS val 497072758 ecr 486536799], length 31
17:34:43.741099 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [R], seq 2955871652, win 0, length 0
17:34:43.741150 IP 2.19.205.43.443 > 192.168.1.116.50196: Flags [F.], seq 3766, ack 361, win 235, options [nop,nop,TS val 497072758 ecr 486536799], length 0
17:34:43.741163 IP 192.168.1.116.50196 > 2.19.205.43.443: Flags [R], seq 2955871652, win 0, length 0
17:34:43.975659 IP 192.168.1.116.56832 > 192.168.1.100.53: 18032+ A? api.mixpanel.com. (34)
17:34:43.975703 IP 192.168.1.116.56832 > 192.168.1.100.53: 35215+ AAAA? api.mixpanel.com. (34)
17:34:43.980758 IP 192.168.1.100.53 > 192.168.1.116.56832: 18032 4/0/0 A 35.186.241.51, A 107.178.240.159, A 35.190.25.25, A 130.211.34.183 (98)
17:34:44.032642 IP 192.168.1.100.53 > 192.168.1.116.56832: 35215 0/1/0 (130)
17:34:44.040749 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [S], seq 2587766697, win 64240, options [mss 1460,sackOK,TS val 4190706108 ecr 0,nop,wscale 7], length 0
17:34:44.083645 IP 35.186.241.51.443 > 192.168.1.116.46570: Flags [S.], seq 2893654242, ack 2587766698, win 65535, options [mss 1412,sackOK,TS val 3761797772 ecr 4190706108,nop,wscale 8], length 0
17:34:44.083736 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [.], ack 1, win 502, options [nop,nop,TS val 4190706151 ecr 3761797772], length 0
17:34:44.313834 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [P.], seq 1:228, ack 1, win 502, options [nop,nop,TS val 4190706381 ecr 3761797772], length 227
17:34:44.356535 IP 35.186.241.51.443 > 192.168.1.116.46570: Flags [.], ack 228, win 261, options [nop,nop,TS val 3761798045 ecr 4190706381], length 0
17:34:44.358816 IP 35.186.241.51.443 > 192.168.1.116.46570: Flags [.], seq 1:1401, ack 228, win 261, options [nop,nop,TS val 3761798046 ecr 4190706381], length 1400
17:34:44.358842 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [.], ack 1401, win 501, options [nop,nop,TS val 4190706426 ecr 3761798046], length 0
17:34:44.360009 IP 35.186.241.51.443 > 192.168.1.116.46570: Flags [.], seq 1401:2801, ack 228, win 261, options [nop,nop,TS val 3761798046 ecr 4190706381], length 1400
17:34:44.360027 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [.], ack 2801, win 491, options [nop,nop,TS val 4190706427 ecr 3761798046], length 0
17:34:44.360872 IP 35.186.241.51.443 > 192.168.1.116.46570: Flags [P.], seq 2801:4105, ack 228, win 261, options [nop,nop,TS val 3761798046 ecr 4190706381], length 1304
17:34:44.360884 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [.], ack 4105, win 481, options [nop,nop,TS val 4190706428 ecr 3761798046], length 0
17:34:44.387773 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [P.], seq 228:313, ack 4105, win 501, options [nop,nop,TS val 4190706455 ecr 3761798046], length 85
17:34:44.430788 IP 35.186.241.51.443 > 192.168.1.116.46570: Flags [P.], seq 4105:4389, ack 313, win 261, options [nop,nop,TS val 3761798119 ecr 4190706455], length 284
17:34:44.430839 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [.], ack 4389, win 501, options [nop,nop,TS val 4190706498 ecr 3761798119], length 0
17:34:44.431970 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [F.], seq 313, ack 4389, win 501, options [nop,nop,TS val 4190706499 ecr 3761798119], length 0
17:34:44.474439 IP 35.186.241.51.443 > 192.168.1.116.46570: Flags [F.], seq 4389, ack 314, win 261, options [nop,nop,TS val 3761798163 ecr 4190706499], length 0
17:34:44.474464 IP 192.168.1.116.46570 > 35.186.241.51.443: Flags [.], ack 4390, win 501, options [nop,nop,TS val 4190706542 ecr 3761798163], length 0
17:34:44.579932 IP 192.168.1.116.38394 > 192.168.1.100.53: 54498+ A? secure.viber.com. (34)
17:34:44.579980 IP 192.168.1.116.38394 > 192.168.1.100.53: 63473+ AAAA? secure.viber.com. (34)
17:34:44.851922 IP 192.168.1.100.53 > 192.168.1.116.38394: 54498 3/0/0 CNAME refugee-use-1985070560.us-east-1.elb.amazonaws.com., A 52.70.29.201, A 34.231.106.102 (130)
17:34:44.871800 IP 192.168.1.100.53 > 192.168.1.116.38394: 63473 1/1/0 CNAME refugee-use-1985070560.us-east-1.elb.amazonaws.com. (183)
17:34:44.874049 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [S], seq 90889429, win 64240, options [mss 1460,sackOK,TS val 2331803902 ecr 0,nop,wscale 7], length 0
17:34:45.025732 IP 52.70.29.201.443 > 192.168.1.116.46400: Flags [S.], seq 567797856, ack 90889430, win 26847, options [mss 1412,sackOK,TS val 1715780303 ecr 2331803902,nop,wscale 8], length 0
17:34:45.025795 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [.], ack 1, win 502, options [nop,nop,TS val 2331804054 ecr 1715780303], length 0
17:34:45.288527 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [P.], seq 1:228, ack 1, win 502, options [nop,nop,TS val 2331804317 ecr 1715780303], length 227
17:34:45.440080 IP 52.70.29.201.443 > 192.168.1.116.46400: Flags [.], ack 228, win 110, options [nop,nop,TS val 1715780407 ecr 2331804317], length 0
17:34:45.443073 IP 52.70.29.201.443 > 192.168.1.116.46400: Flags [.], seq 1:1401, ack 228, win 110, options [nop,nop,TS val 1715780407 ecr 2331804317], length 1400
17:34:45.443096 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [.], ack 1401, win 501, options [nop,nop,TS val 2331804471 ecr 1715780407], length 0
17:34:45.444295 IP 52.70.29.201.443 > 192.168.1.116.46400: Flags [.], seq 1401:2801, ack 228, win 110, options [nop,nop,TS val 1715780407 ecr 2331804317], length 1400
17:34:45.444307 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [.], ack 2801, win 501, options [nop,nop,TS val 2331804473 ecr 1715780407], length 0
17:34:45.445216 IP 52.70.29.201.443 > 192.168.1.116.46400: Flags [.], seq 2801:4201, ack 228, win 110, options [nop,nop,TS val 1715780407 ecr 2331804317], length 1400
17:34:45.445227 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [.], ack 4201, win 501, options [nop,nop,TS val 2331804473 ecr 1715780407], length 0
17:34:45.445933 IP 52.70.29.201.443 > 192.168.1.116.46400: Flags [P.], seq 4201:5282, ack 228, win 110, options [nop,nop,TS val 1715780407 ecr 2331804317], length 1081
17:34:45.445946 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [.], ack 5282, win 501, options [nop,nop,TS val 2331804474 ecr 1715780407], length 0
17:34:45.453089 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [P.], seq 228:354, ack 5282, win 501, options [nop,nop,TS val 2331804481 ecr 1715780407], length 126
17:34:45.604940 IP 52.70.29.201.443 > 192.168.1.116.46400: Flags [P.], seq 5282:5540, ack 354, win 110, options [nop,nop,TS val 1715780448 ecr 2331804481], length 258
17:34:45.604982 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [.], ack 5540, win 501, options [nop,nop,TS val 2331804633 ecr 1715780448], length 0
17:34:45.605969 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [F.], seq 354, ack 5540, win 501, options [nop,nop,TS val 2331804634 ecr 1715780448], length 0
17:34:45.757843 IP 52.70.29.201.443 > 192.168.1.116.46400: Flags [F.], seq 5540, ack 355, win 110, options [nop,nop,TS val 1715780486 ecr 2331804634], length 0
17:34:45.757886 IP 192.168.1.116.46400 > 52.70.29.201.443: Flags [.], ack 5541, win 501, options [nop,nop,TS val 2331804786 ecr 1715780486], length 0
17:34:48.250779 ARP, Request who-has 192.168.1.116 tell 192.168.1.100, length 28
17:34:48.250806 ARP, Reply 192.168.1.116 is-at c4:17:fe:6f:bf:c4, length 28

Здесь появилось окошко "No connection

An Internet connection is required to activate your Viber
account. Check your connection and try again."

И кнопка - "Try again"
см: https://cloud.mail.ru/public/1Low/EowbT2twg

А это я нажал эту кнопку "Try again":
17:35:19.267691 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [S], seq 1145607605, win 64240, options [mss 1460,sackOK,TS val 2331838296 ecr 0,nop,wscale 7], length 0
17:35:19.410288 IP 52.70.29.201.443 > 192.168.1.116.46402: Flags [S.], seq 1238208225, ack 1145607606, win 26847, options [mss 1412,sackOK,TS val 1715788902 ecr 2331838296,nop,wscale 8], length 0
17:35:19.410345 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [.], ack 1, win 502, options [nop,nop,TS val 2331838439 ecr 1715788902], length 0
17:35:19.695335 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [P.], seq 1:228, ack 1, win 502, options [nop,nop,TS val 2331838724 ecr 1715788902], length 227
17:35:19.838075 IP 52.70.29.201.443 > 192.168.1.116.46402: Flags [.], ack 228, win 110, options [nop,nop,TS val 1715789009 ecr 2331838724], length 0
17:35:19.840159 IP 52.70.29.201.443 > 192.168.1.116.46402: Flags [.], seq 1:1401, ack 228, win 110, options [nop,nop,TS val 1715789009 ecr 2331838724], length 1400
17:35:19.840181 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [.], ack 1401, win 501, options [nop,nop,TS val 2331838868 ecr 1715789009], length 0
17:35:19.841448 IP 52.70.29.201.443 > 192.168.1.116.46402: Flags [.], seq 1401:2801, ack 228, win 110, options [nop,nop,TS val 1715789009 ecr 2331838724], length 1400
17:35:19.841461 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [.], ack 2801, win 501, options [nop,nop,TS val 2331838870 ecr 1715789009], length 0
17:35:19.842376 IP 52.70.29.201.443 > 192.168.1.116.46402: Flags [.], seq 2801:4201, ack 228, win 110, options [nop,nop,TS val 1715789009 ecr 2331838724], length 1400
17:35:19.842389 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [.], ack 4201, win 501, options [nop,nop,TS val 2331838871 ecr 1715789009], length 0
17:35:19.843089 IP 52.70.29.201.443 > 192.168.1.116.46402: Flags [P.], seq 4201:5282, ack 228, win 110, options [nop,nop,TS val 1715789009 ecr 2331838724], length 1081
17:35:19.843101 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [.], ack 5282, win 501, options [nop,nop,TS val 2331838871 ecr 1715789009], length 0
17:35:19.849518 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [P.], seq 228:354, ack 5282, win 501, options [nop,nop,TS val 2331838878 ecr 1715789009], length 126
17:35:19.992880 IP 52.70.29.201.443 > 192.168.1.116.46402: Flags [P.], seq 5282:5540, ack 354, win 110, options [nop,nop,TS val 1715789047 ecr 2331838878], length 258
17:35:19.992923 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [.], ack 5540, win 501, options [nop,nop,TS val 2331839021 ecr 1715789047], length 0
17:35:19.993812 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [F.], seq 354, ack 5540, win 501, options [nop,nop,TS val 2331839022 ecr 1715789047], length 0
17:35:20.136138 IP 52.70.29.201.443 > 192.168.1.116.46402: Flags [F.], seq 5540, ack 355, win 110, options [nop,nop,TS val 1715789083 ecr 2331839022], length 0
17:35:20.136180 IP 192.168.1.116.46402 > 52.70.29.201.443: Flags [.], ack 5541, win 501, options [nop,nop,TS val 2331839164 ecr 1715789083], length 0

И снова выскочила табличка "No connection". И дальше - по кругу.

> Если это именно Вайбер и если был двусторонний обмен по tcp, то
> проблема выглядит как это внутри Вайбера, но не в Вайне или
> ещё где-то.

Такое ощущение, что пакеты теряются между вайном и вайбером.

> Просто если оно и передало и пришёл ответ по TCP, то сеть
> работает 100%.

Ответить | Правка | Наверх | Cообщить модератору

Оглавление
wine+viber - No internet connection, anonymous, 28-Апр-21, 22:08  [смотреть все]
Форумы | Темы | Пред. тема | След. тема



Партнёры:
PostgresPro
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру