Date: Tue, 17 Dec 2013 03:07:41 GMT From: Takanori Watanabe <takawata@init-main.com> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/184918: regression on WEP Message-ID: <201312170307.rBH37fei089378@oldred.freebsd.org> Resent-Message-ID: <201312170310.rBH3A0YR049293@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 184918 >Category: kern >Synopsis: regression on WEP >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 17 03:10:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Takanori Watanabe >Release: FreeBSD-11 CURRENT >Organization: AXE inc. >Environment: FreeBSD yayoi.init-main.com 11.0-CURRENT FreeBSD 11.0-CURRENT #18 r259389:259392M: Sun Dec 15 03:53:23 JST 2013 >Description: Updating from FreeBSD 10.0-CURRENT #17 r251566M: Thu Jul 4 15:14:23 JST 2013, my ural(4) dongle does not associate WEP AP,which worked fine before. And run(4) dongle does associate, but does not decrypt WEP crypted broadcast packet. run(4) interface. This interface does not work with WEP in previous version too, but it does decrypt Broadcast packet. (Probably TX packet does not encrypted properly.) In both case, WPA2 AP works fine. What shall I do next? >How-To-Repeat: Plug interface and try to associate WEP AP. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201312170307.rBH37fei089378>