windows 10 LAN lsl fail

Question

windows 10 LAN lsl fail

dmedine opened this issue 6 years ago · comments

David Medine · Answer 1 · Sun Nov 18 2018 11:43:07 GMT+0800 (China Standard Time)

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?

Matthew Grivich · Answer 2 · Sun Nov 18 2018 12:03:30 GMT+0800 (China Standard Time)

Have you turned off all the firewalls? Are you using the standard SendString, ReceiveString examples? Are you on a wired network?

Matthew Grivich · Answer 3 · Sun Nov 18 2018 12:04:23 GMT+0800 (China Standard Time)

P.S. I generally use windows 10<-> Ubuntu these days for LSL stuff.

David Medine · Answer 4 · Sun Nov 18 2018 19:15:11 GMT+0800 (China Standard Time)

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>.

Tristan Stenner · Answer 5 · Sun Nov 18 2018 22:45:11 GMT+0800 (China Standard Time)

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

Matthew Grivich · Answer 6 · Sun Nov 18 2018 22:51:32 GMT+0800 (China Standard Time)

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>.

Tristan Stenner · Answer 7 · Mon Nov 19 2018 23:01:36 GMT+0800 (China Standard Time)

I've uploaded the example apps with some debug messages enabled http://trstan.stennr.de/Chatty_examples_for_David.7z
You can redirect the output by adding > outputfile.txt from the command line, e.g. SendDataC.exe > senderlog.txt.