I want to set up a video chat between Hololens and PC using MR-WebRTC. I have a coTurn server configured to accept Stun/Turns. Everything is fine when I test on the LAN, but terrible on the WAN. The video captured by Hololens cards terribly in the PC when I test on the WAN. Transmitting a 331KB picture using MR-WebRTC on the WAN needs about 13s. I wonder how to figure out that if I have a successful NAT traversal and if NAT traversal is failed, MR-WebRTC would transmit data using a relay server or any other ways.
Hololens LocalVideo Webcam Source:
Capture format:manual
Width:1280
Height:720
Framerate:30
Environment:
Windows10
Hololens2
MixedReality-WebRTC2.0.2
Unity 2019.4.26fc1
Architecture:ARM
Related
I am trying to use WebRTC on an Android App to stream to a media server running on my workstation using a USB tethering connection. I see have good signaling, with an offer and an answer that seem to make sense with respect to the IP addresses, but I do not get any UDP streaming traffic.
Is there something in the Android WebRtc library that would omit this rndis0 interface? Over Wi-Fi, everything works as intended, but not if the tethered ethernet is the only connection.
After webrtc passes by a signaling server on Internet, how it works when two machines are running in the same network?
The data will be exchanged only on the network or will it still use internet ?
I am asking this because of our internet is not good, it's too slow. but our local network speed is very fast.. So I would like to know if the internet signal will affect the audio and video conversation.
Thanks a lot!
Depending on the network configuration, the devices should connect directly over the local network. Please note that some browsers, such as Safari, may not share with the signalling service local ICE Candidates unless configured to do so (false concern over sharing network info). The devices must share local ICE Candidates, or else they will still stream via the external network or a TURN server, if available.
I am currently working on internet of things technology, in one of my scenarios I want to connect raspberry pi2 through the mobile network.
Please tell me is there any possibility to connect with raspberry pi2 through the mobile network.
Regards,
Pradeep
You can connect your Pi2 to a mobile network using either a USB 3G Dongle or a 3G Shield.
You will have to play around with the setup though to see how it works for you.
If you want to access your Pi2 from elsewhere while connected to a mobile network you will also need to setup dynamic ip resolution for your Pi if you do not have a fixed ip assigned by your mobile operator.
If, however you want to connect from a mobile device to your Pi2 which is located on a LAN, you will need to configure port forwarding on your router for the Pi2 to receive communication from the outside world. Once again, if your router does not have a fixed ip supplied by your ISP, you will need to setup a dynamic ip resolution (DDNS).
Hope this helps.
I have a raspi 2 with a WiFi dongle and is setup to act as an access point/router. I also have 2 BeagleBone Blacks that also have WiFi dongles and they are connected to the raspi's network as well as a 9 axis sensor (accelerometer, gyro, etc). But I am unsure on how to send data from one board to another. And it has to be wirelessly.
If your RPi2 is configured as an access point, it must be running dhcpd on it. You will have to configure BBB to connect to RPi's wifi network and make use of some server client program (Could be in any language) to exchange the data. It should not be very difficult if you know what you're doing. I suggest you to break things in part and conquer, like
If you're able to ping Rpi from BBB and vice versa to check your both wifi configuration.
Once done, how about taking TCP server client code from web and test it to exchange simple strings.
and so on...
Hope it helps.
After having been studying a USB Packet Sniffer based around the BeagleBoard xM (https://gitorious.org/beagleboard-usbsniffer/), I have been at a loss as to how the driver actually works in a certain area.
I now understand that the BeagleBoard acts as a one port USB hub for the USB host to see, so that it may view and log the packets going through it. The part i'm trying to currently understand is how exactly the BeagleBoard is able to be somewhat transparent, and able to mimic the USB Vendor/Product ID's of the device being sniffed.
There is nothing to mimic. If it behaves as a hub, it can see all the traffic going between the computer and the device under test because all the USB packets would go through the hub. Packets are received by the hub and transmitted along to the other device.