Operating instructions for Secure Video Demonstration
Server (Transmitter) instructions
The machine is booted in single-user mode. (Key is in service position during boot and option 5 is selected from the menu for single user mode.) The password for the transmitting machine at the microscope is the normal root password.
Run xinit to start an X environment.
The programs are in directory /tmp/.i2demo :
Verify that the ethernet address, broadcast address, and gateway address in the resetether script are correct before running it!
Verify that the destination address is correct in the runvic script before running it.
Starting transmission: Note: At this point several messages will appear in the window from which runvic was started. These messages are caused by the loopback code that is trying to display the video that it is sending. The video device is already opened for encoding and cannot be opened for decoding. You can ignore these messages.
The "rate control" within the Transmission section of the MENU should show 30fps and somewhere around 4.5Mbps (this will vary depending on the content of the video). Note that after a period of time, the bps number may go to zero, but the fps will stay at 30. This is a bug where they count total bytes sent and the number wraps. As long as the frame rate stays up, it’s still transmitting.
Starting an encrypted session The "key exchange" can be initiated by either the sender or the receiver. This has to be coordinated out-of-band… Initiating key exchange: Note: At this point several messages will appear in the window from which runvic was started. These are debug messages showing the key exchange information.
Accepting key exchange: The receiver will have selected the button to initiate secure session.
Receiver instructions The machine is booted in single-user mode. (Key is in service position during boot and option 5 is selected from the menu for single user mode.) The password for the transmitting machine at the microscope is the normal root password.
Run xinit to start an X environment.
The programs are in directory /tmp/.i2demo :
Verify that the ethernet address, broadcast address, and gateway address in the resetether script are correct before running it!
Verify that the destination address is correct in the runvic script before running it.
Starting reception:
When receiving the data, there should be a grey thumbnail window with source and rate information. It should (eventually) show 30fps and somewhere around 4.5Mbps (this will vary depending on the content of the video). Note that after a period of time, the bps number may go to zero, but the fps will stay at 30. This is a bug where they count total bytes sent and the number wraps. As long as the frame rate stays up and the video is still coming, it’s still receiving.
Problems Problem: The transmitter says it is sending at 30fps at some bandwidth, but the receiver is losing a large percentage of the data and getting very poor video. Solution: Quit vic on both sides, run the resetether script to reset the ethernet interface and try again. If the problem persists, reboot the transmitter machine. Don’t know why, but this has fixed it every time…
|