Set SSID=hex doesn't work

Pongsak Tawankanjanachot egapongsak
Wed Apr 15 19:00:36 PDT 2009

   Thank you for suggestion.
   The reason I use BSSID instead of SSID is in the case that we would like
to fix this station with this BSSID no matter what SSID it is. Thus, I
cannot specify SSID name in the SSID parameter.
   I see the BSSID parameter too, but I am not sure on how to configure it.
I've tried several values, but it doesn't work. Here is one of my trial:

        ssid=001a4d2f872c        bssid=1

   The debug message still says that SSID mismatch.


On Fri, Apr 10, 2009 at 3:37 PM, Jouni Malinen <j at> wrote:

> On Thu, Apr 09, 2009 at 11:11:50AM +0700, Pongsak Tawankanjanachot wrote:
> >    As I read from the README, we can set the wpa_supplicant's parameter
> by
> > using hex string as SSID name. Here is my network block:
> > wpa_supplicant.conf
> > network={
> >         ssid="00:1a:4d:2f:87:2c"
> Are you sure that is the SSID that you want to use?
> > 0: 00:1a:4d:2f:87:2c ssid='TEST1' wpa_ie_len=0 rsn_ie_len=22 caps=0x411
> >    skip - SSID mismatch
> Based on the scan results, it looks more like the BSSID of the network,
> not the SSID (which is TEST1 in this AP). You can set the BSSID with the
> bssid option in the network block, but for a WPA network, you will also
> need to configure the SSID.
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Hostap mailing list