Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

missing br0 #191

Open
ElMilos opened this issue Dec 21, 2024 · 2 comments
Open

missing br0 #191

ElMilos opened this issue Dec 21, 2024 · 2 comments
Assignees

Comments

@ElMilos
Copy link

ElMilos commented Dec 21, 2024

I powered off then on my VM with ubuntu then I tired to start cuckoo using comande "cuckoo" the answer was

2024-12-21 23:18:12 INFO [cuckoo.startup]: Starting Cuckoo. cwd=/home/cuckoo/.cuckoocwd
2024-12-21 23:18:12 INFO [cuckoo.startup]: Loading configurations
2024-12-21 23:18:12 ERROR [cuckoo.common.log]: Failure during Cuckoo startup: Failed to load config file /home/cuckoo/.cuckoocwd/conf/machineries/qemu.yaml. Error in config file: /home/cuckoo/.cuckoocwd/conf/machineries/qemu.yaml. Constraint violation for key interface: Network interface 'br0' does not exist.
Stopping Cuckoo..
Failure during Cuckoo startup: Failed to load config file /home/cuckoo/.cuckoocwd/conf/machineries/qemu.yaml. Error in config file: /home/cuckoo/.cuckoocwd/conf/machineries/qemu.yaml. Constraint violation for key interface: Network interface 'br0' does not exist.

And when I checked the br0 it was not there.

Is this normal should I set up the br0 every time i power VM and cuckoo or I missed some steps while installing?

Ps. I used quickstart for instalation and have ubuntu 8GB ram 3 core 150 GB storage 22.04 on VMware workstation

@ElMilos
Copy link
Author

ElMilos commented Dec 22, 2024

Also if could you give me an adivce how to use WEB API.

It's working on ubuntu VM allright.

The problem I'm faceing is trying to use the WEB API commands for example "/submit/browsers" through my main system which is windows 10, using Global routing with changes in VM IP mine is 192.168.1.16 and br0 mine is 192.168.30.1 but can't get it to work.

my tries looks like this:

sudo iptables -t nat -A POSTROUTING -o ens33 -s 192.168.30.0/24 -j MASQUERADE
sudo iptables -P FORWARD DROP
sudo iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -A FORWARD -s 192.168.30.0/24 -j ACCEPT
sudo iptables -A FORWARD -s 192.168.30.0/24 -d 192.168.30.0/24 -j ACCEPT

echo 1 | sudo tee -a /proc/sys/net/ipv4/ip_forward

Update: I am currently able to ping through windows 10 console the VM and br0 but trying to use Any WEB API meets with
curl: (7) Failed to connect to x.x.x.x port 8090 after 2039 ms: Could not connect to server
the IP i used are 127.0.01 // 192,168.1.16 // 192.168.30.1

Update-2: Ok I managed to make it work I needed to set the Api serwer (cuckoo Api) on my VM IP
What I come up with was I probably re-created the br0 wrong way

@triinsa
Copy link

triinsa commented Dec 30, 2024

@ElMilos Thank you for reporting the issue.
First br0, yes you should always bring up bridge after you restart your VM.
The user with sudo privilages in VM, who installed the Cuckoo with quickstart, should see in home files file named helper_script.sh and should run it every time after VM is restarted or shut down. After that it's possible to run Cuckoo.
PS! We will add more documentation to further explain how to bring up the bridge after a restart.
Thank you for bringing up WEB API problem and good job fixing it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants