Re: DHCP problems while connecting with a Wifi AP

On Thu, Dec 27, 2018 at 01:25:17PM +0100, Matthias Apitz wrote: > > Hello, > > I'm using my (Ubuntu) mobile device as AP to connect my FreeBSD laptop > to the Internet. While this is working fine most of the times, I > encounter in some situation problems getting an IP addr with DHCP from > the

Re: "iwn0: iwn_panicked: controller panicked..."

On Thu, Apr 05, 2018 at 03:35:51PM -0700, Adrian Chadd wrote: > Try disabling 11n and see if that fixes it? > Thanks, but that doesn't seem to do it. I changed the "ifconfig_wlan0" line in /etc/rc.conf from: ifconfig_wlan0="WPA DHCP" to: ifconfig_wlan0="WPA DHCP -ht" wlan now shows up as:

"iwn0: iwn_panicked: controller panicked..."

I seem to be seeing a fair number of these, especially running head (at the moment, running: FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #149 r331908M/331923:1200060: Tue Apr 3 04:48:56 PDT 2018 r...@g1-215.catwhisker.org:/common/S3/obj/usr/src/amd64.amd64/sys/CANARY

Re: Starting to try to get a new Dell Precision 5520 laptop running

On Fri, Jan 19, 2018 at 05:48:54AM -0800, David Wolfskill wrote: > ... > One of the "sticking points" so far is that the wireless device is: > none6@pci0:2:0:0: class=0x028000 card=0x00508086 chip=0x24fd8086 > rev=0x78 hdr=0x00 > vendor = 'Intel

Re: Something seems "off" counting outbound traffic (wlan? iwn?)

On Wed, Jan 03, 2018 at 09:38:54AM -0800, Adrian Chadd wrote: > hi, > > Yeah, I thought I remember some issues in the past with output handling.. > Ah -- thanks for verifying that I'm (probably) not hallucinating (about this, anyway). :-) I'm happy to start poking around, given a clue. (I

Re: Something seems "off" counting outbound traffic (wlan? iwn?)

As a possibly-interesting additional data point, here's what the script shows for another "speed" test (same URL as before), but from work: g1-252(11.1-S)[25] net_mon -e -w 5 -c 15 wlan0 wlan0: 192.168.23.119/20 IEEE 802.11 Wireless Ethernet MCS mode 11na

Something seems "off" counting outbound traffic (wlan? iwn?)

I recently configured my "perimeter device" (a 4-homed FreeBSD box named "bats"; see for a diagram) to make use of FQ-CoDel for outbound traffic on the Internet-facing NIC (em2, in this case). I failed to find a way to monitor the traffic

Re: software scan fix - please test (Was: why we can't use the net80211 taskqueue for everything)

On Sat, Feb 20, 2016 at 12:06:17PM +0200, Andriy Voskoboinyk wrote: > > hi, > > > > andriy has a few reviews out that tidy up some things, which I'd reply > > to, but .. reviews is offline. So, here's the 30 second version: > > > > * the net80211 taskqueue runs the software scan engine, and the >

Re: head/amd64 @r288358: panic: lock (sleep mutex) iwn0_com_lock not locked @ /usr/src/sys/dev/iwn/if_iwn.c:5356

On Tue, Sep 29, 2015 at 12:12:02PM -0700, Adrian Chadd wrote: > hi > > (please subscribe and email freebsd-wireless@ these things, I'm more > likely to notice!) > > It looks due to my recent taskqueue change for updateedca. I'll go fix > that today. > > Thanks, > ... Looks as if you did:

Re: Panic [page fault] in _ieee80211_crypto_delkey(): stable/10/amd64 @r286878

On Wed, Aug 19, 2015 at 12:25:38PM -0700, Adrian Chadd wrote: ... But we definitely ahe enough to put into a PR.. ... Bug 202494 - Panic [page fault] in _ieee80211_crypto_delkey() https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202494 Peace, david -- David H. Wolfskill

stable/10 panic; _ieee80211_crypto_delkey() likely involved

I was reading some recent commits to stable/10 after just having issued service netif restart iwn0 in an effort to get wlan0 to re-associate, and my laptop panicked: Fri Apr 24 15:28:37 PDT 2015 FreeBSD localhost 10.1-STABLE FreeBSD 10.1-STABLE #46 r281921M/281927:1001512: Fri Apr 24 04:24:32

Re: CTF: wpa_supplicant/hostapd 2.4 import

On Sun, Apr 19, 2015 at 02:35:17PM -0700, Rui Paulo wrote: Hi, Please test the new wpa_supplicant/hostapd. Here's the patch against FreeBSD HEAD: https://people.freebsd.org/~rpaulo/wpa-2.4.diff ... Seems OK so far for both amd64 i386; sources (prior to applying above patch)

iwn(4) link down/up cycling

The laptop I've had for some time has an iwn(4) device that has generally been working well. I recently acquired a laptop which I've set up for my spouse to use; its wireless NIC is also detected as iwn(4). However, even when rather little is going on (as in, she's not using it, because she's