----- Original Message -----
From: "Aubin Galinotti" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, October 22, 2002 2:19 PM
Subject: Re: [tech]scanne ip de mm classe en ligne
> On Tue, 2002-10-22 at 14:11, Ludovic Janray wrote:
> > 192.198.0.1 pour adresse reseau
> >
> > Le resultat est sous quelle forme?
> > Merci
>
> alors chez moi j'ai :
>
> # ifconfig eth0 :
> inet addr:192.168.0.11 Bcast:192.168.0.255 Mask:255.255.255.0
Rigolo, idem chez moi
[EMAIL PROTECTED] /root]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:40:CA:15:01:FD
inet addr:192.168.0.11 Bcast:192.168.0.255 Mask:255.255.255.0
EtherTalk Phase 2 addr:65280/57
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:83140 errors:0 dropped:0 overruns:0 frame:0
TX packets:92340 errors:0 dropped:0 overruns:0 carrier:0
collisions:2563 txqueuelen:100
Interrupt:11 Base address:0x1080
> donc je fait :
>
> # ping -b 192.168.0.255
Pareil
sauf que j'ai:
[EMAIL PROTECTED] /root]# ping -b 192.168.0.255
WARNING: pinging broadcast address
Warning: no SO_TIMESTAMP support, falling back to SIOCGSTAMP
PING 192.168.0.255 (192.168.0.255) from 192.168.0.11 : 56(84) bytes of data.
64 bytes from 192.168.0.11: icmp_seq=0 ttl=255 time=96 usec
64 bytes from 192.168.0.11: icmp_seq=1 ttl=255 time=70 usec
64 bytes from 192.168.0.11: icmp_seq=2 ttl=255 time=69 usec
64 bytes from 192.168.0.11: icmp_seq=3 ttl=255 time=63 usec
64 bytes from 192.168.0.11: icmp_seq=4 ttl=255 time=64 usec
64 bytes from 192.168.0.11: icmp_seq=5 ttl=255 time=63 usec
64 bytes from 192.168.0.11: icmp_seq=6 ttl=255 time=113 usec
64 bytes from 192.168.0.11: icmp_seq=7 ttl=255 time=114 usec
64 bytes from 192.168.0.11: icmp_seq=8 ttl=255 time=65 usec
64 bytes from 192.168.0.11: icmp_seq=9 ttl=255 time=63 usec
au lieu de |
\ /
> WARNING: pinging broadcast address
> PING 192.168.0.255 (192.168.0.255) from 192.168.0.11 : 56(84) bytes of
> data.
> 64 bytes from 192.168.0.11: icmp_seq=1 ttl=64 time=0.097 ms
> 64 bytes from 192.168.0.2: icmp_seq=1 ttl=255 time=0.184 ms (DUP!)
> 64 bytes from 192.168.0.254: icmp_seq=1 ttl=64 time=0.325 ms (DUP!)
> 64 bytes from 192.168.0.11: icmp_seq=2 ttl=64 time=0.072 ms
> 64 bytes from 192.168.0.2: icmp_seq=2 ttl=255 time=0.143 ms (DUP!)
> 64 bytes from 192.168.0.254: icmp_seq=2 ttl=64 time=0.225 ms (DUP!)
>
Donc,
Warning: no SO_TIMESTAMP support, falling back to SIOCGSTAMP en cadeau...
?
Merci
Ludo.
Linux-Azur : http://www.linux-azur.org
Désinscriptions: http://www.linux-azur.org/liste.php3
**** Pas de message au format HTML, SVP ****
