Updated Networking (markdown)

Networking.md

@@ -5,14 +5,47 @@ QEMU's robust networking support infrastructure, provides a flexible array of
 advanced network configuration options. There are two network backends exposed
 in the Network configuration window for xemu:
 
-- **User (NAT)**: In this networking mode, a full TCP/IP stack is running within
+- **NAT**: In this networking mode, a full TCP/IP stack is running within
   xemu, and network address translation is used to route packets between the
   internal network and the outside world.
-- **Socket**: In this networking mode, all traffic that would be sent/recieved by
+- **UDP Tunnel**: In this networking mode, all traffic that would be sent/received by
   the emulated NIC is simply encapsulated in UDP datagrams and forwarded to a
   remote host, which could be another instance of xemu or perhaps a real Xbox
   (see [l2tunnel](github.com/mborgerson/l2tunnel) for more information). This
   is useful for quickly setting up a virtual LAN.
+- **Bridged Adapter**: In this networking mode, the emulated NIC is bridged
+  to one of the network interfaces on your machine. This means that all traffic
+  sent/received by xemu will be sent directly to this network interface. With
+  this mode you can easily set up a System Link session with a real Xbox by
+  just connecting the Xbox to your computer with an Ethernet cable.
+  Additionally, this mode can be used to connect with tunneling services.
+
+Troubleshooting
+---------------
+
+### Bridged Adapter Permission Problems
+
+**Important:** You should **never** need to run xemu as the `root` user.
+
+#### Linux
+
+If you get a permission error when attempting to enable Bridged Adapter,
+you may need to update the executable capabilities to provide raw access
+to your network interface. You can do so with the following command:
+
+```bash
+sudo setcap cap_net_raw,cap_net_admin=eip `which xemu`
+```
+
+#### macOS
+
+If you get a permission error when attempting to enable Bridged Adapter,
+you may need to update the `/dev/bpfX` permissions on your system. You can
+work around this by opening a terminal and executing the following command:
+
+```bash
+sudo chown $(whoami):admin /dev/bpf*
+```
 
 Tips
 ----