Re: [zd1211-devs] problems with zd1211 and wpa

[John H. <mis...@gm...>]

ok, i seem to have figured out one thing.
psk=3D is supposed to be the result of wpa_passphrase, not the ascii
text, woopsie.

but i still can't get on:(   i did it in console and it says "cannot
find ssid "blahblah" and quotes my ssid, which is not hidden, and
easily discoverable in windows.

am i supposed to even have to do iwconfig wlan0 essid blah?



On 12/21/05, John H. <mis...@gm...> wrote:
> woopsie, i meant 1.2.0.
> http://zd1211.ath.cx/zd1211
> it's from zydas.
>
> hmm, how can i compile a recent version of wpa supplicant to get it to
> have zd1211 support if i use r48 dir?  how do i compile it using the
> r48 dir????
>
> On 12/21/05, Jose Pascual <jos...@al...> wrote:
> > Please, run "wpa_supplican -version" and write version, (1.2.5 is not a
> > known version for me)
> >
> > someting important is to recompile wpa_supplicant source using your r48
> > directory.
> >
> > > -----Mensaje original-----
> > > De: zd1...@li...
> > > [mailto:zd1...@li...] En nombre de John H.
> > > Enviado el: mi=E9rcoles, 21 de diciembre de 2005 17:51
> > > Para: Jose Pascual
> > > CC: zd1...@li...
> > > Asunto: Re: [zd1211-devs] problems with zd1211 and wpa
> > >
> > >
> > > i am using 48 on athlon x86 fc4 machine.
> > >
> > > i have to use wpa 1.2.5 because that's the only one i could
> > > find with zd1211 support.
> > >
> > > On 12/21/05, Jose Pascual <jos...@al...> wrote:
> > > > Hi,
> > > >
> > > > I have using WPA without no problem (saving WEP and WPA
> > > configured at
> > > > the same time in same AP),
> > > >
> > > > Are you using release r48?
> > > > which arquitecture (x86 ppc arm ...)?
> > > > What version of wpa_supplicant are you using (0.3.9, 0.4.7, ...)?
> > > >
> > > > example
> > > >
> > > > # Only WPA-PSK is used. Any valid cipher combination is accepted.
> > > >
> > > > ap_scan=3D1
> > > >
> > > > network=3D{
> > > >        ssid=3D"MyAp"
> > > >        proto=3DWPA
> > > >        key_mgmt=3DWPA-PSK
> > > >        pairwise=3DCCMP TKIP
> > > >          group=3DCCMP TKIP WEP104 WEP40
> > > >        psk=3D"testingWPA"
> > > >        priority=3D2
> > > > }
> > > >
> > > > regards
> > > >
> > > > > -----Mensaje original-----
> > > > > De: zd1...@li...
> > > > > [mailto:zd1...@li...] En
> > > nombre de John
> > > > > H. Enviado el: mi=E9rcoles, 21 de diciembre de 2005 16:50
> > > > > Para: Jose Pascual
> > > > > CC: zd1...@li...
> > > > > Asunto: Re: [zd1211-devs] problems with zd1211 and wpa
> > > > >
> > > > >
> > > > > sheesh, i set the settings, i had to add
> > > > > psetting->wpasupport=3D1 as it was not there.
> > > > >
> > > > > the only way i can keep wpa_supplicant from locking up
> > > ifconfig and
> > > > > everything else is to set ap_scan=3D0 to
> > > wpa_supplicant.conf in /etc.
> > > > >
> > > > > even if i set essid manually with iwconfig wlan0 essid
> > > myssid, after
> > > > > i run the aforementioned wpasupplicant command, it resets
> > > the essid,
> > > > > as you can see from iwconfig, to "" again.
> > > > >
> > > > > i don't get why this is sooooooooo difficult:(  the essid is not
> > > > > hidden or anything, and i can get on any open network, i
> > > just cannot
> > > > > manage to get on a wpa network.
> > > > >
> > > > > On 12/21/05, John H. <mis...@gm...> wrote:
> > > > > > ok, in this case, it is not hidden.
> > > > > > where do i set those settings?  in the source itself?
> > > > > >
> > > > > >
> > > > > > On 12/21/05, Jose Pascual <jos...@al...> wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > first of all, in the driver r48 in function
> > > > > > > zd1205_init_card_setting, be sure you have
> > > > > > >         pSetting->HiddenSSID =3D 1;       //enable hidden ess=
id
> > > > > > >         pSetting->EncryOnOff =3D 1;   //enable encryption
> > > > > > >           pSetting->WPASupport =3D 1;   //enable WPA
> > > > > > >
> > > > > > > if AP has essid broadcast hidden, use iwconfig to
> > > config essid
> > > > > > > manually and wait 2 seconds before start wpa_supplicant,
> > > > > > >
> > > > > > > try it and comment results,
> > > > > > >
> > > > > > > regards
> > > > > > >
> > > > > > >
> > > > > > > > -----Mensaje original-----
> > > > > > > > De: zd1...@li...
> > > > > > > > [mailto:zd1...@li...] En
> > > > > nombre de John
> > > > > > > > H. Enviado el: mi=E9rcoles, 21 de diciembre de 2005 5:42
> > > > > > > > Para: zd1...@li...
> > > > > > > > Asunto: [zd1211-devs] problems with zd1211 and wpa
> > > > > > > >
> > > > > > > >
> > > > > > > > Sheesh, why is it so hard to get this working with WPA?
> > > > >  It works
> > > > > > > > fine without.  I followed the instructions as per
> > > this page.
> > > > > > > > http://ubuntuforums.org/archive/index.php/t-92327.html
> > > > > > > > on my fedora core 4 machine
> > > > > > > >
> > > > > > > > here is my /etc/wpa_supplicant.conf.  Now I set the essid
> > > > > > > > manually, then issue the command wpa_supplicant -Bw
> > > -i wlan0
> > > > > > > > -c /etc/wpa_supplicant.conf -D zydas And then I ran
> > > > > dhclient wlan0,
> > > > > > > > but it never gets the IP.  Then the keyboard, but not
> > > > > the mouse,
> > > > > > > > stopped working.  help?
> > > > > > > >
> > > > > > > > ##### Example wpa_supplicant configuration file
> > > > > > > > ############################### # Empty lines and lines
> > > > > starting
> > > > > > > > with # are ignored
> > > > > > > >
> > > > > > > > # NOTE! This file may contain password information
> > > and should
> > > > > > > > probably be made # readable only by root user on multiuser
> > > > > > > > systems.
> > > > > > > >
> > > > > > > > # global configuration (shared by all network blocks) #
> > > > > > > > # Interface for separate control program. If this
> > > is specified,
> > > > > > > > wpa_supplicant # will create this directory and a
> > > UNIX domain
> > > > > > > > socket for listening to requests # from external programs
> > > > > > > > (CLI/GUI, etc.) for status information and #
> > > configuration. The
> > > > > > > > socket file will be named based on the interface name, so #
> > > > > > > > multiple wpa_supplicant processes can be run at the
> > > > > same time if
> > > > > > > > more than # one interface is used. #
> > > /var/run/wpa_supplicant
> > > > > > > > is the recommended directory for sockets and by # default,
> > > > > > > > wpa_cli will use it when trying to connect with
> > > > > > > > wpa_supplicant. ctrl_interface=3D/var/run/wpa_supplicant
> > > > > > > >
> > > > > > > > # Access control for the control interface can be
> > > configured
> > > > > > > > by setting the # directory to allow only members of
> > > a group to
> > > > > > > > use sockets. This way, it is # possible to run
> > > > > wpa_supplicant as root
> > > > > > > > (since it needs to change network # configuration
> > > and open raw
> > > > > > > > sockets) and still allow GUI/CLI components to be # run as
> > > > > > > > non-root users. However, since the control interface
> > > > > can be used
> > > > > > > > to # change the network configuration, this access
> > > needs to be
> > > > > > > > protected in many # cases. By default, wpa_supplicant is
> > > > > > > > configured to use gid 0 (root). If you # want to allow
> > > > > > > > non-root users to use the contron interface, add a
> > > new group #
> > > > > and change
> > > > > > > > this value to match with that group. Add users that
> > > > > should have #
> > > > > > > > control interface access to this group. # # This
> > > > > variable can be a
> > > > > > > > group name or gid. #ctrl_interface_group=3Dwheel
> > > > > ctrl_interface_group=3D0
> > > > > > > >
> > > > > > > > # IEEE 802.1X/EAPOL version
> > > > > > > > # wpa_supplicant was implemented based on IEEE
> > > > > 802-1X-REV-d8 which
> > > > > > > > defines # EAPOL version 2. However, there are many APs
> > > > > that do not
> > > > > > > > handle the new # version number correctly (they seem to
> > > > > drop the
> > > > > > > > frames completely). In order # to make wpa_supplicant
> > > > > interoperate
> > > > > > > > with these APs, the version number is set # to 1 by
> > > > > default. This
> > > > > > > > configuration value can be used to set it to the
> > > new # version
> > > > > > > > (2). eapol_version=3D1
> > > > > > > >
> > > > > > > > # AP scanning/selection
> > > > > > > > # By default, wpa_supplicant requests driver to perform AP
> > > > > > > > scanning and then # uses the scan results to select a
> > > > > suitable AP.
> > > > > > > > Another alternative is to # allow the driver to
> > > take care of
> > > > > > > > AP scanning and selection and use # wpa_supplicant just to
> > > > > > > > process EAPOL frames based on IEEE 802.11 association #
> > > > > information from
> > > > > > > > the driver. # 1: wpa_supplicant initiates scanning and AP
> > > > > > > > selection # 0: driver takes care of scanning, AP selection,
> > > > > > > > and IEEE 802.11 association
> > > > > > > > #    parameters (e.g., WPA IE generation); this
> > > mode can also
> > > > > > > > be used with
> > > > > > > > #    non-WPA drivers when using IEEE 802.1X mode
> > > > > > > > ap_scan=3D2
> > > > > > > >
> > > > > > > > # network block
> > > > > > > > #
> > > > > > > > # Each network (usually AP's sharing the same SSID) is
> > > > > configured
> > > > > > > > as a separate # block in this configuration file.
> > > The network
> > > > > > > > blocks are in preference order # (the first match
> > > is used). #
> > > > > > > > # network block fields: # # ssid: SSID (mandatory);
> > > either as
> > > > > > > > an ASCII string with double quotation or
> > > > > > > > #       as hex string; network name
> > > > > > > > #
> > > > > > > > # scan_ssid:
> > > > > > > > #       0 =3D do not scan this SSID with specific
> > > Probe Request
> > > > > > > > frames (default)
> > > > > > > > #       1 =3D scan with SSID-specific Probe Request frames
> > > > > > > > (this can be used to
> > > > > > > > #           find APs that do not accept broadcast
> > > SSID or use
> > > > > > > > multiple SSIDs;
> > > > > > > > #           this will add latency to scanning, so
> > > enable this
> > > > > > > > only when needed)
> > > > > > > > #
> > > > > > > > # bssid: BSSID (optional); if set, this network block
> > > > > is used only
> > > > > > > > when
> > > > > > > > #       associating with the AP using the configured BSSID
> > > > > > > > #
> > > > > > > > # priority: priority group (integer)
> > > > > > > > # By default, all networks will get same priority
> > > group (0).
> > > > > > > > If some of the # networks are more desirable, this field
> > > > > can be used
> > > > > > > > to change the order in # which wpa_supplicant goes
> > > through the
> > > > > > > > networks when selecting a BSS. The # priority
> > > groups will be
> > > > > > > > iterated in decreasing priority (i.e., the larger the #
> > > > > priority
> > > > > > > > value, the sooner the network is matched against the scan
> > > > > > > > results). # Within each priority group, networks will
> > > > > be selected
> > > > > > > > based on security # policy, signal strength, etc. # Please
> > > > > > > > note that AP scanning with scan_ssid=3D1 is not using this
> > > > > priority to #
> > > > > > > > select the order for scanning. Instead, it uses the
> > > order the
> > > > > > > > networks are in # the configuration file. # #
> > > proto: list of
> > > > > > > > accepted protocols # WPA =3D WPA/IEEE 802.11i/D3.0 # RSN
> > > > > =3D WPA2/IEEE
> > > > > > > > 802.11i (also WPA2 can be used as an alias for RSN)
> > > # If not
> > > > > > > > set, this defaults to: WPA RSN # # key_mgmt: list
> > > of accepted
> > > > > > > > authenticated key management protocols # WPA-PSK =3D WPA
> > > > > > > > pre-shared key (this requires 'psk' field) # WPA-EAP =3D WP=
A
> > > > > > > > using EAP authentication (this can use an external
> > > > > > > > #       program, e.g., Xsupplicant, for IEEE 802.1X EAP
> > > > > Authentication
> > > > > > > > # IEEE8021X =3D IEEE 802.1X using EAP authentication and
> > > > > > > > (optionally) dynamically
> > > > > > > > #       generated WEP keys
> > > > > > > > # NONE =3D WPA is not used; plaintext or static WEP could b=
e
> > > > > > > > used # If not set, this defaults to: WPA-PSK WPA-EAP # #
> > > > > > > > pairwise: list of accepted pairwise (unicast)
> > > ciphers for WPA
> > > > > > > > # CCMP =3D AES in Counter mode with CBC-MAC [RFC 3610, IEEE
> > > > > > > > 802.11i/D7.0] # TKIP =3D Temporal Key Integrity
> > > Protocol [IEEE
> > > > > > > > 802.11i/D7.0] # NONE =3D Use only Group Keys
> > > (deprecated, should
> > > > > > > > not be included if APs support
> > > > > > > > #       pairwise keys)
> > > > > > > > # If not set, this defaults to: CCMP TKIP
> > > > > > > > #
> > > > > > > > # group: list of accepted group
> > > (broadcast/multicast) ciphers
> > > > > > > > for WPA # CCMP =3D AES in Counter mode with CBC-MAC
> > > [RFC 3610,
> > > > > > > > IEEE 802.11i/D7.0] # TKIP =3D Temporal Key Integrity Protoc=
ol
> > > > > > > > [IEEE 802.11i/D7.0] # WEP104 =3D WEP (Wired
> > > Equivalent Privacy)
> > > > > > > > with 104-bit key # WEP40 =3D WEP (Wired Equivalent
> > > Privacy) with
> > > > > > > > 40-bit key [IEEE 802.11] # If not set, this
> > > defaults to: CCMP
> > > > > > > > TKIP WEP104 WEP40 # # psk: WPA preshared key; 256-bit
> > > > > > > > pre-shared key # The key used in WPA-PSK mode can
> > > be entered
> > > > > > > > either as 64 hex-digits, i.e., # 32 bytes or as an ASCII
> > > > > > > > passphrase (in which case, the real PSK will be # generated
> > > > > > > > using the passphrase and SSID). ASCII passphrase must be
> > > > > > > > between # 8 and 63 characters (inclusive). # This
> > > field is not
> > > > > > > > needed, if WPA-EAP is used. # Note: Separate tool,
> > > > > > > > wpa_passphrase, can be used to generate 256-bit keys # from
> > > > > > > > ASCII passphrase. This process uses lot of CPU and
> > > > > > > > wpa_supplicant # startup and reconfiguration time can be
> > > > > > > > optimized by generating the PSK only # only when the
> > > > > > > > passphrase or SSID has actually changed. # #
> > > eapol_flags: IEEE
> > > > > > > > 802.1X/EAPOL options (bit field) # Dynamic WEP key
> > > require for
> > > > > > > > non-WPA mode # bit0 (1): require dynamically
> > > generated unicast
> > > > > > > > WEP key # bit1 (2): require dynamically generated broadcast
> > > > > > > > WEP key
> > > > > > > > #       (3 =3D require both keys; default)
> > > > > > > > #
> > > > > > > > # Following fields are only used with internal EAP
> > > > > > > > implementation. # eap: space-separated list of accepted
> > > > > EAP methods
> > > > > > > > #       MD5 =3D EAP-MD5 (unsecure and does not generate key=
ing
> > > > > > > > material ->
> > > > > > > > #                       cannot be used with WPA; to be used
> > > > > > > > as a Phase 2 method
> > > > > > > > #                       with EAP-PEAP or EAP-TTLS)
> > > > > > > > #       MSCHAPV2 =3D EAP-MSCHAPv2 (cannot be used separatel=
y
> > > > > > > > with WPA; to be used
> > > > > > > > #               as a Phase 2 method with EAP-PEAP
> > > or EAP-TTLS)
> > > > > > > > #       OTP =3D EAP-OTP (cannot be used separately with
> > > > > WPA; to be used
> > > > > > > > #               as a Phase 2 method with EAP-PEAP
> > > or EAP-TTLS)
> > > > > > > > #       GTC =3D EAP-GTC (cannot be used separately with
> > > > > WPA; to be used
> > > > > > > > #               as a Phase 2 method with EAP-PEAP
> > > or EAP-TTLS)
> > > > > > > > #       TLS =3D EAP-TLS (client and server certificate)
> > > > > > > > #       PEAP =3D EAP-PEAP (with tunnelled EAP authenticatio=
n)
> > > > > > > > #       TTLS =3D EAP-TTLS (with tunnelled EAP or
> > > > > > > > PAP/CHAP/MSCHAP/MSCHAPV2
> > > > > > > > #                        authentication)
> > > > > > > > #       If not set, all compiled in methods are allowed.
> > > > > > > > #
> > > > > > > > # identity: Identity string for EAP
> > > > > > > > # anonymous_identity: Anonymous identity string for
> > > EAP (to be
> > > > > > > > used as the
> > > > > > > > #       unencrypted identity with EAP types that support
> > > > > > > > different tunnelled
> > > > > > > > #       identity, e.g., EAP-TTLS)
> > > > > > > > # password: Password string for EAP
> > > > > > > > # ca_cert: File path to CA certificate file. This file can
> > > > > > > > have one or more
> > > > > > > > #       trusted CA certificates. If ca_cert is not included=
,
> > > > > > > > server certificate
> > > > > > > > #       will not be verified. This is insecure and the CA
> > > > > > > > file should always be
> > > > > > > > #       configured.
> > > > > > > > # client_cert: File path to client certificate file
> > > > > > > > # private_key: File path to client private key file
> > > > > > > > # private_key_passwd: Password for private key file
> > > > > > > > # phase1: Phase1 (outer authentication, i.e., TLS
> > > > > tunnel) parameters
> > > > > > > > #       (string with field-value pairs, e.g., "peapver=3D0"=
 or
