Bringing up VirtualBox interface before starting Cuckoo

Posted on August 27, 2014 in Tools • 1 min read

I am getting older and I need to write down commands I use rarely.

Cuckoo sandbox expects to found all network interfaces configured in its configuration file up when you start it.

If you configured Cuckoo to bind on, for example, VirtualBox virtual interface although it is not up and working, Cuckoo will raise an error to tell you it cannot operate with an interface down.

Cuckoo Sandbox 1.2-dev
Copyright (c) 2010-2014

2014-08-24 00:21:33,713 [root] CRITICAL: CuckooCriticalError: Unable to bind ResultServer on [Errno 99] Cannot assign requested address

The “Unable to bind ResultServer” error means that Cuckoo was unable to bind the component used to fetch analysis’ logs, it happens because your virtual interface is down or missing.

To fix you have only to bring up your (virtual) interface. You should create the virtual networking device and configure it.

With VirtualBox you have two ways to get a virtual interface up. The quick and dirty one: just start and stop your virtual machine. The cleanest, use the following commands to create the virtual network interface and configure it:

# VBoxManage hostonlyif create
# ip link set vboxnet0 up
# ip addr add dev vboxnet0

The first command tells VirtualBox to bring up an host-only vboxnet interface, the rest is used to configure it.

Happy analysis!