2011/12/19 Catalin Bucur <[email protected]>: > On 19.12.2011 00:21, Calin wrote: >> $ sudo tcpdump -i <linx-local-iface> -w capture-file.cap -s <vezi-mai-jos> >> 'icmp' >> >> nota: nu mai tin minte care e local iface in linux - in osx e lo0 ... >> >> iar in alt terminal window: >> >> $ ping -s 64 (<vezi-mai-sus>) 127.0.0.1 - si incearca apoi diverse valori >> pentru -s si chiar -D (don't fragment) >> >> apoi deshide fisierul capture-file.cap in wireshark, si vezi ce se petrece > > > Reply-ul vine imediat de la interfata, se pare ca e intarziata > trimiterea de pachete: > > 16:37:38.406200 IP 127.0.0.1 > 127.0.0.1: ICMP echo request, id 50215, > seq 0, length 64 > 16:37:38.406232 IP 127.0.0.1 > 127.0.0.1: ICMP echo reply, id 50215, seq > 0, length 64 > 16:37:39.454648 IP 127.0.0.1 > 127.0.0.1: ICMP echo request, id 50215, > seq 0, length 64 > 16:37:39.454668 IP 127.0.0.1 > 127.0.0.1: ICMP echo reply, id 50215, seq > 0, length 64 > 16:37:40.507563 IP 127.0.0.1 > 127.0.0.1: ICMP echo request, id 50215, > seq 0, length 64 > 16:37:40.507582 IP 127.0.0.1 > 127.0.0.1: ICMP echo reply, id 50215, seq > 0, length 64 > > Fping merge ok fara delay-uri, asa ca am dedus ca e o problema de > utilitar (ping). Am downloadat si compilat: > http://www.skbuff.net/iputils/iputils-s20071127.tar.bz2 > si am facut teste, dar am aceleasi rezultate. > > Modificari de packetsize si fragmentare nu schimba situatia.
1 fping foloseste pachete ARP who-is si reply ca arping? 2 cum stai cu firewall-urile? t. _______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