> > > > > > > > #       "peapver=3D1 peaplabel=3D1")
> > > > > > > > #       'peapver' can be used to force which PEAP version (=
0
> > > > > > > > or 1) is used.
> > > > > > > > #       'peaplabel=3D1' can be used to force new
> > > label, "client
> > > > > > > > PEAP encryption",
> > > > > > > > #       to be used during key derivation when PEAPv1 or
> > > > > > > > newer. Most existing
> > > > > > > > #       PEAPv1 implementation seem to be using the
> > > old label,
> > > > > > > > "client EAP
> > > > > > > > #       encryption", and wpa_supplicant is now using that a=
s
> > > > > > > > the default value.
> > > > > > > > #       Some servers, e.g., Radiator, may require
> > > peaplabel=3D1
> > > > > > > > configuration to
> > > > > > > > #       interoperate with PEAPv1; see eap_testing.txt for
> > > > > > > > more details.
> > > > > > > > #       'peap_outer_success=3D0' can be used to terminate P=
EAP
> > > > > > > > authentication on
> > > > > > > > #       tunneled EAP-Success. This is required with some
> > > > > > > > RADIUS servers that
> > > > > > > > #       implement
> > > > > draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
> > > > > > > > #       Lucent NavisRadius v4.4.0 with PEAP in "IETF
> > > > > Draft 5" mode)
> > > > > > > > # phase2: Phase2 (inner authentication with TLS tunnel)
> > > > > parameters
> > > > > > > > #       (string with field-value pairs, e.g.,
> > > "auth=3DMSCHAPV2")
> > > > > > > > # Following certificate/private key fields are used
> > > in inner
> > > > > > > > Phase2 # authentication when using EAP-TTLS or EAP-PEAP. #
> > > > > > > > ca_cert2: File path to CA certificate file. This
> > > file can have
> > > > > > > > one or more
> > > > > > > > #       trusted CA certificates. If ca_cert2 is not
> > > > > included, server
> > > > > > > > #       certificate will not be verified. This is insecure
> > > > > > > > and the CA file
> > > > > > > > #       should always be configured.
> > > > > > > > # client_cert2: File path to client certificate file #
> > > > > > > > private_key2: File path to client private key file #
> > > > > > > > private_key2_passwd: Password for private key file
> > > > > > > >
> > > > > > > > # Example blocks:
> > > > > > > >
> > > > > > > > # Only WPA-PSK is used. Any valid cipher combination is
> > > > > accepted.
> > > > > > > >
> > > > > > > >    network=3D{
> > > > > > > >    ssid=3D"NetworkForMe"
> > > > > > > >    scan_ssid=3D1
> > > > > > > >    pairwise=3DTKIP
> > > > > > > >    psk=3D"mykeywords"
> > > > > > > >    key_mgmt=3DWPA-PSK
> > > > > > > >    proto=3DWPA
> > > > > > > >    }
> > > > > > > >
> > > > > > > >
> > > > > > > > -------------------------------------------------------
> > > > > > > > This SF.net email is sponsored by: Splunk Inc. Do you
> > > > > grep through
> > > > > > > > log files for problems?  Stop!  Download the new
> > > AJAX search
> > > > > > > > engine that makes searching your log files as easy as
> > > > > surfing the
> > > > > > > > web.  DOWNLOAD SPLUNK!
> > > > > http://ads.osdn.com/?ad_idv37&alloc_id=16865>
> > > > > > > > &op=3Dick
> > > > > >
> > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > >
> > > > > > > > Zd1211-devs mailing list Zd1...@li...
> > > > > > > > https://lists.sourceforge.net/lists/listinfo/zd> 1211-devs
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------
> > > > > This SF.net email is sponsored by: Splunk Inc. Do you
> > > grep through
> > > > > log files for problems?  Stop!  Download the new AJAX
> > > search engine
> > > > > that makes searching your log files as easy as surfing the  web.
> > > > > DOWNLOAD SPLUNK!
> > > http://ads.osdn.com/?ad_idv37&alloc_id=16865> > &op=3Dick
> > > > >
> > > > >
> > > _______________________________________________
> > > > >
> > > > > Zd1211-devs mailing list
> > > > > Zd1...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/zd> 1211-devs
> > > > >
> > > >
> > > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep
> > > through log files for problems?  Stop!  Download the new AJAX
> > > search engine that makes searching your log files as easy as
> > > surfing the  web.  DOWNLOAD SPLUNK!
> > > http://ads.osdn.com/?ad_idv37&alloc_id=16865> &op=3Dick
> > >
> > > _______________________________________________
> > >
> > > Zd1211-devs mailing list
> > > Zd1...@li...
> > > https://lists.sourceforge.net/lists/listinfo/zd> 1211-devs
> > >
> >
> >
>