diff --git a/Starting-access-point-hangs!.md b/Starting-access-point-hangs!.md
index e67decf..eef2fb2 100644
--- a/Starting-access-point-hangs!.md
+++ b/Starting-access-point-hangs!.md
@@ -1,9 +1,11 @@
-Before checking for master mode manually, try running fluxion with the process killer flag:
+### About This Issue
+The access point service hangs when a problem occurs with the wireless interface preventing the start of the AP service chosen. Before checking if your wireless device supports master mode with the linux drivers, try running fluxion with the process killer flag to make sure it isn't a process interfering with the interface selected:
 ```
 export FLUXIONWIKillProcesses=1; ./fluxion.sh
 ```
-If this does not work, continue reading, otherwise you're good to go.
+If you continue to have the issue after the step above, continue reading.
 
+### Verifying Master Mode
 To verify your driver supports master mode with hostpad, try the following.<br>
 Pick an interface you'd like to use and switch it to monitor mode:
 ```
@@ -47,4 +49,52 @@ If this looks fine, check with another device (like a phone/tablet) if a new AP
 The AP will not have any routes, but it should spawn and you should see it available.<br>
 <br>
 If all the steps succeeded and you're able to see a new wireless network, your driver supports master mode with hostapd.<br>
-To kill hostapd, simply do ctrl+c.
\ No newline at end of file
+To kill hostapd, simply do ctrl+c.
+
+
+### Verify Virtual Interface Functionality
+Fluxion requires virtual networking interfaces **when utilizing a single interface.** This is due to the fact some attacks, such as the `Captive Portal` attack, require two different wireless actions to succeed, such as `Captive Portal` requiring a jammer for the target AP and an access point for the rogue AP.
+
+The objective here is to utilize a single physical device with two virtual interfaces. For this we need to create a secondary interface from our main interface. First we need to select an interface we would like to work with and "reserve it" by setting it into monitor mode:
+```
+ip link set wlanX down # Deactivate interface
+iwconfig wlanX mode monitor # Switch interface to monitor mode (revert by switching to "managed" mode)
+ip link set wlanX up # Activate interface
+```
+The command(s) in the block above **should not generate any type of output**, if any output is shown chances are something went wrong.
+
+Next, we need to add the secondary virtual interface from the primary interface:
+```
+iw dev wlanX interface add wlanY type monitor
+```
+The command(s) in the block above **should not generate any type of output**, if any output is shown chances are something went wrong.
+
+Both interfaces should be ready at this point, so now we'll attempt to use them simultaneously.
+
+The primary interface, wlanX, will run the jammer, while the secondary interface, wlanY, will run the rogue AP. **Make sure you're running the jammer legally, follow your local laws and don't be an asshole.** For this part, **you'll need the channel set in the configuration file for hostapd created above.** Create a file with the target's MAC address, not the rogue network's MAC address:
+```
+XX:XX:XX:XX:XX:XX
+```
+Save it as target.lst in your desktop.
+
+Modify the hostapd configuration file created in the hostapd section to update the interface
+```
+interface=wlanY
+driver=nl80211
+ssid=TestAP
+channel=1
+```
+Save it on your desktop as hostapd.conf.
+
+Start the mdk3 deauthenticator on the primary interface:
+```
+mdk3 wlanX d -c TARGET_CHANNEL_HERE -b ~/Desktop/target.lst
+```
+This will start mdk3 in deauthentication test mode.
+
+On another terminal, start hostapd on the secondary interface:
+```
+hostapd ~/Desktop/hostapd.conf
+```
+If everything succeeded, you should see mdk3 and hostapd running and working without stopping.
+If everything succeeded, fluxion should work fine.
\ No newline at end of file