Date: Sun, 07 Jan 2018 05:25:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 224961] VLAN ID 0 Not Supported Message-ID: <bug-224961-2472-ZxcMsjRJ2A@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224961-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-224961-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224961 Reshad Patuck <reshadpatuck1@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |reshadpatuck1@gmail.com --- Comment #1 from Reshad Patuck <reshadpatuck1@gmail.com> --- (In reply to johnllyon from comment #0) I believe netgraph with ng_vlan can do this. I have not tested with vlan id 0 but I do remember it giving me finer contr= ol of VLANs than the if_vlan implementation. I used it when I had to separate vlan traffic in such a way that tagged tra= ffic could no longer be seen on the physical interface. You can use the example on the ng_vlan man page and set up with vlan id 0. This creates a virtual interface named ngeth which should have the traffic = you want. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224961-2472-ZxcMsjRJ2A>