Date: Wed, 25 Jun 2014 10:12:17 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: jfv@freebsd.org, Ricardo Campos Passanezi <riccp@ige.unicamp.br> Subject: Re: Solved: Re: Problem with tagged vlan after upgrading Message-ID: <201406251012.17421.jhb@freebsd.org> In-Reply-To: <assp.0253967b0f.20140625134555.GB9359@ige.unicamp.br> References: <assp.02527dc6be.20140624192455.GA3645@ige.unicamp.br> <assp.02536a3fee.20140625133245.GA9359@ige.unicamp.br> <assp.0253967b0f.20140625134555.GB9359@ige.unicamp.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, June 25, 2014 9:45:55 am Ricardo Campos Passanezi wrote: > On Wed, Jun 25, 2014 at 10:32:45AM -0300, Ricardo Campos Passanezi wrote: > > > > Some more info I've forgotten to add: > > > > - If I listen the vlan interfaces (tcpdump -i vlanX), the traffic is > > there. > > > > - I've tested the scenario: > > > > - 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. Please submit a bug report for this and cc it to jfv@FreeBSD.org. The vlanhwtag stuff should work properly. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201406251012.17421.jhb>