From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: Bisect'ed BUG in VLAN promisc mode (6c78dcbd47) Date: Fri, 26 Sep 2008 21:41:09 +0200 Message-ID: <48DD3AD5.80800@trash.net> References: <1222437636.7598.14.camel@localhost.localdomain> <48DD0A4F.6020703@trash.net> <1222456933.2381.3.camel@localhost.localdomain> <48DD36D2.90103@trash.net> <48DD37E3.9090706@trash.net> <1222457670.2381.8.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: "netdev@vger.kernel.org" To: jdb@comx.dk Return-path: Received: from stinky.trash.net ([213.144.137.162]:46483 "EHLO stinky.trash.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752986AbYIZTlM (ORCPT ); Fri, 26 Sep 2008 15:41:12 -0400 In-Reply-To: <1222457670.2381.8.camel@localhost.localdomain> Sender: netdev-owner@vger.kernel.org List-ID: Jesper Dangaard Brouer wrote: > On Fri, 2008-09-26 at 21:28 +0200, Patrick McHardy wrote: >> Actually - one question: you're saying you're using different MAC >> addresses on the VLAN devices, so I guess thats why you're expecting >> the underlying device to still be in promiscous mode after you set >> eth1.1025 down. For devices that support multiple unicast addresses >> in hardware, we don't put the device in promiscous mode anymore. >> So the question is: is something actually not working, or did you >> just notice that the real device is no longer in promiscous mode? > > It stopped working! In the test setup I do have a machine connected to > eth1.1013, where I have a ping running, that stop working... Found it in the bugreport :) OK, I'll try to reproduce it now. > I use the tg3 driver for both netcards. Don't know if it supports it? The driver doesn't support it.