Re: iwn: Centrino Ultimate-N 6300 scans, doesn't dhcp?
On Thu, 26 Jan 2017 at 5:35 PM, Stefan Sperling wrote: > On Wed, Jan 25, 2017 at 08:43:11PM -0600, Austin Bentley wrote: > > Interesting. It seems that on OpenBSD the reception is quite weak. > > I've connected, HOWEVER, I have to be in the same room as my router! > > On Linux I can be anywhere in my house. > > > > I tried disabling powersave (-powersave), and still I have to be very > > I believe the powersave option is a no-op with iwn(4) so I am > not surprised it doesn't change anything. > > > close to my router. My phone can connect to it no problem anywhere in > > the house. Does anyone have any clue what's going on? Is it possible > > that the driver is permanently set on a power save mode? > > Well, it seems something strange is going on since it works with Linux. > > It is not clear whether the problem is with sending or receiving. > I would guess it is more likely that iwn(4) has some problem with > sending data, rather than receiving it. Both have to work to associate > successfully. > > You can enable some debug output like this: > > ifconfig iwn0 debug > > Look in /var/log/messages. Any beacon received should be mentioned there, > and in case a WPA handshare is attempted you should see this as well. > > Perhaps the problem has to do with regdomain settings? iwn(4) does not > do anything about those -- it relies on hardware/firmware defaults. > Does Linux print anything about regulatory domains in its dmesg? > > > On Wed, Jan 25, 2017 at 7:37 PM, Austin Bentley wrote: > > > nwid MYSSID chan 6 bssid yy:yy:yy:yy:yy:yy -58dBm HT-MCS15 > > > privacy,short_slottime,wpa1 > > Do you also happen to have this AP on a 5GHz channel or is this > AP on 2GHz only? If iwn(4) is trying to connect on 5GHz instead of 2, > that would explain why it doesn't work well through walls. > I'm facing similar issues and assuming it was a router incompatibility Issue that causes this to happen. > >
Re: iwn: Centrino Ultimate-N 6300 scans, doesn't dhcp?
On Wed, Jan 25, 2017 at 08:43:11PM -0600, Austin Bentley wrote: > Interesting. It seems that on OpenBSD the reception is quite weak. > I've connected, HOWEVER, I have to be in the same room as my router! > On Linux I can be anywhere in my house. > > I tried disabling powersave (-powersave), and still I have to be very I believe the powersave option is a no-op with iwn(4) so I am not surprised it doesn't change anything. > close to my router. My phone can connect to it no problem anywhere in > the house. Does anyone have any clue what's going on? Is it possible > that the driver is permanently set on a power save mode? Well, it seems something strange is going on since it works with Linux. It is not clear whether the problem is with sending or receiving. I would guess it is more likely that iwn(4) has some problem with sending data, rather than receiving it. Both have to work to associate successfully. You can enable some debug output like this: ifconfig iwn0 debug Look in /var/log/messages. Any beacon received should be mentioned there, and in case a WPA handshare is attempted you should see this as well. Perhaps the problem has to do with regdomain settings? iwn(4) does not do anything about those -- it relies on hardware/firmware defaults. Does Linux print anything about regulatory domains in its dmesg? > On Wed, Jan 25, 2017 at 7:37 PM, Austin Bentley wrote: > > nwid MYSSID chan 6 bssid yy:yy:yy:yy:yy:yy -58dBm HT-MCS15 > > privacy,short_slottime,wpa1 Do you also happen to have this AP on a 5GHz channel or is this AP on 2GHz only? If iwn(4) is trying to connect on 5GHz instead of 2, that would explain why it doesn't work well through walls.
Re: iwn: Centrino Ultimate-N 6300 scans, doesn't dhcp?
Interesting. It seems that on OpenBSD the reception is quite weak. I've connected, HOWEVER, I have to be in the same room as my router! On Linux I can be anywhere in my house. I tried disabling powersave (-powersave), and still I have to be very close to my router. My phone can connect to it no problem anywhere in the house. Does anyone have any clue what's going on? Is it possible that the driver is permanently set on a power save mode? On Wed, Jan 25, 2017 at 7:37 PM, Austin Bentley wrote: > I've got a ThinkPad x220 with a Centrino Ultimate-N 6300, and I'm > trying to get it to connect to a WPA1 WiFi network. Network has a > password. > > Steps taken thus far: > Tested WiFi on Linux > > Update WiFi drivers with fw_update via ethernet > > Verified /etc/firmware/iwn-6000 exists (it does) > > dmesg: > dmesg | grep iwn > iwn0 at pci2 dev 0 function 0 "Intel Centrino Ultimate-N 6300" > rev 0x3e: msi, MIM0 3T3R, MoW, address: xx:xx:xx:xx:xx:xx > > Scanning networks works: > ifconfig iwn0 scan > iwn0: flags=8843 mtu 1500 >lladdr xx:xx:xx:xx:xx:xx >index 2 priority 4 llprio 3 >groups: wlan >media: IEEE802.11 autoselect (DS1 mode 11g) >status: no network >ieee80211: nwid MYSSID chan 6 bssid yy:yy:yy:yy:yy:yy -58dBm > wpakey 0x wpaprotos wpa1,wpa2 wpaakms psk wpacipchers > tkip,ccmp wpagroupcipher tkip > nwid MYSSID chan 6 bssid yy:yy:yy:yy:yy:yy -58dBm HT-MCS15 > privacy,short_slottime,wpa1 > ... #other networks > ... > > Of course, I attempted `dhclient iwn0` with both /etc/hostname.iwn0, > and `ifconfig iwn0 nwid MYSSID wpa wpakey up`, and both > achieved this: > dhclient iwn0 > iwn0: no link ... sleeping > > The WiFi light on my laptop is constantly blinking too. > Does this indicate anything? > > Thanks, > Austin Bentley >
