In message <20171017125829.ga35...@albert.catwhisker.org>, David Wolfskill
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> On Mon, Oct 16, 2017 at 11:27:00PM -0700, Cy Schubert wrote:
> > In message <fe754a9e-be47-4843-ab3a-2619665f1...@lastsummer.de>, Franco=
> > Fichtne
> > r writes:
> > ...
> > > wpa_supplicant 2.6_2
> > >=20
> > > No apparent issues with the ports, preliminary connectivity
> > > checks work as expected. Started a public CFT over at OPNsense
> > > to gather more feedback.
> > Agreed.
> > ....
> First: Thank you for doing this, Cy.
No problem. I was aiming to put something together in base but an hour at
noon wasn't enough so I switched gears and went after the port instead. It
was a quick win.
> I am now (also) running wpa_supplicant-2.6_2 successfully on my laptop
> (when it's running stable/11).
> I did have one mild surprise: I had rebooted my laptop to verify that
> the ports version of wpa_supplicant would work, and as the screen went
> dark, I recalled that I had failed to copy /etc/wpa_supplicant.conf to
> /usr/local/etc -- but my concern proved to be unfounded: the
> wpa_supplicant.conf in /etc/ was used (successfully).
> Question: Should one expect a wpa_supplicant-2.6_2 executable built
> under FreeBSD stable/11 (amd64) to work on the same hardware, but
> running head?
Possibly. I run head here. The things that could impact you are shared
libraries (ABI) and KBI.
> For reasons that are (at best) tangential to this topic, I track,
> build, and smoke-test both stable/11 and head daily, but only build
> the ports (daily) under (the just-built/booted) stable/11 -- depending
> on misc/compat11 to handle things as necessary for head. This works
> (well, IMO)... except that when I had configured my "head slice"
> to use the ports version of wpa_supplicant, the latter was apparently
> not happy:
> Oct 17 11:06:13 localhost kernel: wlan0: Ethernet address: 00:24:d6:7a:03:ce
> Oct 17 11:06:13 localhost wpa_supplicant: Successfully initialized wp=
> Oct 17 11:06:14 localhost wpa_supplicant: ioctl[SIOCS80211, op=3D98, =
> arg_len=3D32]: Invalid argument
> Oct 17 11:06:14 localhost wpa_supplicant: failed to IEEE80211_IOC_DEV=
> CAPS: Invalid argument
> Oct 17 11:06:14 localhost wpa_supplicant: wlan0: Failed to initialize=
> driver interface
> Oct 17 11:06:14 localhost root: /etc/rc.d/wpa_supplicant: WARNING: failed t=
> o start wpa_supplicant
You have your answer. It's likely a KBI issue.
> The laptop spends the vast bulk of its time running stable/11, so
> the threat is somewhat mitigated....
It appears you may need to in some cases rebuild some ports on head.
Cy Schubert <cy.schub...@cschubert.com>
FreeBSD UNIX: <c...@freebsd.org> Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"