You may want to use your virtual device with a proxy program such as Charles or Burp. Setting up a proxy on a virtual device is very similar to the process for setting up a physical device.
Be sure to check out our video demo on integrating devices with Burp Suite here:
Intercepting HTTP and HTTPS Network Traffic
The simplest way to proxy HTTP and HTTPS traffic is to configure an APN proxy.
APN proxies are configured in the Settings application. It's slightly different across Android versions.
On Android 7, click
Wireless & networks > More > Cellular networks > Access Point Names
On Android 8, 9, 10, and 11, click
Network & Internet > Mobile network > Advanced > Access Point Names
Edit the currently active APN. Set the Proxy and Port fields. The Proxy field should be an IP address, routable from the VM.
Save the configuration and exit. All VM HTTP and HTTPS network traffic will now be routed through the APN proxy.
For iOS devices, follow these steps to set up your device proxy:
Launch your proxy program and set up your project. You will need the appropriate Port number (such as 8080).
If you are using the cloud product, ensure you are connected to the appropriate VPN profile.
You will need to identify the Server address, or the IP address assigned to the virtual device. On-site users can find the device's Wi-Fi address in the Access Details bar of the Device page. Cloud users can identify the IP by looking in the VPN details or by running ifconfig and looking for the IP starting with 10.*.
On the virtual device, launch the Settings app. Go to Wi-Fi, and connect to the Corellium network.
Once connected, next to the Corellium network name, click the (i) button.
Select Proxy -> Manual.
Enter the Server address and Port identified in the previous steps. A common example might be server 10.11.3.2 on port 8080.
Save these settings, and your proxy is ready to go!
If you have set up your proxy and are not able to see traffic, try closing and restarting your VPN session. Ensure that you are able to ping the IP address from the virtual device console.
Remember, you may not be able to reach HTTPS websites without proper trust certificates installed.
If the issue still persists, contact your network administrator to determine if any local network configurations may be blocking or interfering with the virtual device network.