ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: "Anton V. Boyarshinov" <boyarsh@ru.echo.fr>
To: community@altlinux.ru
Subject: Re: [Comm] Re: Непонятные проблемы с доступом к некоторомы сайтам.
Date: Tue, 11 Mar 2003 21:15:26 +0300
Message-ID: <20030311181012.8C0242B51B@mail.ru.echo.fr> (raw)
In-Reply-To: <20030304114010.1088d682.vyt@vzljot.ru>

On Tue, 4 Mar 2003 11:40:10 +0300 Vitaly Ostanin
 wrote:

> > Возможно, даже вероятно. Но ума не приложу в чём, если с других
> > машин его сети всё прекрасно открывается. Никаких transparent
> > proxy и прочего они (по их утверждениям) не используют.
> 
> Ну ясно, что дело в адресе - кто-то его не любит - либо
> провайдер, либо google, либо Вы :) У себя с iptables Вы можете
> поэкспериментировать, остальное - дело их support'ов, посидеть с
> tcpdump'ом на Ваш адрес.

Провайдера сидеть с tcpdump-ом пока не уговорил, support google молчит.
А вот сам с tcpdump посидел и вот что высидел:

[avb@boyarsh avb]$ telnet 216.239.37.100 80
Trying 216.239.37.100...
Connected to 216.239.37.100.
Escape character is '^]'.
get / HTTP/1.1
Host: www.google.com.ru


Connection closed by foreign host.
[avb@boyarsh avb]$ 


[root@boyarsh root]# tcpdump -i ppp0 \( src 216.239.37.100 and dst 62.117.104.97 \) or \(dst 216.239.37.100 and src 62.117.104.97 \)
tcpdump: listening on ppp0
21:07:11.474526 62.117.104.97.32860 > 216.239.37.100.http: S 1382252959:1382252959(0) win 3840 <mss 960,nop,nop,sackOK,nop,wscale 0> (DF) [tos 0x10] 
21:07:11.621070 216.239.37.100.http > 62.117.104.97.32860: S 765269482:765269482(0) ack 1382252960 win 8190 <mss 960>
21:07:11.621182 62.117.104.97.32860 > 216.239.37.100.http: . ack 1 win 3840 (DF) [tos 0x10] 
21:07:17.420471 62.117.104.97.32860 > 216.239.37.100.http: P 1:17(16) ack 1 win 3840 (DF) [tos 0x10] 
21:07:17.788443 216.239.37.100.http > 62.117.104.97.32860: . ack 17 win 8190
21:07:17.788519 62.117.104.97.32860 > 216.239.37.100.http: P 17:42(25) ack 1 win 3840 (DF) [tos 0x10] 
21:07:18.133653 216.239.37.100.http > 62.117.104.97.32860: . ack 42 win 8190
21:07:20.042863 62.117.104.97.32860 > 216.239.37.100.http: P 42:44(2) ack 1 win 3840 (DF) [tos 0x10] 
21:07:20.188013 216.239.37.100.http > 62.117.104.97.32860: . ack 42 win 30660 (DF) [tos 0x10] 
21:07:20.193633 216.239.37.100.http > 62.117.104.97.32860: . ack 44 win 32120 (DF) [tos 0x10] 
21:07:20.200944 216.239.37.100.http > 62.117.104.97.32860: P 961:1461(500) ack 44 win 32120
21:07:20.201007 62.117.104.97.32860 > 216.239.37.100.http: . ack 1 win 3840 (DF) [tos 0x10] 
21:07:20.208200 216.239.37.100.http > 62.117.104.97.32860: . 1:957(956) ack 44 win 32120 (frag 17996:976@0+)
21:07:20.209906 216.239.37.100.http > 62.117.104.97.32860: P 1461:1921(460) ack 44 win 32120
21:07:20.209975 62.117.104.97.32860 > 216.239.37.100.http: . ack 1 win 3840 (DF) [tos 0x10] 
21:07:21.215160 216.239.37.100.http > 62.117.104.97.32860: P 1:957(956) ack 44 win 32120 (frag 34800:976@0+)
21:07:23.225527 216.239.37.100.http > 62.117.104.97.32860: P 1:957(956) ack 44 win 32120 (frag 7426:976@0+)
21:07:27.236130 216.239.37.100.http > 62.117.104.97.32860: P 1:957(956) ack 44 win 32120 (frag 20156:976@0+)
21:07:35.248203 216.239.37.100.http > 62.117.104.97.32860: P 1:957(956) ack 44 win 32120 (frag 18068:976@0+)
21:07:50.199027 62.117.104.97 > 216.239.37.100: icmp: ip reassembly time exceeded [tos 0xc0] 
21:07:51.208945 62.117.104.97 > 216.239.37.100: icmp: ip reassembly time exceeded [tos 0xc0] 
21:07:51.261537 216.239.37.100.http > 62.117.104.97.32860: P 1:957(956) ack 44 win 32120 (frag 39329:976@0+)
21:07:53.218929 62.117.104.97 > 216.239.37.100: icmp: ip reassembly time exceeded [tos 0xc0] 
21:07:57.228932 62.117.104.97 > 216.239.37.100: icmp: ip reassembly time exceeded [tos 0xc0] 
21:08:21.258927 62.117.104.97 > 216.239.37.100: icmp: ip reassembly time exceeded [tos 0xc0] 

26 packets received by filter
0 packets dropped by kernel
[root@boyarsh root]# 
	
К сожалению, мои знания протокола TCP/IP достаточно поверхностны. Однако
очевидно, что повторения "216.239.37.100.http > 62.117.104.97.32860: P
1:957(956) ack 44" а также "ip reassembly time exceeded" не к добру.
Буду очень благодарен если кто-нибудь объяснит мне что это значит
или что по этому поводу почитать.

Антон
-- 
mailto:boyarsh@mail.ru
mailto:boyarsh@ru.echo.fr
 21:04:01  up 6 days,  4:34,  2 users,  load average: 0.00, 0.00, 0.00


  parent reply	other threads:[~2003-03-11 18:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04  7:47 [Comm] " Anton V. Boyarshinov
2003-03-04  7:57 ` Anton V. Boyarshinov
2003-03-04  8:14 ` [Comm] " Vitaly Ostanin
2003-03-04  8:22   ` Anton V. Boyarshinov
2003-03-04  8:40     ` Vitaly Ostanin
2003-03-04  8:59       ` Anton V. Boyarshinov
2003-03-11 18:15       ` Anton V. Boyarshinov [this message]
2003-03-11 18:22         ` Anton V. Boyarshinov
2003-03-12  9:35       ` Anton V. Boyarshinov
2003-03-12 10:51         ` [Comm] " Sergey S. Skulachenko
2003-03-04  8:44     ` [Comm] " Padukov Vladimir
2003-03-04  9:01       ` Anton V. Boyarshinov
2003-03-05 13:08 ` [Comm] " Dmitry V. Levin
2003-03-06  8:09   ` Anton V. Boyarshinov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030311181012.8C0242B51B@mail.ru.echo.fr \
    --to=boyarsh@ru.echo.fr \
    --cc=community@altlinux.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Community general discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
		mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
	public-inbox-index community

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git