Re: duplicate packet

2008-09-22 Thread Valdis . Kletnieks
On Mon, 22 Sep 2008 19:54:17 PDT, John Jensen said: > She'd have to actually specify -b to ping a broadcast address, Only true if you're pinging the broadcast address of a network that you have an interface on, or the system has other knowledge of the netmask/etc. If you're pinging a remote addre

Re: duplicate packet

2008-09-22 Thread John Jensen
At least I think that's how it works. :) On Mon, Sep 22, 2008 at 7:54 PM, John Jensen <[EMAIL PROTECTED]> wrote: > She'd have to actually specify -b to ping a broadcast address, and if > she did, she would only get replies back from the hosts on that > subnet, not duplicate replies from the same I

Re: duplicate packet

2008-09-22 Thread John Jensen
She'd have to actually specify -b to ping a broadcast address, and if she did, she would only get replies back from the hosts on that subnet, not duplicate replies from the same IP. On Wed, Sep 10, 2008 at 5:11 AM, Sebastian Abt <[EMAIL PROTECTED]> wrote: > * chloe K wrote: >> When I ping the ip,

Re: duplicate packet

2008-09-10 Thread Laurence F. Sheldon, Jr.
Sebastian Abt wrote: * chloe K wrote: When I ping the ip, I get the duplicate 64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.344 ms 64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.401 ms (DUP!) What's your netmask? Is 192.168.0.95 your net's broadcast

RE: duplicate packet

2008-09-10 Thread Tim Sanderson
From: Jon Lewis [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 10, 2008 8:11 AM To: chloe K Cc: nanog@nanog.org Subject: Re: duplicate packet On Wed, 10 Sep 2008, chloe K wrote: > When I ping the ip, I get the duplicate > > I check the ip is just one. Why it happens? >

Re: duplicate packet

2008-09-10 Thread Sebastian Abt
* chloe K wrote: > When I ping the ip, I get the duplicate > > 64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.344 ms > 64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.401 ms (DUP!) What's your netmask? Is 192.168.0.95 your net's broadcast address? sebasti

Re: duplicate packet

2008-09-10 Thread Jon Lewis
On Wed, 10 Sep 2008, chloe K wrote: When I ping the ip, I get the duplicate I check the ip is just one. Why it happens? 64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.344 ms 64 bytes from 192.168.0.95: icmp_seq=1 ttl=63 time=0.401 ms (DUP!) Not enough information has been given. Just

RE: duplicate packet

2008-09-10 Thread Eric Van Tol
> -Original Message- > From: chloe K [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 10, 2008 6:46 AM > To: nanog@nanog.org > Subject: duplicate packet > > Hi all > > When I ping the ip, I get the duplicate > > I check the ip is just one. Why it happens? > > Thank you > > 64 bytes fr

RE: duplicate packet

2008-09-10 Thread Darden, Patrick S.
Check your ARP tables, local and on intervening switches/routers. Make sure there are no duplicate entries for that IP. If you note the response time, the second packet is always higher which might be indicative. I would also check for a botched MITM a la C&A. Even if there is no obvious AR

Re: duplicate packet

2008-09-10 Thread Florian Weimer
* chloe K.: > When I ping the ip, I get the duplicate > > I check the ip is just one. Why it happens? Are the source and target on the same subnet? Have you checked the source MAC address of the response? -- Florian Weimer<[EMAIL PROTECTED]> BFK edv-consulting GmbH http: