I think, the string command interface is good the only thing is that if command parameters are documented that would be great help. I wrote a vapsh - virtual AP Shell to execute the string command via control interface.You can find that in this link - https://github.com/naushada/vapsh This is not yet completed. -Naushad On Thu, Oct 31, 2019 at 12:30 AM <hostap-request@xxxxxxxxxxxxxxxxxxx> wrote: > > Send Hostap mailing list submissions to > hostap@xxxxxxxxxxxxxxxxxxx > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.infradead.org/mailman/listinfo/hostap > or, via email, send a message with subject or body 'help' to > hostap-request@xxxxxxxxxxxxxxxxxxx > > You can reach the person managing the list at > hostap-owner@xxxxxxxxxxxxxxxxxxx > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Hostap digest..." > > > Today's Topics: > > 1. Re: socket interface (Andrej Shadura) > 2. RE: [EXTERNAL] Re: socket interface (Gladish, Jacob) > 3. Error occur when setting P2P_Device Interface for RPI (Rohith K D) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 30 Oct 2019 12:29:37 +0100 > From: Andrej Shadura <andrew@xxxxxxxxxx> > To: Jacob Gladish <Jacob_Gladish@xxxxxxxxxxx> > Cc: "hostap@xxxxxxxxxxxxxxxxxxx" <hostap@xxxxxxxxxxxxxxxxxxx> > Subject: Re: socket interface > Message-ID: > <CACujMDOzaf=u65aykR1dwdscoRvgCTF4kFsgQe8p2NA6wLFCKw@xxxxxxxxxxxxxx> > Content-Type: text/plain; charset="UTF-8" > > Hi Jacob, > > On Tue, 29 Oct 2019 at 17:04, Gladish, Jacob <Jacob_Gladish@xxxxxxxxxxx> wrote: > > I was curious what people's thoughts were regarding the current wpa_supplicant/hostapd domain socket interface. It seems to me that it was built primarily to support cli interaction which sends/receives strings. I'm not a big fan of that approach. > > > > I have been thinking that it would be better if both wpa_supplicant and hostapd supported a more structured command/control interface that made it easier to write code against. This could be something like onc/rpc or something more modern that would work easily with multiple programming languages. > > > > If this is something that people think is valuable? I'd like to discuss some approaches to doing this and then start hacking. > > I believe both wpa_supplicant and hostapd support D-Bus, which may be > just what you?re looking for. > > -- > Cheers, > Andrej > > > > ------------------------------ > > Message: 2 > Date: Wed, 30 Oct 2019 13:56:52 +0000 > From: "Gladish, Jacob" <Jacob_Gladish@xxxxxxxxxxx> > To: Andrej Shadura <andrew@xxxxxxxxxx> > Cc: "hostap@xxxxxxxxxxxxxxxxxxx" <hostap@xxxxxxxxxxxxxxxxxxx> > Subject: RE: [EXTERNAL] Re: socket interface > Message-ID: > <DM6PR11MB3660CF81A52DBFAE567380AAD0600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> > > Content-Type: text/plain; charset="utf-8" > > The d-bus does look like what I'm talking about. My problem is that we're operating on devices that don't run d-bus. > > -----Original Message----- > From: Andrej Shadura <andrew@xxxxxxxxxx> > Sent: Wednesday, October 30, 2019 7:30 AM > To: Gladish, Jacob <Jacob_Gladish@xxxxxxxxxxxxxxxxx> > Cc: hostap@xxxxxxxxxxxxxxxxxxx > Subject: [EXTERNAL] Re: socket interface > > Hi Jacob, > > On Tue, 29 Oct 2019 at 17:04, Gladish, Jacob <Jacob_Gladish@xxxxxxxxxxx> wrote: > > I was curious what people's thoughts were regarding the current wpa_supplicant/hostapd domain socket interface. It seems to me that it was built primarily to support cli interaction which sends/receives strings. I'm not a big fan of that approach. > > > > I have been thinking that it would be better if both wpa_supplicant and hostapd supported a more structured command/control interface that made it easier to write code against. This could be something like onc/rpc or something more modern that would work easily with multiple programming languages. > > > > If this is something that people think is valuable? I'd like to discuss some approaches to doing this and then start hacking. > > I believe both wpa_supplicant and hostapd support D-Bus, which may be just what you?re looking for. > > -- > Cheers, > Andrej > > ------------------------------ > > Message: 3 > Date: Wed, 30 Oct 2019 15:59:16 +0000 > From: Rohith K D <rohith.k@xxxxxxxxxxxxxxx> > To: "hostap@xxxxxxxxxxxxxxxxxxx" <hostap@xxxxxxxxxxxxxxxxxxx> > Subject: Error occur when setting P2P_Device Interface for RPI > Message-ID: > <SG2PR04MB3495F5533CC79BF16338791ADF600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> > > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > I was just trying to get my RPI 3B+ to run wpa_supplicant on latest version. However I am getting error on wpa_supplicant on startup. My RPI creates two interfaces on running wpa_supplicant. They are wlan0 and p2p-dev-wlan0. > > For me on creation of p2p interface an error message is shown on enabling debug. "Failed to set interface 0 to mode 10: -22 (invalid argument)". Please note that my supplicant continues to work normally even though this error message is thrown. My RPI in its capabilities mentions that it support P2P. My kernel is 4.14.98. Is this error due to any driver level missing implementation or do we have the root cause on the user space of supplicant? > > Rohith > ________________________________ > Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version. > ________________________________ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Hostap mailing list > Hostap@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/hostap > > > ------------------------------ > > End of Hostap Digest, Vol 49, Issue 34 > ************************************** _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
