Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 08 Jan 2018 17:00:43 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-net@FreeBSD.org
Subject:   [Bug 224961] VLAN ID 0 Not Supported
Message-ID:  <bug-224961-2472-3VYHora6EM@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

--- Comment #2 from johnllyon@gmail.com ---
(In reply to Reshad Patuck from comment #1)

Netgraph -- I love it's power, but the documentation is frustratingly sparse
regarding certain fundamental concepts.

I will give ng_vlan a brief try later this week when I have some free time =
to
experiment.  Do you know if I can attach services and assign an IP to the
virtual interface created by ng_vlan?  For some context, my server is recei=
ving
traffic tagged with VLAN 0.  Services on that interface (e.g., dhcp client)
don't appear to recognize the traffic because it is tagged as vlan 0 (versus
being not tagged at all).  So I'm trying to create an interface assigned to
vlan 0 so that I my services on that interface will work.  Think ng_vlan can
help me do that?


For some context these links describe my problem and a Linux solution to it:

http://blog.0xpebbles.org/Bypassing-At-t-U-verse-hardware-NAT-table-limits
https://strscrm.io/bypassing-gigapowers-provided-modem.html
https://www.reddit.com/r/Ubiquiti/comments/60rfdr/transparent_proxy_for_802=
1xeap/dfcba6o/

I'm trying to create a FreeBSD equivalent solution.  I've already successfu=
lly
duplicated the functionality of ebtables using Netgraph.  I'm just stuck at=
 the
last part because I can't assign vlan 0 to an interface (or create a virtual
interface on vlan 0) to which I can move my services (e.g., DHCP client).

Thanks.

--=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-3VYHora6EM>