From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 26 May 2003 23:56:16 +1100 From: Dmitry Lebkov To: community@altlinux.ru Subject: Re: [Comm] =?KOI8-R?Q?=ED=C1=D2=DB=D2=D5=D4=C9=DA=C1=C3=C9=D1?= Message-Id: <20030526235616.6c6baf10.dima@sakhalin.ru> In-Reply-To: <3ECDF447.6090006@rmts.donpac.ru> References: <3ECDD198.8070002@rmts.donpac.ru> <20030523202834.621a0e7b.dima@sakhalin.ru> <3ECDF447.6090006@rmts.donpac.ru> X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i586-alt-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit Sender: community-admin@altlinux.ru Errors-To: community-admin@altlinux.ru X-BeenThere: community@altlinux.ru X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: community@altlinux.ru List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Archived-At: List-Archive: List-Post: On Fri, 23 May 2003 14:13:27 +0400 Прокопьев Евгений wrote: [skip] > > На простой машине: > > ifconfig -a > > iptables -L -n > > ping -n 192.168.10.5 > > ping -n 192.168.101.3 > > [root@dbms root]# ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:01:80:09:48:CD > inet addr:192.168.10.6 Bcast:192.168.10.255 > Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 > Metric:1 > RX packets:10761 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:1660657 (1.5 Mb) TX bytes:0 (0.0 b) > Interrupt:10 Base address:0xc400 Я что-то сразу не обратил внимания - а почему TX packets = 0? Как-то же пакеты уходят, если есть RX и машина получает ответы на ping? > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > [root@dbms root]# iptables -L -n > bash: iptables: command not found > [root@dbms root]# ping -n 192.168.10.5 > PING 192.168.10.5 (192.168.10.5) 56(84) bytes of data. > 64 bytes from 192.168.10.5: icmp_seq=1 ttl=64 time=1.30 ms > 64 bytes from 192.168.10.5: icmp_seq=2 ttl=64 time=0.338 ms > 64 bytes from 192.168.10.5: icmp_seq=3 ttl=64 time=0.357 ms > 64 bytes from 192.168.10.5: icmp_seq=4 ttl=64 time=0.341 ms > 64 bytes from 192.168.10.5: icmp_seq=5 ttl=64 time=0.364 ms > > --- 192.168.10.5 ping statistics --- > 5 packets transmitted, 5 received, 0% packet loss, time 4002ms > rtt min/avg/max/mdev = 0.338/0.541/1.307/0.383 ms > [root@dbms root]# ping 192.168.101.3 > PING 192.168.101.3 (192.168.101.3) 56(84) bytes of data. > > --- 192.168.101.3 ping statistics --- > 5 packets transmitted, 0 received, 100% packet loss, time 3999ms > Тогда на сервере и на клиенте: 'tcpdump -i eth0 -n 'host 192.168.10.6', а на клиенте еще и: 'ping -n -c 5 192.168.101.3'. И результат tcpdump - сюда. -- WBR, Dmitry Lebkov