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

Bug#494363: marked as done (thecus nic driver multicast issue)

Your message dated Mon, 3 Aug 2009 19:45:01 +0200
with message-id <20090803174501.GI22735@inutil.org>
and subject line Re: Bug#407217: avahi not working with r8169 driver
has caused the Debian Bug report #407217,
regarding thecus nic driver multicast issue
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.)


-- 
407217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407217
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.25-2-iop32x
Version: 2.6.25-7
Severity: normal

Apparently the nic driver for my thecus n2100 has a problem with
multicast packets. It ignores them unless put in promisc or allmulti
mode.

This means that IPV6 doesn't work right by default, since ipv6 relies on
multicast traffic to do neighbor discovery.

For example, I start tcpdump on the n2100, using -p to avoid putting it into
promisc mode:

root@turtle:/home/joey>tcpdump -p -n -i eth0
# Here I start ping6 from ::feb2:9663 (box next to the n2100) to
# 2001:4830:1231::1 (the n2100). There are no responses.
^Z
root@turtle:/home/joey>ifconfig eth0 allmulti; fg
14:20:01.038563 IP6 2001:4830:1231:0:20c:f1ff:feb2:9663 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:4830:1231::1, length 32
14:20:01.038975 IP6 2001:4830:1231::1 > 2001:4830:1231:0:20c:f1ff:feb2:9663: ICMP6, neighbor advertisement, tgt is 2001:4830:1231::1, length 32
14:20:01.039295 IP6 2001:4830:1231:0:20c:f1ff:feb2:9663 > 2001:4830:1231::1: ICMP6, echo request, seq 28, length 64
14:20:01.039602 IP6 2001:4830:1231::1 > 2001:4830:1231:0:20c:f1ff:feb2:9663: ICMP6, echo reply, seq 28, length 64
14:20:02.038770 IP6 2001:4830:1231:0:20c:f1ff:feb2:9663 > 2001:4830:1231::1: ICMP6, echo request, seq 29, length 64
14:20:02.039015 IP6 2001:4830:1231::1 > 2001:4830:1231:0:20c:f1ff:feb2:9663: ICMP6, echo reply, seq 29, length 64
14:20:03.042996 IP6 2001:4830:1231:0:20c:f1ff:feb2:9663 > 2001:4830:1231::1: ICMP6, echo request, seq 30, length 64
14:20:03.043320 IP6 2001:4830:1231::1 > 2001:4830:1231:0:20c:f1ff:feb2:9663: ICMP6, echo reply, seq 30, length 64
# Now ping is working.
^C
root@turtle:/home/joey>ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:14:fd:30:14:ae  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2001:4830:1231::1/64 Scope:Global
          inet6 addr: fe80::214:fdff:fe30:14ae/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:10624092 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12315556 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2505702674 (2.3 GiB)  TX bytes:3802624039 (3.5 GiB)
          Interrupt:27 Base address:0xc200 
joey@dodo:~>ifconfig eth0 # machine I was pinging from
eth0      Link encap:Ethernet  HWaddr 00:0c:f1:b2:96:63  
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2001:4830:1231:0:20c:f1ff:feb2:9663/64 Scope:Global
          inet6 addr: fe80::20c:f1ff:feb2:9663/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15302416 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14007641 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4180405781 (3.8 GiB)  TX bytes:1835701985 (1.7 GiB)

Pinging between other machines on the same network (including nslu2, various
intel white boxes etc) works ok, so I don't think it's a problem with my
switch or general network.

Some more details about this problem here:
https://www.sixxs.net/forum/?msg=setup-780039

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armel (armv5tel)

Kernel: Linux 2.6.25-2-iop32x
Locale: LANG=, LC_CTYPE= (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.25-2-iop32x depends on:
ii  debconf [debconf-2.0]         1.5.23     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92e      tools for generating an initramfs
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo

linux-image-2.6.25-2-iop32x recommends no packages.

Versions of packages linux-image-2.6.25-2-iop32x suggests:
pn  fdutils                       <none>     (no description available)
pn  linux-doc-2.6.25              <none>     (no description available)

-- debconf information excluded

-- 
see shy jo

--- End Message ---
--- Begin Message --- 
Version: 2.6.26-16

On Mon, Jun 15, 2009 at 04:16:37PM +0100, Ben Hutchings wrote:
> On Mon, Jun 15, 2009 at 02:01:44PM +0100, Sam Morris wrote:
> > found 407217 2.6.26-15
> > thanks
> > 
> > I believe I'm seeing this on an amd64 system with the following
> > hardware:
> > 
> > 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
> > 	Kernel driver in use: r8169
> > 	Kernel modules: r8169
> > 
> > That's the onboard NIC of an Asus P6T-SE.
> [...]
> 
> I think this is the same as bug #514268, which should be fixed in stable
> release 5.0.2 (package version 2.6.26-16).

Marking as fixed in that version. Jon, please reopen if the bug persists.

Cheers,
        Moritz

--- End Message ---
Reply to: