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

Bug#546214: marked as done (laptop-net: arp-discovery does not work on my laptop)

Your message dated Sun, 27 Feb 2011 10:40:44 +0000
with message-id <[🔎] E1Pte3Q-0004ov-J6@franck.debian.org>
and subject line Bug#581442: Removed package(s) from unstable
has caused the Debian Bug report #546214,
regarding laptop-net: arp-discovery does not work on my laptop
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
546214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546214
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: laptop-net
Version: 2.26-8.1
Severity: important

Hello,

I was using laptop-net on my amd64 laptop for a long time. It starts not
working anymore several months ago.

I finally manage to look at it and found that arp-discovery returns
@NO-RESPONSES@ what ever happens.

--8<---------------cut here---------------start------------->8---
home    192.168.1.1 192.168.1.2
work    172.30.75.131
friend  10.0.0.254
--8<---------------cut here---------------end--------------->8---

Looking at a tcpdump show that ARP request are sent and replied:

--8<---------------cut here---------------start------------->8---
root@laptop: ~# tcpdump -n ether host <LAPTOP MAC ADDRESS> and ! port ssh
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
18:40:53.673781 ARP, Request who-has 192.168.1.1 tell 0.0.0.0, length 46
18:40:53.673789 ARP, Request who-has 192.168.1.2 tell 0.0.0.0, length 46
18:40:53.673794 ARP, Reply 192.168.1.2 is-at <STATION MAC ADDRESS>, length 28
18:40:53.673798 ARP, Request who-has 172.30.75.131 tell 0.0.0.0, length 46
18:40:53.673800 ARP, Request who-has 10.0.0.254 tell 0.0.0.0, length 46
18:40:54.795309 ARP, Request who-has 192.168.1.1 tell 0.0.0.0, length 46
18:40:54.795317 ARP, Request who-has 192.168.1.2 tell 0.0.0.0, length 46
18:40:54.795320 ARP, Reply 192.168.1.2 is-at <STATION MAC ADDRESS>, length 28
18:40:54.795323 ARP, Request who-has 172.30.75.131 tell 0.0.0.0, length 46
18:40:54.795325 ARP, Request who-has 10.0.0.254 tell 0.0.0.0, length 46
18:40:55.909573 ARP, Request who-has 192.168.1.1 tell 0.0.0.0, length 46
18:40:55.909580 ARP, Request who-has 192.168.1.2 tell 0.0.0.0, length 46
18:40:55.909584 ARP, Reply 192.168.1.2 is-at <STATION MAC ADDRESS>, length 28
18:40:55.909587 ARP, Request who-has 172.30.75.131 tell 0.0.0.0, length 46
18:40:55.909589 ARP, Request who-has 10.0.0.254 tell 0.0.0.0, length 46
18:40:57.031050 ARP, Request who-has 192.168.1.1 tell 0.0.0.0, length 46
18:40:57.031057 ARP, Request who-has 192.168.1.2 tell 0.0.0.0, length 46
18:40:57.031061 ARP, Reply 192.168.1.2 is-at <STATION MAC ADDRESS>, length 28
18:40:57.031064 ARP, Request who-has 172.30.75.131 tell 0.0.0.0, length 46
18:40:57.031066 ARP, Request who-has 10.0.0.254 tell 0.0.0.0, length 46
18:40:58.152522 ARP, Request who-has 192.168.1.1 tell 0.0.0.0, length 46
18:40:58.152529 ARP, Request who-has 192.168.1.2 tell 0.0.0.0, length 46
18:40:58.152533 ARP, Reply 192.168.1.2 is-at <STATION MAC ADDRESS>, length 28
18:40:58.152535 ARP, Request who-has 172.30.75.131 tell 0.0.0.0, length 46
18:40:58.152537 ARP, Request who-has 10.0.0.254 tell 0.0.0.0, length 46
18:40:59.273993 ARP, Request who-has 192.168.1.1 tell 0.0.0.0, length 46
18:40:59.273999 ARP, Request who-has 192.168.1.2 tell 0.0.0.0, length 46
18:40:59.274003 ARP, Reply 192.168.1.2 is-at <STATION MAC ADDRESS>, length 28
18:40:59.274006 ARP, Request who-has 172.30.75.131 tell 0.0.0.0, length 46
18:40:59.274008 ARP, Request who-has 10.0.0.254 tell 0.0.0.0, length 46
18:41:00.395455 ARP, Request who-has 192.168.1.1 tell 0.0.0.0, length 46
18:41:00.395462 ARP, Request who-has 192.168.1.2 tell 0.0.0.0, length 46
18:41:00.395466 ARP, Reply 192.168.1.2 is-at <STATION MAC ADDRESS>, length 28
18:41:00.395469 ARP, Request who-has 172.30.75.131 tell 0.0.0.0, length 46
18:41:00.395471 ARP, Request who-has 10.0.0.254 tell 0.0.0.0, length 46
18:41:01.514847 ARP, Request who-has 192.168.1.1 tell 0.0.0.0, length 46
18:41:01.514853 ARP, Request who-has 192.168.1.2 tell 0.0.0.0, length 46
18:41:01.514856 ARP, Reply 192.168.1.2 is-at <STATION MAC ADDRESS>, length 28
18:41:01.514859 ARP, Request who-has 172.30.75.131 tell 0.0.0.0, length 46
18:41:01.514861 ARP, Request who-has 10.0.0.254 tell 0.0.0.0, length 46
--8<---------------cut here---------------end--------------->8---

But arp-discovery alwas returns @NO-RESPONSES.

I tested it on my workstation and it's the same.

Regards.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (90, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31+hati.2 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1

Attachment: pgpZaRylWbRxz.pgp
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Version: 2.26-9+rm

Dear submitter,

as the package laptop-net has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/581442

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)

--- End Message ---
Reply to: