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> In-Reply-To: <assp.02536a3fee.20140625133245.GA9359@ige.unicamp.br> References: <assp.02527dc6be.20140624192455.GA3645@ige.unicamp.br> <assp.02536a3fee.20140625133245.GA9359@ige.unicamp.br>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?assp.0253967b0f.20140625134555.GB9359>