https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
--- Comment #15 from topsecretsauce ---
(In reply to topsecretsauce from comment #14)
I forgot to mention. I'm referring to this change to dhclient
https://reviews.freebsd.org/D31515
--
You are receiving this mail because:
You are the ass
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
topsecretsauce changed:
What|Removed |Added
CC||xerowings...@gmail.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
bigjohn...@gmail.com changed:
What|Removed |Added
CC||bigjohn...@gmail.com
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
--- Comment #12 from crb ---
This isn't actually happening on a wlan. My fiber network connection requires
EAP authentication to pass traffic and I'm trying to get that to work.
Christopher
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
--- Comment #11 from Hans Petter Selasky ---
kib@ : Can you comment on the question above, for WLAN EAPOL packets being
prio-tagged. Maybe a WIFI router problem?
--HPS
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
--- Comment #10 from crb ---
Hans,
I greatly appreciate your previous feedback here! Thank you
This does indeed seem to work to issue vlan 0 packets, at least as far as I can
understand looking at tcpdump output on a stock 13.1 system. H
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
--- Comment #9 from Hans Petter Selasky ---
You maybe need a 13-stable kernel.
Yes, setting the pcp, cause network traffic to use VLAN ID=0. You can check
using tcpdump ?
--HPS
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
crb changed:
What|Removed |Added
CC||c...@chrisbowman.com
--- Comment #8 from crb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
demus...@gmail.com changed:
What|Removed |Added
CC||demus...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
--- Comment #5 from johnll...@gmail.com ---
(In reply to Eugene Grosbein from comment #3)
I think therein lies the problem. We are not recognizing frames tagged as vlan
0 as being untagged. On the flip side, it seems that if we detect tha
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
Rodney W. Grimes changed:
What|Removed |Added
CC||rgri...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
Eugene Grosbein changed:
What|Removed |Added
CC||eu...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
--- Comment #2 from johnll...@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 la
--- Comment #1 from Reshad Patuck ---
(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 control
of VLANs than the if_vlan implementation.
I used it when I had to separate vlan traffic in such a way
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
Ok..
Can someone please submit a PR with a patch that addresses this? I'll
try to make sure it gets into freebsd-head.
-a
On 27 September 2014 18:24, Danny J. Mitzel wrote:
> On Sat, Sep 27, 2014 at 4:44 PM, Adrian Chadd wrote:
> > .. the spec allows vlan id=0?
>
> 0
On Sat, Sep 27, 2014 at 4:44 PM, Adrian Chadd wrote:
> .. the spec allows vlan id=0?
0 is not a valid VLAN ID but the specs do allow it
in a tagged packet, it's called "Priority tagged".
The priority bits should be interpreted when making
any queuing / scheduling decisions
.. the spec allows vlan id=0?
-a
On 27 September 2014 06:55, Tony Moseby wrote:
> Hello,
>
> FreeBSD seems to dropp frames with vlan id 0(all other id ok) does anyone know
> if this has been corrected?patch etc
>
> I can see a patch for this very same issue in Linux
Hello,
FreeBSD seems to dropp frames with vlan id 0(all other id ok) does anyone know
if this has been corrected?patch etc
I can see a patch for this very same issue in Linux but not in FreeBSD!
Thanks
___
freebsd-net@freebsd.org mailing list
http
20 matches
Mail list logo
