[Bug 203088] [patch] net/if_media.h: remove obsolete mode (IFM_IEEE80211_IBSS)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203088 Andriy Voskoboinyk changed: What|Removed |Added Depends on||203086 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
[Bug 203086] [patch] security/wpa_supplicant or from base: fix WPA-None in IBSS mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203086 Andriy Voskoboinyk changed: What|Removed |Added Blocks||203088 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
[Bug 203088] [patch] net/if_media.h: remove obsolete mode (IFM_IEEE80211_IBSS)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203088 Bug ID: 203088 Summary: [patch] net/if_media.h: remove obsolete mode (IFM_IEEE80211_IBSS) Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: s3er...@gmail.com Keywords: patch Created attachment 161025 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161025&action=edit Remove IFM_IEEE80211_IBSS from net/if_media.h The IFM_IEEE80211_IBSS mode is not used in the kernel and should be removed (or aliased to IFM_IEEE80211_ADHOC) to prevent any misuses of it. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
[Bug 203086] [patch] security/wpa_supplicant or from base: fix WPA-None in IBSS mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203086 Bug ID: 203086 Summary: [patch] security/wpa_supplicant or from base: fix WPA-None in IBSS mode Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: s3er...@gmail.com Keywords: patch Created attachment 161021 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161021&action=edit Fix.diff -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Problem reports for freebsd-wireless@FreeBSD.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open|163312 | [panic] [ath] kernel panic: page fault with ath0 Open|166190 | [ath] TX hangs and frames stuck in TX queue Open|166357 | [ath] 802.11n TX stall when the first frame in th Open|169362 | [ath] AR5416: radar pulse PHY errors sometimes in 5 problems total for which you should take action. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: looking for if_rsu testers
oh, and I should add: * - PS_ACTIVE actually means "fully on" - it's not actually doing any intelligent power saving. We should port over the basic power management code from rtlwifi so we put the NIC into off mode if it's not active, and into power-save mode if it's not associated - much like what I did with ath(4) for network-sleep. * I think the transmit path is always using TID 0, rather than an appropriate TID for things. We have to fix that before we do 11n or lulz will ensue. * the nic supports softap, ibss and monitor modes - it'd be nice to at least get monitor mode working as a way of testing out 11n.. -adrian On 13 September 2015 at 12:45, Adrian Chadd wrote: > hi all, > > I've done some digging into if_rsu (thanks to idwer on #freebsd-wifi > on efnet!) and found a few places that needed addressing. I haven't > yet enabled 11n on the thing yet, but it now seems a bunch more stable > and associating-y than it did before. > > Here's what I've found thus far: > > http://urbinek.eu/_soft/RTL819xSU_usb_linux_v2.6.6.0.20120405/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/document/RTL8712_D0_1_Programming_Guide_20090601.pdf > > http://www.urbinek.eu/_soft/RTL819xSU_usb_linux_v2.6.6.0.20120405/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/ReleaseNotes.pdf > > I also looked at the rtlwifi driver in linux and the fork specifically > for this particular chipset for ideas: > > https://github.com/chunkeey/rtl8192su/tree/master/rtlwifi > > This is a mostly-smart device. ie, the firmware handles scanning, > 802.11 association, transmit rate control, and I /think/ at least > something to do with 11n aggregation - but I don't know the full > details there yet. > > * openbsd adds a ENOTSUPP stub method for ic_send_mgmt() - ie, it > blocks all software-generated management frames out. The general idea > here is that the device handles scan, probe, assoc req, etc itself. I > bet freebsd transmitting its own assoc request / probe requests at the > same time the device is was confusing things. > * it's smart like iwm/iwn/etc - however scan returns a survey message > set, not beacons - so we should directly populate the scan cache > rather than the current hack of faking a beacon to the stack > * handle the STA disassociate message - yes, it's actually legit. > * the debug sysctl is now a bitmap, so you can see interesting things > without getting spammed. The most interesting one is the /text/ > firmware debug messages - sysctl hw.usb.rsu.debug=0x200 - which is > actually pretty enlightening. > * we don't yet print out the join message response code - it does tell > you about failures if they occur. > * there's some very large scan-to-scan differences in reported RSSI, > which is highly suspicious. That's worth looking into, in case our > calibration code is suspect. > > So, if you're using if_rsu then please update to the latest -head and > try it out. I'm very interested in the results. firmware messages via > debugging is also good - compile a kernel with USB_DEBUG, and sysctl > hw.usb.rsu.debug=0x200 . It'll actually give you text strings as > debugging info, which is highly awesome. > > Thanks! > > > -adrian ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
looking for if_rsu testers
hi all, I've done some digging into if_rsu (thanks to idwer on #freebsd-wifi on efnet!) and found a few places that needed addressing. I haven't yet enabled 11n on the thing yet, but it now seems a bunch more stable and associating-y than it did before. Here's what I've found thus far: http://urbinek.eu/_soft/RTL819xSU_usb_linux_v2.6.6.0.20120405/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/document/RTL8712_D0_1_Programming_Guide_20090601.pdf http://www.urbinek.eu/_soft/RTL819xSU_usb_linux_v2.6.6.0.20120405/rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405/ReleaseNotes.pdf I also looked at the rtlwifi driver in linux and the fork specifically for this particular chipset for ideas: https://github.com/chunkeey/rtl8192su/tree/master/rtlwifi This is a mostly-smart device. ie, the firmware handles scanning, 802.11 association, transmit rate control, and I /think/ at least something to do with 11n aggregation - but I don't know the full details there yet. * openbsd adds a ENOTSUPP stub method for ic_send_mgmt() - ie, it blocks all software-generated management frames out. The general idea here is that the device handles scan, probe, assoc req, etc itself. I bet freebsd transmitting its own assoc request / probe requests at the same time the device is was confusing things. * it's smart like iwm/iwn/etc - however scan returns a survey message set, not beacons - so we should directly populate the scan cache rather than the current hack of faking a beacon to the stack * handle the STA disassociate message - yes, it's actually legit. * the debug sysctl is now a bitmap, so you can see interesting things without getting spammed. The most interesting one is the /text/ firmware debug messages - sysctl hw.usb.rsu.debug=0x200 - which is actually pretty enlightening. * we don't yet print out the join message response code - it does tell you about failures if they occur. * there's some very large scan-to-scan differences in reported RSSI, which is highly suspicious. That's worth looking into, in case our calibration code is suspect. So, if you're using if_rsu then please update to the latest -head and try it out. I'm very interested in the results. firmware messages via debugging is also good - compile a kernel with USB_DEBUG, and sysctl hw.usb.rsu.debug=0x200 . It'll actually give you text strings as debugging info, which is highly awesome. Thanks! -adrian ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros wireless interface not working
hiya, ok. There aren't any plans yet to do that driver. I have all the hardwrae and documentation (i was part of the team that did bringup and driver development for this particular chip, so I know it pretty well) but I have too much else going on at the moment. I'll send an email out to the list if/when I have done an initial ath10k port from linux. Thanks! -a On 12 September 2015 at 20:35, Sreenath Battalahalli wrote: > Though the documentation that came with the laptop does not say anything, > the data sheet of the model on Amazon does say it is 802.11ac. > > -Sreenath > > > On Sat, 9/12/15, Adrian Chadd wrote: > > Subject: Re: Atheros wireless interface not working > To: "Sreenath Battalahalli" > Cc: "freebsd-wireless@freebsd.org" > Date: Saturday, September 12, 2015, 3:24 PM > > Is it the 11ac part? > > > -a > > > On 11 September 2015 at > 23:16, Sreenath Battalahalli > > wrote: > > Hi > > > > I got a new laptop (Acer E5-573) that has > an atheros wireless adapter. > > However, > the driver available with Freebsd 10.2 does not recognise > the adapter, and I don't see the wlan0 interface. > > > > Here are relevant > lines from > > $ pciconf -lv > > > > none2@pci0:3:0:0: > class=0x028000 card=0x080611ad chip=0x0042168c > rev=0x30 > > hdr=0x00 > > vendor = > 'Atheros Communications Inc.' > > > class = network > > > > dmesg shows one > following lines for the same device. > > > pci3: at device 0.0 (no driver attached) > > > > any help in getting > this working appreciated. > > > > thanks, > > > Sreenath > > > > > ___ > > freebsd-wireless@freebsd.org > mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" > ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
