-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Miracast over Infrastructure #12
Comments
I will look into it. It does seem like a attractive feature and may solve the issue of unreliable a/v transmission, but I want to figure out a way so we don't have to modify the existing codes too much. |
It would be great to have it. I'm thinking on converting our university DLPs into wireless ones using RPI3, but it would be easier to have them in common, infrastructure network, because if you use a laptop to connect to the DLP via WiFi, then you cannot connect parallel to another network i.e. to present on-line content. |
I actually tried to implement it some time ago. It seems like it should be as simple as adding a few WPS IE to Beacon and Probe Response frame. I tried |
I was thinking as temporary solution, to connect RPI using Ethernet to the
infrastructure and configure routing /Nat for WiFi AP. Then connect to the
WiFi both Miscast and regular. I just wonder, if it works, however.
…On Tue, 5 Mar 2019, 08:47 homeworkc, ***@***.***> wrote:
I actually tried to implement it some time ago. It seems like it should be
as simple as adding a few WPS IE to Beacon and Probe Response frame. I
tried wpa_cli VENDOR_ELEM_ADD but it seems that this has no effects on
the frames. Please let me know if anyone has figured out this problem.
(After that I discovered that Raspbian started to randomized MAC address
of the P2P interface on every reboot so I shifted my focus to that issue.
Again, let me know if anyone has any ideas.)
On the side note, wifi direct should allow concurrent connections. (That
is, the laptop should be able to connect to the Internet on one interface
while doing Miracast (on another "virtual" interface) simultaneously.) Even
in this extension, wifi direct is still mandatory for device discovery.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWoKxme0BePdyuL-zB79F8pZkmdarI92ks5vTiEugaJpZM4ZNUs->
.
|
any updates on this @homeworkc ! |
Not at the moment. The main issue here is to embed the information elements (IE) in beacon frames. |
Hello homeworkc, I like the home work you are doing! |
Thanks. |
As I said I can send files to you, that you can analyze with wireshark. I made a trace with Airserver and one with ScreenBeam. I have been sitting on one end of our school with 2 PCs. One sending Beacons generated with python and the other making the connection to Airserver situated on the other end of the building. I used scapy and was able to send the beacon. You can have of course have my sources but I think here is not the place to share files. |
Cool. Thanks for your help. I will send a private email to you if you want to send files or links. Currently I am able to send the beacon with all the required information so my focus right now is on the DNS part. According to the spec, we have to publish additional information (registering ._display._tcp.local and a TXT key-value pair) by DNS/mDNS on the sink (i.e., Pi). This information is exchanged on Ethernet and I think I have a rough idea of how to implement it. |
The MICE feature works in the latest commit. It still has lots of rough edges and more tests may be needed but it does provide better experience especially using Ethernet. |
You mention using specific IPs on both sides. I can get the Any specifics on this setup not mentioned in readme? |
Ended up getting it to work. Modified |
I'm following the mice guide, but it isn't clear to me whether I need to connect my desktop to pi via ethernet directly or pi to router via ethernet? I connected the pi to router via ethernet, assigned pi static IP and added it to |
For mice, it should work if the desktop and pi are connected. (Basically it should work as long as the desktop can successfully ping pi.) It can be a direct ethernet connection, or both connecting to the same router. (Ethernet or WiFi should not matter, although I think I read somewhere that mice will not try to use an open WiFi network.) |
Hi @homeworkc, any reason for using the |
If I remember correctly, the reason is that specifically for MICE, the IE has to be one of the WPS IEs. I think setting VendorExtension will make it a separate IE, which did not work with Windows. |
Thanks for the response @homeworkc, that helps. I was trying to map the WFDIEs set in |
A very useful feature would be Miracast over Infrastructure, which is supported under Windows 10 1703 and later. In companion with Chromecast-like GUI this feature would make lazycast a very useful solution even in semi-corporate networks. Please consider adding it in future releases.
The text was updated successfully, but these errors were encountered: