Setting vendor specific extensions via wpa_supplicant

Vincent Keller v.keller.86 at gmail.com
Thu Jun 28 09:21:41 PDT 2018


Hello,

I am attempting to add additional vendor extensions to WPS vendor
specific P2P packets, but can't seem to figure out how to do it
correctly with wpa_supplicant.

I have attempted to use the 'ap_vendor_elements' keyword in the
wpa_supplicant.conf file, but that doesn't seem to have any effect.

An example of how I used this keyword follows:

ap_vendor_elements=dd2c0050f2041049002400013720010001052002000776446576506f642005000d3139322e3136382e332e313232

A breakdown of the packet meaning is:

dd          // Element ID
2c          // Length:
00 50 f2    // OUI (Microsoft)
04          // OUT Type (WPS)

10 49       // WSCVEA
00 24       // Length: 36
00 01 37    // OUI: WPS

20 01       // P2PATTR: Capability Attribute
00 01       // Length: 1 byte
05          // 00000101

20 02       // P2PATTR: Host Name Attribute
00 07       // Length: 7
76 44 65 76 50 6f 64 // vDevPod

20 05       // P2PATTR: IP Address Issue
00 0d       // Length: 13
31 39 32 2e 31 36 38 2e 33 2e 31 32 32    // 192.168.3.122


I have also notice a 'vendor' command available in wpa_cli, but can't
find documentation for how to use it. My wifi driver is nl80211.

One more data point is that, in other implementations that emit
packets like this, I am only seeing the additional vendor extensions
in beacon packets, not probe requests or probe responses. When I do a
packet capture on my device, I never see any beacon packets. Is there
a way to enable beacons, or some condition that must be satisfied for
beacon packets to be broadcasted? It is possible that the vendor
extension is working but it would only be show in the beacon packet.

Any feedback would be much appreciated!

Thanks,
Vincent



More information about the Hostap mailing list