Re: WLAN 802.1x authentication problems

2022-01-20 Thread Christian Ehrhardt
Hi, On Fri, Jan 21, 2022 at 12:00:54AM -0700, Theo de Raadt wrote: > > In addition, I checked the code of dhclient and while it does listen > > to the RTM_80211INFO messages it will only use them to do a RESTART (drop > > things it thinks it knows about the interface and re-read all the > >

Re: WLAN 802.1x authentication problems

2022-01-20 Thread Christian Ehrhardt
Hi all, On Thu, Jan 20, 2022 at 08:01:13PM +0100, Stefan Sperling wrote: > On Thu, Jan 20, 2022 at 05:13:22PM +0100, Christian Ehrhardt wrote: > > The wpa supplicant (tries to) use routing messages of type > > RTM_80211INFO to detect WLAN access point changes. If the > &

WLAN 802.1x authentication problems

2022-01-20 Thread Christian Ehrhardt
Hi, The wpa supplicant (tries to) use routing messages of type RTM_80211INFO to detect WLAN access point changes. If the SSID or the BSSID changes compared to the last RTM_80211INFO message an ASSOC event is injected into the 802.1x state machines. The problem with this approach is that the

Re: wireguard-related mbuf panic (was: Re: panic: ieee80211_has_seq(wh) assertion failed)

2022-01-18 Thread Christian Ehrhardt
Hi Alexander, On Tue, Jan 18, 2022 at 01:51:45PM +0100, Alexander Bluhm wrote: > On Tue, Jan 18, 2022 at 12:59:25PM +0100, Christian Ehrhardt wrote: > > If so, any volunteers to commit this? > > Done. Thanks for fixing this. > > Two more things: > > - We need

Re: wireguard-related mbuf panic (was: Re: panic: ieee80211_has_seq(wh) assertion failed)

2022-01-18 Thread Christian Ehrhardt
nitial mbuf just fine and m_free() it. > I would not change this since I think it makes the code more complex for > little gain. True. Here's an updated version. ok? If so, any volunteers to commit this? regards Christian commit de01ce44f59450c9ddb0c2362bbc93eafb8cfd0a Author

Re: wireguard-related mbuf panic (was: Re: panic: ieee80211_has_seq(wh) assertion failed)

2022-01-13 Thread Christian Ehrhardt
Hi all, On Wed, Jan 12, 2022 at 08:04:11PM +0100, Alexander Bluhm wrote: > On Wed, Jan 12, 2022 at 04:21:13PM +0100, Christian Ehrhardt wrote: > > > > - if (len <= tail - head) { > > > > - /* there's enough space in the first mbuf */ > > &

Re: wireguard-related mbuf panic (was: Re: panic: ieee80211_has_seq(wh) assertion failed)

2022-01-12 Thread Christian Ehrhardt
Hi, On Wed, Jan 12, 2022 at 02:57:28PM +0100, Stefan Sperling wrote: > On Wed, Jan 12, 2022 at 10:50:50AM +0100, Christian Ehrhardt wrote: > > diff --git a/sys/kern/uipc_mbuf.c b/sys/kern/uipc_mbuf.c > > index 5e4cb5ba88..d8b9e751c6 100644 > > --- a/sys/kern/uipc_mbuf

Re: wireguard-related mbuf panic (was: Re: panic: ieee80211_has_seq(wh) assertion failed)

2022-01-12 Thread Christian Ehrhardt
the iwx(4) in my machine. > > Christian Ehrhardt (over at Genua) provided a diff that printf's when > there's a read-only mbuf passed to m_pullup: > > Index: uipc_mbuf.c > === > RCS file: /home/OpenBSD/cvs/src/sys/k

Re: Consistent Kernel Panic-Hardware-Related?

2013-07-08 Thread Christian Ehrhardt
Hi, On Thu, Jul 04, 2013 at 09:56:56AM -0700, Scott Vanderbilt wrote: I've been trying to build userland repeatedly over the past few days on a particular machine and consistently get kernel panics, though never at exactly the same point in the process. The latest occurred midway through

Re: Wrong destinatino APIC-ID in i386 MSI messages

2012-09-21 Thread Christian Ehrhardt
Hi, On Fri, Sep 21, 2012 at 11:53:23AM +0200, Mark Kettenis wrote: there are machines (in particular those based on AMD CPUs) where the APIC-ID of the boot CPU's LAPIC is not zero. Instead APIC-ID zero is apparently assigned to the first IO-APIC. AFAICS we will mis-route MSI interrupts on

Wrong destinatino APIC-ID in i386 MSI messages

2012-09-18 Thread Christian Ehrhardt
Hi, there are machines (in particular those based on AMD CPUs) where the APIC-ID of the boot CPU's LAPIC is not zero. Instead APIC-ID zero is apparently assigned to the first IO-APIC. AFAICS we will mis-route MSI interrupts on such a machine. The symptom (apart from MSI interrupts not working)