doomedraven

just tested with cape.local instead of ip, and it works just fine here so i can't really help here

hello, just tested Beta ``` diec 6c512d9943a225d686b26fc832589e4c8bef7c4dd0a8bdfd557d5d27fe5bba0f [1] 2079703 segmentation fault (core dumped) diec -j 6c512d9943a225d686b26fc832589e4c8bef7c4dd0a8bdfd557d5d27fe5bba0f diec -v die 3.11 ```

diec and diec -j, both fails, you have example in my previous comment

Thank you, maybe there some issue on my side, I will investigate, we can close this. Thanks for fix

To prevent recursive errors on json reports, for some malware spawns a lot of processes, and we embed children into parent process

well sometime progress requires breaking changes, this rarely happens, but would be nice to handle this properly without loosing details, but yes quick fix i guess will be configurable limit,...

hello. can you start rooter by hand in verbose mode to verify that iptables? you need * `sudo systemctl stop cape-rooter` and then as cape user in poetry shell: `cd...

also did you configure netplan? https://capev2.readthedocs.io/en/latest/installation/host/routing.html#configuring-netplan

well to properly route traffic you need to configure netplan, just replace `enx00a0c6000000` with `ens18` and fix network ranges for your need thats all

Ens18 should be fine El vie, 25 abr 2025, 16:01, Vishwa Iyer ***@***.***> escribió: > *vishiswoz* left a comment (kevoreilly/CAPEv2#2571) > > > Do i need a management interface, ie...