From owner-freebsd-net@FreeBSD.ORG Sun Mar 31 12:57:07 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 01AF55F6 for ; Sun, 31 Mar 2013 12:57:07 +0000 (UTC) (envelope-from rlp@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id B1F9BB83 for ; Sun, 31 Mar 2013 12:57:06 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id 48886D4C44; Sun, 31 Mar 2013 14:56:59 +0200 (CEST) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id yeNrqGy+KaCj; Sun, 31 Mar 2013 14:56:58 +0200 (CEST) Received: from webmail.semihalf.com (semihalf.com [206.130.101.55]) by smtp.semihalf.com (Postfix) with ESMTPSA id 160BBD4C25; Sun, 31 Mar 2013 14:56:57 +0200 (CEST) MIME-Version: 1.0 Date: Sun, 31 Mar 2013 06:56:55 -0600 From: Pablo Ribalta Lorenzo To: Subject: Re: vlan with modified MAC fails to communicate In-Reply-To: <201303301948.r2UJm2PX061547@mail.karels.net> References: <201303301948.r2UJm2PX061547@mail.karels.net> Message-ID: X-Sender: rlp@semihalf.com User-Agent: RoundCube Webmail/0.2.2 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Cc: freebsd-net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Mar 2013 12:57:07 -0000 >> From what I see, looks like this behavior from FreeBSD side is expected >> and the changes should be incorporated to my NIC. > > I'm not sure what you mean, but there is no existing code to propagate > a MAC change on a VLAN to its parent device. I think it is a bug that > a change appears to work. Rather than to my NIC, I wanted to say that my solution can be related to improve the packet filtering for not dropping the packets in the NIC after changing vlan's MAC, my fault. Anyway you previous experience is a good hint for me, thank you for sharing it. However, I won't be able to perform concrete tests on this side once this easter weeekend passes and I have the time, so by now I can only speculate.