RE: 6-BETA1 iwi + wpa_supplicant fails, and sometimes silently re boots

From: Brandon S. Allbery KF8NH (allbery_at_ece.cmu.edu)
Date: 07/26/05

  • Next message: Wilko Bulte: "Re: dhclient taking all cpu" 
    To: Kirk Davis <Kirk.Davis@epsb.ca>
Date: Tue, 26 Jul 2005 15:59:09 -0400

    I won't be able to try WPA until I get home this evening (if then).

    I'm still having failures and ultimately silent reboots trying to get at
    the unsecured network on campus, however. wpa_supplicant.conf and a
    debug log attached. ---Is there some secret incantation needed to
    disable all authentication, or is that case simply not implemented/not
    tested? The log shows it timing out and failing to authenticate to a
    null BSSID, instead of simply not authenticating at all. 

    -- 
brandon s. allbery   [linux,solaris,freebsd,perl]      allbery@kf8nh.com
system administrator      [WAY too many hats]        allbery@ece.cmu.edu
electrical and computer engineering, carnegie mellon univ.         KF8NH

    ctrl_interface=/var/run/wpa_supplicant
    ctrl_interface_group=wheel
    eapol_version=1
    ap_scan=1
    fast_reauth=1

    network={
            ssid="800-7"
            scan_ssid=1
            key_mgmt=WPA-PSK
            psk="[redacted]"
            #group=TKIP
    }

    network={
            ssid="CMU"
            key_mgmt=NONE
    }

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Wilko Bulte: "Re: dhclient taking all cpu"

    Relevant Pages

    • RE: Wireless Security Notes and Findings (from this list and other places)
      ... There are two general areas of wireless security: Authentication and ... authentication standard that works with wireless networks. ... client computer runs a client program to connect to the network with a ...
      (Security-Basics)
    • Re: IP address assignment problem
      ... I have a little problem and seek for ur thoughts, let's assume I'm in a very open environment where everyone can very easily try to get his/her laptop on the network and IP addresses are assigned by a DHCP server and we are in a domain environment, how do I prevent machines that are not part of our domain to be assigned an IP address? ... This approach doesn't stop your rogue clients from connecting to other clients, but merely doesn't give them the information they normally need to do so. ... Using 802.1x, your workstations authenticate through the switch to a radius server before they are allowed any connectivity. ... This authentication can use X.509 certificates, computer account credentials from AD, or whatever else you'd normally configure radius to authenticate with. ...
      (Focus-Microsoft)
    • Re: Kerberos machine authentication - apparent authentication failures
      ... When you joined your computer to the domain your wireless network card was ... denied access until you can authenticate to a domain controller as a user. ... While kerberos is the default authentication protocol of choice, ...
      (microsoft.public.windows.server.security)
    • RE: 802.1x, Computers, Wired Security
      ... client to use EAP-TLS. ... Authentication-Provider = Windows ... Wired 802.1X Authentication failed. ... Network Adapter: Broadcom NetXtreme Gigabit Ethernet - Packet Scheduler ...
      (microsoft.public.windows.server.active_directory)
    • Re: IIS 6.0 and 401.2 and 401.1 Errors
      ... > authentication -- client and server first negotiate authentication that ... > So, if you see repeated 401.2 for the same resource from the same client, ... > authenticated connection and instead RENEGOTIATING a new connection. ... > You can easily verify this by installing "Network Monitor" from Windows ...
      (microsoft.public.inetserver.iis)