[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#241673: marked as done (arping: Arping can't ping ip-address)

Your message dated Sun, 23 Jul 2006 02:30:57 +0200
with message-id <87d5bxupq6.fsf@debian.org>
and subject line Fixed in arping 2.05-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: arping
Version: 2.01-3
Severity: normal

I have problems to ping a ip with arping, pinging the hostname is
possible. For example:

[sebastianw@lain:~]$ sudo arping divine
60 bytes from 00:10:dc:90:ec:49 ( index=0 time=93.937 usec

--- statistics ---
1 packets transmitted, 1 packets received,   0% unanswered
[sebastianw@lain:~]$ sudo arping

--- statistics ---
10 packets transmitted, 0 packets received, 100% unanswered
[Exit 1] 

As you see, I first ping the hostname associated with the ip It gets answered at once. After that I ping the ip manually but I don't get back any packets.

Sebastian Wiesinger

-- System Information:
Debian Release: 3.0
Architecture: i386
Kernel: Linux lain 2.6.4 #2 Mon Mar 15 18:47:14 CET 2004 i686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro

Versions of packages arping depends on:
ii  libc6                       2.3.2.ds1-10 GNU C Library: Shared libraries an
ii  libnet1               Library for the construction and h
ii  libpcap0.7                  0.7.2-5      System interface for user-level pa

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: arping
Source-Version: 2.05-1

As the upstream author says, this is fixed in the current version.
(I can reproduce the problem with 2.01-3, while 2.05-1 works fine.)

Thanks for your patience,


--- End Message ---

Reply to: