From owner-freebsd-current@FreeBSD.ORG  Wed Jun 25 13:45:58 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 2760AEC6
 for <freebsd-current@freebsd.org>; Wed, 25 Jun 2014 13:45:58 +0000 (UTC)
Received: from saturno.ige.unicamp.br (saturno.ige.unicamp.br [143.106.76.34])
 by mx1.freebsd.org (Postfix) with ESMTP id C044729A7
 for <freebsd-current@freebsd.org>; Wed, 25 Jun 2014 13:45:57 +0000 (UTC)
Received: from netuno.ige.unicamp.br (saturno.ige.unicamp.br [143.106.76.34])
 by saturno.ige.unicamp.br (Postfix) with ESMTPS id 90CB8359710
 for <freebsd-current@freebsd.org>; Wed, 25 Jun 2014 10:45:52 -0300 (BRT)
Received: from netuno.ige.unicamp.br ([143.106.76.2]
 helo=netuno.ige.unicamp.br)
 by saturno.ige.unicamp.br with SMTP (2.3.3); 25 Jun 2014 10:45:52 -0300
Received: by netuno.ige.unicamp.br (Postfix, from userid 1003)
 id D14677627; Wed, 25 Jun 2014 10:45:55 -0300 (BRT)
Date: Wed, 25 Jun 2014 10:45:55 -0300
From: Ricardo Campos Passanezi <riccp@ige.unicamp.br>
To: freebsd-current@freebsd.org
Subject: Solved: Re: Problem with tagged vlan after upgrading
Message-ID: <assp.0253967b0f.20140625134555.GB9359@ige.unicamp.br>
References: <assp.02527dc6be.20140624192455.GA3645@ige.unicamp.br>
 <assp.02536a3fee.20140625133245.GA9359@ige.unicamp.br>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <assp.02536a3fee.20140625133245.GA9359@ige.unicamp.br>
User-Agent: Mutt/1.5.23 (2014-03-12)
Content-Transfer-Encoding: quoted-printable
X-Assp-Version: 2.3.3(13160) on saturno.ige.unicamp.br
X-Assp-ID: saturno.ige.unicamp.br m-03952-09125
X-Assp-Session: B9BE20C90 (mail 1)
X-Assp-Original-Subject: Solved: Re: Problem with tagged vlan after upgrading
X-Assp-Server-TLS: yes
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 13:45:58 -0000

On Wed, Jun 25, 2014 at 10:32:45AM -0300, Ricardo Campos Passanezi wrote:
>=20
> Some more info I've forgotten to add:
>=20
> - If I listen the vlan interfaces (tcpdump -i vlanX), the traffic is
>   there.
>=20
> - I've tested the scenario:
>=20
>   - delete the inet from em0;
>   - create a vlan2 with th IP used by "em0"
>   - enable the vlan tag in the switch
>   - now, I can use the "vlan1" (10.0.0.0/8)o


....


The problem has been solved by issuing a "ifconfig em0 -vlanhwtag".

After that eveything is working.



--=20
Ricardo Campos Passanezi - Supervisor de Se=E7=E3o
Chave PGP e GPG P=FAblica em: http://www.ige.unicamp.br/~riccp
Instituto de Geoci=EAncias - http://www.ige.unicamp.br - UNICAMP
Tel: (19) 3521 4560