CloudShark can listen to its IPv6 address by making a small, one-time change to a configuration file. Edit the file /var/www/cloudshark/shared/config/nginx-network.conf. This file is not upgraded by the CloudShark installer, so it will persist between CloudShark upgrades. The file’s default value for IPv4 only is:
Change this file to contain:
listen 80; listen [::]:80;
If you have a listen directive in your nginx-ssl.conf file for an SSL instance of CloudShark and you want it to be available over IPv6 and IPv4, you must include a directive for each:
listen [::]:443 ssl; listen 443 ssl;
The file then includes your ssl_certificate and ssl_certificate_key directives as usual.
And then restart your CloudShark Appliance. CloudShark will bind to any non-link-local addresses that are assigned to the system.
At the end of this article there is a bash script that aggregates everything mentioned in this article, if you prefer to just see a script.
How to Set up a Proxy
CloudShark can be installed from behind either an HTTP proxy or a SOCKS proxy. The
initial installation uses the
curl command behind the scenes to install the
CloudShark software. Curl needs to be configured before you begin the
CloudShark is always installed by the
Create the file
/root/.curlrc and add a single line:
proxy = http://proxy.lan
The configuration is slightly different for a SOCKS proxy depending on if you are installing from CentOS 6 or CentOS 7:
# centos 7 proxy = socks5://proxy.lan:1080
To use an authenticated proxy, simply include the user credentials in the proxy
URLs for either step:
Proxy support for import by URL
CloudShark has the ability to import capture files given a URL. The file transfer is handled on the server side, so if a proxy is required, you may also need to set up proxy support for that feature.
These same proxy options should be added to the
/home/cloudshark/.curlrc file as described
by the Custom curl options page.