-
Notifications
You must be signed in to change notification settings - Fork 132
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
windows 10 LAN lsl fail #360
Comments
I am having trouble getting LSL to do 2 way communication on windows 10 LANs. I had this problem before, and deleting all the virtual hyper ethernet adapters fixed it, but not this time. Basically I have two pcs connected directly, they can ping each other, but I can only send LSL streams 1 way, from my Windows 10 to the other pc which is running Windows 7. I understood this to be an issue having to do with LSL not being able to handle multiple network adapters, but now there is only 1 and the bloody thing still won't go. Anyone know about this? |
Have you turned off all the firewalls? Are you using the standard SendString, ReceiveString examples? Are you on a wired network? |
P.S. I generally use windows 10<-> Ubuntu these days for LSL stuff. |
Wired. Firewalls disabled. PCs can ping each other. LSL goes out of
Windows 10 to Windows , but not vice versa. Like I said, I've
encountered this before, but disabling the virtual network adapters
solved it.
…On 18.11.2018 05:04, Matthew Grivich wrote:
P.S. I generally use windows 10<-> Ubuntu these days for LSL stuff.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/sccn/labstreaminglayer/issues/360#issuecomment-439666127>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADch7mQMhmW0Ke8wDFew3fkT-uMYP50Kks5uwNxHgaJpZM4Ynwx7>.
|
I can send you a work in progress build with some more debug logging, so far I haven't been able to reproduce that issue reliably so maybe Windows 10 being always broken can help thete |
You should try updating to the latest liblsl (build from source) on both
endpoints.
Also try turning off ipv6 on both endpoints. I fixed one issue with
ipv6, but I'm not convinced that I fixed them all.
…On 11/18/2018 3:15 AM, David Medine wrote:
Wired. Firewalls disabled. PCs can ping each other. LSL goes out of
Windows 10 to Windows , but not vice versa. Like I said, I've
encountered this before, but disabling the virtual network adapters
solved it.
On 18.11.2018 05:04, Matthew Grivich wrote:
>
> P.S. I generally use windows 10<-> Ubuntu these days for LSL stuff.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
>
<https://github.com/sccn/labstreaminglayer/issues/360#issuecomment-439666127>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/ADch7mQMhmW0Ke8wDFew3fkT-uMYP50Kks5uwNxHgaJpZM4Ynwx7>.
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/sccn/labstreaminglayer/issues/360#issuecomment-439684884>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFC33f57EaUzuKN2ZIhPp-5zQ2U47JCWks5uwUFBgaJpZM4Ynwx7>.
|
I've uploaded the example apps with some debug messages enabled http://trstan.stennr.de/Chatty_examples_for_David.7z |
No description provided.
The text was updated successfully, but these errors were encountered: