route monitor & RTM_IFINFO mtu

Since setting the MTU of an interface now sends an RTM_IFINFO message, it would make sense to also print the new interface MTU in monitor mode. ok? Index: route.c === RCS file: /d/cvs/src/sbin/route/route.c,v retrieving revision

missing malloc() return check in athn(4)

I added this bug recently... Index: athn.c === RCS file: /cvs/src/sys/dev/ic/athn.c,v retrieving revision 1.95 diff -u -p -r1.95 athn.c --- athn.c 12 Jan 2017 18:06:57 - 1.95 +++ athn.c 17 Jan 2017 19:33:31 -

net80211: enable tkip with 'ifconfig wpaprotos wpa1,wpa2'

The recommended way to enable WPA1/TKIP support is: ifconfig iwm0 wpaprotos wpa1,wpa2 pirofti@ noticed that 'ifconfig iwm0 wpaprotos wpa1,wpa2' is not enough to connect to a WPA1-only AP. A list of pairwise ciphers must also be provided: "ifconfig iwm0 wpaciphers tkip,ccmp" Because I forgot to

iwm: fix a timeout race

I managed to trigger the following uvm fault by continously switching an iwm(4) client between two APs on different channels, i.e. a loop that runs: ifconfig iwm0 chan X; sleep 10; ifconfig iwm chan Y; sleep 10; uvm_fault(0x819614a0, 0x7, 0, 2) -> e kernel: page fault trap, code=0

Document the RI_CLEARMARGINS flag in rasops.9

Hi tech@, The RI_CLEARMARGINS flag is used on sparc64 but isn't documented in the rasops man page. Comments? OK? Index: share/man/man9/rasops.9 === RCS file: /cvs/src/share/man/man9/rasops.9,v retrieving revision 1.16 diff -u -p

Re: xenocara fontconfig: make slight hinting the default

> Matthieu Herrb hat am 16. Januar 2017 um 23:42 > geschrieben: > > > On Sun, Jan 15, 2017 at 10:37:20AM +0100, Nils Reuße wrote: > > On 01/04/2017 01:19 PM, Nils Reuße wrote: > > > Dear all, > > > > > > fontconfig made slight hinting the default in version 2.11.95 (see

Re: 11n support for athn(4)

On Tue, Jan 17, 2017 at 10:19:39AM +, Peter Kay wrote: > From: s...@stsp.name > Sent: 17 January 2017 10:00 a.m. > To: syllops...@syllopsium.co.uk > Cc: tech@openbsd.org > Subject: Re: 11n support for athn(4) > > On Mon, Jan 16, 2017 at 11:58:51PM +, Peter Kay wrote: > >> > >> Three,

Re: 11n support for athn(4)

On Tue, Jan 17, 2017 at 11:56:09AM +0100, Stefan Sperling wrote: > Without more details, all I can do is guess. > I made one guess already (antennas) and sadly I guessed wrong. Another thing where your setup differs from mine is that you are using a device with 3 antennas, whereas my devices only

Re: 11n support for athn(4)

  Original Message   From: s...@stsp.name Sent: 17 January 2017 12:25 p.m. To: syllops...@syllopsium.co.uk; tech@openbsd.org Subject: Re: 11n support for athn(4) On Tue, Jan 17, 2017 at 11:56:09AM +0100, Stefan Sperling wrote: >> Without more details, all I can do is guess. >> I made one guess

Re: 11n support for athn(4)

On Mon, Jan 16, 2017 at 11:58:51PM +, Peter Kay wrote: > On 16 January 2017 at 23:30, Stefan Sperling wrote: > > Do you have 2 antennas properly connected to the athn card? > > Three, yes, but note that unless the antennas have been unreasonably > disturbed during the

Re: wsfont.c: remove sony8x16 and sony12x24?

On Thu, Jan 12, 2017 at 01:39:47PM +0100, Frederic Cambus wrote: > Most fonts in wsfont are not compiled in by default, and while some are > worth keeping and using, I would like to propose deleting some of them > in order to make space for larger sized fonts. > > The Sony fonts are Serif, which

Re: 11n support for athn(4)

  Original Message   From: s...@stsp.name Sent: 17 January 2017 10:00 a.m. To: syllops...@syllopsium.co.uk Cc: tech@openbsd.org Subject: Re: 11n support for athn(4) On Mon, Jan 16, 2017 at 11:58:51PM +, Peter Kay wrote: >> >> Three, yes, but note that unless the antennas have been