[FS#550] hostapd (wpad-mesh) fails to start interface at same time with meshpoint interface

[LEDE Bugs]

The following task has a new comment added:

FS#550 - hostapd (wpad-mesh) fails to start interface at same time with meshpoint interface
User who did this - Jeff Kletsky (jeffsf)

----------
Had to move the development to lede-17.01, but having initial success with the "latest" wpa_supplicant code. Mesh came up and the other stations connected successfully. AP looks good too!


phy#0
	Interface wlan0-1
		ifindex 98
		wdev 0x6
		addr 32:b5:c2:xx:xx:xx
		type AP
		txpower 0.00 dBm
	Interface wlan0
		ifindex 97
		wdev 0x5
		addr 30:b5:c2:yy:yy:yy
		type mesh point
		txpower 0.00 dBm


Thu Mar 15 20:46:27 2018 daemon.info hostapd: wlan0-1: STA  IEEE 802.11: authenticated
Thu Mar 15 20:46:27 2018 daemon.info hostapd: wlan0-1: STA  IEEE 802.11: associated (aid 1)
Thu Mar 15 20:46:27 2018 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED 
Thu Mar 15 20:46:27 2018 daemon.info hostapd: wlan0-1: STA  RADIUS: starting accounting session E1A5117BAEC56FE9
Thu Mar 15 20:46:27 2018 daemon.info hostapd: wlan0-1: STA  WPA: pairwise key handshake completed (RSN)

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=550#comment4481