Changeset 64187 in vbox for trunk/doc/manual
- Timestamp:
- Oct 10, 2016 1:20:32 PM (8 years ago)
- svn:sync-xref-src-repo-rev:
- 111175
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_AdvancedTopics.xml
r63892 r64187 4288 4288 </sect1> 4289 4289 4290 <sect1 id="usbip"> 4291 <title>Accessing USB devices exposed over the network with USB/IP</title> 4292 4293 <para>Starting with 5.1.0, VirtualBox supports passing through USB 4294 devices which are exposed over the network using the USB over IP protocol 4295 without needing to configure the client side provided by the kernel and 4296 usbip tools. Furthermore this also works with VirtualBox running on any 4297 supported host instead of just on Linux like it is the case with the official 4298 client. </para> 4299 4300 <para>To enable support for passing through USB/IP devices the device server exporting 4301 the devices must be added with the followig command: 4302 <screen>VBoxManage usbdevsource add "Unique name" --backend "USBIP" --address "Device server"[:port]</screen> 4303 USB devices exported on the device server are then accessile through the GUI 4304 or VBoxManage just like any USB device attached locally. This can be used multiple times 4305 to access different device servers.</para> 4306 4307 <para>To remove a device server the following command can be used: 4308 <screen>VBoxManage usbdevsource remove "Unique name"</screen> 4309 </para> 4310 4311 <sect2 id="usbip-setup-server"> 4312 <title>Setting up USB/IP support on a Linux system</title> 4313 4314 <para>This secton gives a brief overview on how to set up a Linux based system 4315 to act as a USB device server. The system on the server requires the 4316 <computeroutput>usbip-core.ko</computeroutput> and 4317 <computeroutput>usbip-host.ko</computeroutput> kernel drivers 4318 to be available and that the USB/IP tools package is installed. 4319 How to install the necessary tools depends on the used distribution, for 4320 Debian based systems the following command should install the required tools: 4321 <screen>apt-get install usbip-utils</screen></para> 4322 4323 <para>Checking whether the necessary tools are installed can be done with 4324 the following command which should produce a similar output like 4325 in the example below: 4326 <screen> 4327 $ usbip list -l 4328 - busid 4-2 (0bda:0301) 4329 Realtek Semiconductor Corp. : multicard reader (0bda:0301) 4330 4331 - busid 5-1 (046d:c52b) 4332 Logitech, Inc. : Unifying Receiver (046d:c52b) 4333 </screen></para> 4334 4335 <para>If everything is installed the USB/IP server needs to be started as 4336 <computeroutput>root</computeroutput> with the following command, 4337 consult the documentation of the used distribution on how to start the 4338 service when the system boots: 4339 <screen>usbipd -D</screen></para> 4340 4341 <para>By default no device on the server is exported which must be done manually 4342 for each device. To export a device use: <screen>usbip bind -b "bus identifier"</screen> 4343 To export the multicard reader from above for example use: 4344 <screen>usbip bind -b 4-2</screen></para> 4345 </sect2> 4346 4347 <sect2 id="usbip-security"> 4348 <title>Security considerations</title> 4349 4350 <para>The communiction between the server and client is not encrypted and 4351 there is no authorization required to access exported devices. An attacker 4352 might sniff sensitive data or gain control over a device. To mitigate this 4353 risk the device should be exposed over a local network only trusted 4354 clients have access to. To access the devie remotely over a public network 4355 a VPN solution should be used to add the required protection.</para> 4356 </sect2> 4357 </sect1> 4358 4290 4359 </chapter>
Note:
See TracChangeset
for help on using the changeset viewer.