FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2026-02-26T03:49:43Z 2026-02-26T03:49:43Z Adrian Chadd adrian@FreeBSD.org 2026-02-26T03:49:43Z urn:sha1:70786de406b62bed55566ec95c932e150c25c3b3 Migrate to the new encryption key API rather than poking at the key struct directly. Differential Revision: https://reviews.freebsd.org/D54482 2025-02-26T19:29:18Z Adrian Chadd adrian@FreeBSD.org 2025-01-02T04:35:24Z urn:sha1:7067450010931479f8dd97e51e4c5bf6a4d34c7e This just mechanically converts things. * For linuxkpi, it was just used for display. * For uath, it was just used for display, as firmware doesn't report it up. Differential Revision: https://reviews.freebsd.org/D48602 Reviewed by: bz, thj 2024-07-15T18:45:30Z Adrian Chadd adrian@FreeBSD.org 2024-06-06T17:28:03Z urn:sha1:2589197adb199ec37f132dd7e279eb0795713f1e The way that net80211 and drivers are checking for the /type/ of key is to check if it's in the vap WEP key array and if so, it's a group key. If not, it's a unicast key. That's not only kind of terrible, but it's also going to be problematic with future 802.11 support (for multiple unicast keys and IGTK keys for management frame protection.) So as part of this, remove the places where this is done and instead use a pair inline functions - ieee80211_is_key_global() and ieee80211_is_key_unicast(). They currenly still use the same logic but the drivers and net80211 stack isn't doing it itself. There are still open questions about why keys are not being correctly tagged as GROUP, GTK, PTK, etc. That will be investigated and addressed in follow-up work as a pre-cursor to MFP, IGTK, etc. as mentioned above. Testing: * iwn, rtwn - STA mode Differential Revision: https://reviews.freebsd.org/D45516 2023-12-01T00:48:54Z Bjoern A. Zeeb bz@FreeBSD.org 2023-11-03T21:19:26Z urn:sha1:1c6dd33d26eb02c6145383a49150965eeca61120 This reverts commit b65f813c1ab99448278961c5ca80dc422b1eae29. As a side effect this also seems to fix wtap which seems to have lost the epoch over the input path in between. Sponsored by: The FreeBSD Foundation MFC after: 3 days 2023-10-02T14:52:57Z Bjoern A. Zeeb bz@FreeBSD.org 2023-10-02T14:44:29Z urn:sha1:f156cd892b55c04a39fa06d1899e6e316de77f03 ieee80211_node_incref() is the FreeBSD implementation of ieee80211_ref_node(). Not being interested in the node returned it was used as a shortcut in 3 drivers (ath, uath, wpi). Replace the call with the public KPI of ieee80211_ref_node() and ignore the result. This leaves us with the single internal call going ieee80211_ref_node() -> ieee80211_node_incref() and that should help increasing portability but also limiting the places to trace for node reference operations. Sponsored by: The FreeBSD Foundation MFC after: 4 weeks 2023-08-16T17:54:36Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:36Z urn:sha1:685dc743dc3b5645e34836464128e1c0558b404b Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ 2023-08-16T17:54:24Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:24Z urn:sha1:71625ec9ad2a9bc8c09784fbd23b759830e0ee5f Remove /^/[*/]\s*\$FreeBSD\$.*\n/ 2023-08-16T17:54:11Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:11Z urn:sha1:95ee2897e98f5d444f26ed2334cc7c439f9c16c6 Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ 2023-04-25T17:26:03Z Dimitry Andric dim@FreeBSD.org 2023-04-25T17:18:58Z urn:sha1:bab8274c090942cf96c44bc001307b9bffac9d7e A signed one-bit wide bit-field can take only the values 0 and -1. Clang 16 introduced a warning that "implicit truncation from 'int' to a one-bit wide bit-field changes value from 1 to -1". Fix the warnings by using C99 bool. Reported by: Clang 16 Reviewed by: emaste, jhb MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D39705 2022-05-06T22:46:57Z John Baldwin jhb@FreeBSD.org 2022-05-06T22:46:57Z urn:sha1:51776a92ca4abc726bda5749a4255876dbce550e