On Tue, Dec 27, 2016 at 12:31:36PM +0100, Gregor Best wrote:
> On Tue, Dec 27, 2016 at 01:00:54AM +0100, Gregor Best wrote:
> > On Mon, Dec 26, 2016 at 08:44:47PM +0100, Stefan Sperling wrote:
> > > [...]
> > > E.g. at 33C3 there are APs with: RxMCS 0xf8f8f800000000000000
> > >
> > > The diff below makes OpenBSD clients work in 11n mode on such networks
> > > by relaxing our "supported MCS" 11n feature check.
> > > [...]
> >
> > To go along with the 33c3 motto: "Works for me". Thanks a lot :)
> > [...]
>
> Looks like I spoke a bit too soon. The card associates and can receive
> IPv6 router advertisements, but that seems to be it. I don't receive
> replies to DHCP requests and statically configuring an address doesn't
> yield a working connection either.
>
> A PCAP file I captured with
>
> tcpdump -y IEEE802_11 -ni iwm0 -w /tmp/nw.pcap
>
> is at [0]. The output of ifconfig and a dmesg follows. The kernel is
> one built from a CVS checkout from 0100 this morning.
>
> Is this related to an AP with weird 11n handling at all?
Not sure. Are you forcing 11a mode, by chance?
When it works it looks like this:
media: IEEE802.11 autoselect (HT-MCS14 mode 11n)
status: active
ieee80211: nwid 33C3-open chan 100 bssid ac:a3:1e:e5:e3:f1 73%
I've talked to the NOC folks last night. They're doing some crazy things to
steer clients between APs and it's not entirely clear how OpenBSD clients
will respond to that.
If you can't get it to work, try to find me at the BSD assembly or at
coffee nerds, and we can debug it together.
