Difference between revisions of "Using Scream over LAN"

From Looking Glass
Jump to navigation Jump to search
Line 33: Line 33:
 
Usage: ./scream-pulse [-u] [-p <port>] [-i <iface>] [-g <group>]
 
Usage: ./scream-pulse [-u] [-p <port>] [-i <iface>] [-g <group>]
  
         All commands
+
         All command line options are optional. Default is to use
 +
        multicast with group address 239.255.77.77, port 4010.
 +
 
 +
        -u
 
</syntaxhighlight>
 
</syntaxhighlight>
 
However confirming that Scream is running on the Windows Guest it can be ran by simply pointing it to the Bridge accociated with the VM. Ex:<code>./scream-pulse -i bridge0</code>
 
However confirming that Scream is running on the Windows Guest it can be ran by simply pointing it to the Bridge accociated with the VM. Ex:<code>./scream-pulse -i bridge0</code>

Revision as of 12:10, 26 February 2020

Introduction

In the event your Windows Guest does not require network isolation by traversing NAT (for security purposes) using Scream over a VirtIO Bridge will yield a overall better experience to using the IVSHMEM drivers. Setup is also simpler.

Prerequisites & Dependencies

Before setup can begin there are a few requirements.

Prerequisites

  • The Guest needs to have a VirtIO Network Adapter installed. This includes:
    • Creating a Bridged Network Adapter on the Host
    • Passing the Bridged Network Adapter to the Guest
    • Installing the VirtIO drivers on the Guest.

Dependencies

  • We also require a few packages:
    • git
    • libpulse-dev (May already be installed.)
    • make (Will already be installed if you've setup Looking Glass)

Setup

For the most basic configuration Scream over LAN does not have much setup to it.

Installing Scream on the Windows Guest

How to Install Scream on the Windows Guest has already been covered.

Installing Scream on the GNU/Linux Host

  1. Start by downloading Scream from the Github repository. git clone https://github.com/duncanthrax/scream.git
  2. Now navigate to the scream/Receivers/pulseaudio directory and run make.
  3. Scream over LAN is now ready to use.

Running Scream

Scream only uses a small number of arguments to operate which can be viewed by running ./scream-pulse -h:

Usage: ./scream-pulse [-u] [-p <port>] [-i <iface>] [-g <group>]

         All command line options are optional. Default is to use
         multicast with group address 239.255.77.77, port 4010.

         -u

However confirming that Scream is running on the Windows Guest it can be ran by simply pointing it to the Bridge accociated with the VM. Ex:./scream-pulse -i bridge0