lonely wolf wrote: Am sa-i raspund si d-lui Birzan cu un drum, ca si el m-a intrebat de tcpdump.
> un tcpdump pe masina 72.100 ce zice ? > in special pachetele generate ar fi interesante. Pe masina 72.100 nu se poate face tcpdump in schimb se poate snifa traficul inspre/de la 72.100. Acolo se vad toate pachetele dinspre 1.30 atat UDP cat si ICMP dar nici un pachet spre 1.30 (cum era si normal). Am facut asta mai devreme, din pacate nu mai am dump-urile. Credeti-ma pe cuvant. Un tcpdump pe 1.30 arata asa (am pastrat fragmente relevante): 17:45:15.546014 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 5, id 24082, len 38) 17:45:15.596916 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 5, id 24083, len 38) 17:45:15.650843 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 5, id 24084, len 38) 17:45:15.706386 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 6, id 24085, len 38) 17:45:15.764137 172.16.72.100 > 192.168.1.30: icmp: time exceeded in-transit [tos 0x80] (ttl 250, id 21778, len 56) 17:45:15.764625 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 6, id 24086, len 38) 17:45:15.814686 172.16.72.100 > 192.168.1.30: icmp: time exceeded in-transit [tos 0x80] (ttl 250, id 21779, len 56) 17:45:15.814761 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 6, id 24087, len 38) 17:45:15.880483 172.16.72.100 > 192.168.1.30: icmp: time exceeded in-transit [tos 0x80] (ttl 250, id 21783, len 56) 17:45:17.842414 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 12, id 24105, len 38) 17:45:17.930584 172.16.72.100 > 192.168.1.30: icmp: time exceeded in-transit [tos 0x80] (ttl 244, id 40455, len 56) 17:45:17.930655 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 13, id 24106, len 38) 17:45:22.930054 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 13, id 24107, len 38) 17:45:27.930057 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 13, id 24108, len 38) 17:45:32.930070 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 14, id 24109, len 38) 17:45:37.930056 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 14, id 24110, len 38) 17:45:42.930057 192.168.1.30 > 172.16.72.100: icmp: echo request (ttl 14, id 24111, len 38) > dar ma indoiesc ca e situatia ta. de altfel cred ca desi apare de 6 ori, > de fapt e un singur router care se screme si nu stie cum sa te faca sa > ii intelegi dilemele existentiale prin care trece. E un Cisco la care nu am acces, ca de altfel la toate ruterele de pe traseu. Doar terminatiile imi apartin. Oricum "dilemele existentiale" sunt cea mai buna explicatie de pana acum :) >># ping 172.16.72.100 >>PING 172.16.72.100 (172.16.72.100) from 192.168.1.30 : 56(84) bytes of data. >> >>--- 172.16.72.100 ping statistics --- >>7 packets transmitted, 0 received, 100% loss, time 6015ms >> >> > > $IPT -A INPUT -p icmp --icmp-type echo-reply -i $EXTERNAL_INTERFACE1 -j DROP > $IPT -A INPUT -p icmp --icmp-type time-exceeded -i $EXTERNAL_INTERFACE1 > -j ACCEPT > si o sa ai traceroute fara a avea ping reply. Corect, am uitat sa precizez ca nu exista nici un fel de filtrare pe 72.10. Din reteaua 172.16.72.0, 72.100 raspunde la ping. Grig --- Detalii despre listele noastre de mail: http://www.lug.ro/
