ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Troubleshooting issues with the Dirty Line on Malware Analysis appliances


Article ID: 169020


Updated On:


Malware Analysis Software - MA


  • Noticed that the IVM uses the back end interface settings instead of dirty line for task processing
  • Running URL task processing for '' shows error in reaching to destination server
  • Have configured the dirty line but need to know if it is using the dirty line for task processing


  1. Make sure the Firewall configuration settings is set to Limited to both Active and URL submissions.
  2. Use eth1 for the interface name of dirty line interface and make sure to not change this setting to another interface.
  3. Confirm that there are no IVM profile that is being customized. If so, rebuild the profile.
  4. Make sure the default browser inside the IVM profile used for URL testing is not using proxy setting (proxy IP is in the same subnet with the back end IP).
  5. Ensure that the external Firewall/router is not blocking the dirty interface from reaching out to Internet.

Note that when configuring via System Settings / Network / Internet Settings, the dirty line will only be used when executing samples or URLs and the Firewall selected for the task is not the isolated firewall. It is very helpful to know your external IP address for both the dirty line and back end internet connections when running these tests.


For testing you should use a web page URL that will show you your external IP address.  This will both confirm connectivity and show you that the right internet connection is being used. To give you fast results without waiting time, do not send files to MAA via Security Analytics or the Content Analysis System or other automated methods.

This example uses for URL task processing:

  1. Monitoring the dirty line connection
Connect to the MA Appliance via SSH using the g2 user.
Run these commands:
$sudo -s
$tcpdump -vv -i -eth1 | grep -i ""
Leave the ssh terminal open.
  1. Create the new URL task
i. Be sure to select the pre-configured "limited" firewall on the "basic" tab.
ii. Watch the tcpdump output in the ssh terminal. It should look like this:

[email protected]:~# tcpdump -vv -i eth1 | grep -i ""
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes > [udp sum ok] 42001+ A? (36) > [udp sum ok] 42001 q: A? 4/0/0 CNAME, A, A, A (116)
iii. When the task is complete, abort tcpdump using CTRL+C.
iv.. Check the task report. It should contain a screenshot with the external IP address.
v. If not getting the expected output, recheck the points provided in this solutions.
  1. Support information:
Please provide the support package from https://<MAA IP>/support