Search results

  1. B

    Intel Centrino Advanced-N 6235 WiFi Driver

    Thanks for the effort guys. Just wondering, did you also test 802.11n and 40 MHz channels? The last time I've looked into adding 6235 support, I had really big issues at HT40, firmware crashes, terrible throughput, .. As you've probably noticed, I've pushed the firmware into the tree already...
  2. B

    Wireless not working after resume

    I'd call these bugs actually.. I've fixed a few suspend/resume methods for the Intel wireless drivers and Adrian did so for the Atheros driver. I'll try to talk him into doing an MFC to stable/9.
  3. B

    dwa-160

    No, none of the newer Atheros 11n USB chips are supported currently.
  4. B

    multiple ssid's over a single physical wireless interface

    It's a general issue, FreeBSD's hostapd driver hasn't been told about how VAPs work. Currently you have start multiple instances, one for each VAP interface.
  5. B

    Roaming Wifi

    Depends on the network you are trying to connect to. I'm sure there is a possibility to add some kind of a 'wildcard' network block into wpa_supplicant.conf which will connect to any open network. For networks which require encryption, you'll have to add the keys..
  6. B

    FreeBSD Foundation's New Project: Implement GEM/KMS/DRI for Intel Graphics

    I guess by the time this feature is in a usable state, 9.0 will be already (or soon to be) released. I might be wrong though.. go for it kib :beer
  7. B

    About bwn on FreeBSD 8.1R amd64

    Same with other types of encryption? WPA1-TKIP maybe? That is suspicious.. smells like the hardware itself tries to decrypt the frame and net80211 tries again, hmm..
  8. B

    Driver for Intel Centrino Ultimate-N 6300

    If the cards has a device/vendor ID of 0x8086:0x422B or 0x8086:0x4238 it is supported by iwn on 8.2-RELEASE and newer.
  9. B

    About bwn on FreeBSD 8.1R amd64

    Also the output of wlandebug +crypto might be helpful.
  10. B

    About bwn on FreeBSD 8.1R amd64

    The message about the multicast update is just a warning, you can safely ignore that. I have no clue what the other message is supposed to mean though, keyidx is just the index into the key table (the group and unicast keys), but what's wrong about trying to decrypt a packet? hmm.. *looking...
  11. B

    About bwn on FreeBSD 8.1R amd64

    The bwn(4) manpages mentions some loader tunables, did you try those? Especially the usedma one?
  12. B

    [Wireless] Dell 1510 / Broadcom BCM 204 6B2

    This seems to be a new driver, totally unrelated to bwn(4) or bwi(4). The license headers in each file seems to indeed indicate that this driver can be ported without a lot of hassle (license wise), feel free to do so. :stud How stable is it anyways? The TODO file mentions a lot of missing...
  13. B

    Wireless AP problems

    If it works for over 2 hours before having any issues, I doubt it's related to configuration. It would help a lot if you can narrow this issue down as much as possible. For example, does that issue also occur if there is only one client, without any encryption, connected? Does it happen after...
  14. B

    Buildworld of 8_2_RELENG fails from 8.2-RC2 host - missing headers?

    I guess you already tried stripping everything from /usr/obj?
  15. B

    WPA auth issue with WDA-1320 adapter and Belkin router.

    This issue sounds pretty much like a bug which Adrian is chasing for some time now. Can you fill a PR and send its number to adrian@f.o?
  16. B

    macaddr_acl not taken into account in hostapd settings

    Can you verify that the macaddr_acl option ever worked? It isn't mentioned in hostapd.conf(8) and I don't see any handling in the driver_freebsd.c glue. Based on that I suppose it never actually worked.
  17. B

    Access Point selection?

    I do not see any error in that log, are you sure no association happens? From that log it looks pretty much like there is connection. Hm.. maybe the WEP key is just wrong? Can you try with network={ ssid="MY_SSID" scan_ssid=1 key_mgmt=NONE wep_tx_keyidx=0 wep_key0="my_wepkey" }...
  18. B

    Wireless Access Point Panics

    So.. looks like it is crashing while trying to do 920 ifp->if_opackets++; I have not clue why that might happen, ifp should be allocated at that point and if_opackets is just an int. Hmm.. Wanna try this? Index: sys/dev/ral/rt2661.c...
Back
Top