We have cases in which we need to connect Reach directly to the ethernet port. I am having huge problems to do that. Have been able to see the virtual ethernet-connection in Windows 10 when connecting with USB-cable, but that just is not enought. So the setup would be:
Reach -> usb-otg-cable -> usb-ethernet-adapter -> network switch (different IP space than 192.168.2.1/24). Reach should be available through the network as a TCP server. in One network we are actually having 7 reach-modules.
Does anyone have any ideas about the approach? I have read some previous posts about somewhat similar problems but didn´t come any smarter.
Hoping for quick replies as we are in great hurry!
Doesn´t too any good. I can connect Reach to PC with usb-virtual ethernet and get it work like an ethernet connection towards reach. But what I can´t do, is to get Reach to connect LAN via ethernet.
Reach act as an ethernet adapter FOR MY PC. I would need Reach to use it´s ethernet capabilities to communicate to LAN.
You need to make brigde connection between the reach network adapter and the lan network adapter you have under network settings in windows.
I think there was i discussion whether connecting reach directly to Lan is ok or not.
That would be good idea if i had any computers in the machine that the reach is supposed to be
Thing is, that the wireless network is running @ 60Ghz. 2.4G is not an option. Only thing that seems reasonable would be to connect reach directly to the network switch right next to it. Why is it so damn hard to do?