Le vendredi 28 septembre 2012 00:21:47 Francois Romieu a écrit :

Can you send an 'ip -s link' before any ipv6 traffic flows, then
after ?

Before ipv6 traffic

% ip -s link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    RX: bytes  packets  errors  dropped overrun mcast   
    0          0        0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    0          0        0       0       0       0      
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state 
UP mode DEFAULT qlen 1000
    link/ether 30:85:a9:ee:43:fa brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast   
    2607155    2232     0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    142314     1725     0       0       0       0

During tcpdump interception

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    RX: bytes  packets  errors  dropped overrun mcast   
    0          0        0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    0          0        0       0       0       0      
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state 
UP mode DEFAULT qlen 1000
    link/ether 30:85:a9:ee:43:fa brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast   
    4191544    4587     0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    268787     3317     0       0       0       0 

After set set eth0 in promisc mode

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    RX: bytes  packets  errors  dropped overrun mcast   
    0          0        0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    0          0        0       0       0       0      
2: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether 30:85:a9:ee:43:fa brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast   
    10301337   12212    0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    803894     9309     0       0       0       0 

quoted

% dmesg | grep r8169

[    1.810423] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    1.810548] r8169 0000:03:00.0: irq 44 for MSI/MSI-X
[    1.810671] r8169 0000:03:00.0: eth0: RTL8168f/8111f at
0xffffc900057ae000, 30:85:a9:ee:43:fa, XID 08000800 IRQ 44 [    1.810672]
r8169 0000:03:00.0: eth0: jumbo features [frames: 9200 bytes, tx
checksumming: ko]

Hayes, is there by any luck something different for the 8168f regarding
the layout of the multicast filtering registers ?

I don't have sufficient skills in networks to understand what do you mean, 
sorry. Any command line, files comparing to get the information?