I've added a tcpdump container that could be used to keep all the configuration required for Tulip in the same place. Of course for some CTFs this won't be useful in which case the container shuts down. The main scenario you would use this in is if you're running Tulip on the same server as the vulnbox.
It exposes the PCAP data using PCAP-Over-IP on port 11337 on the host. It exposes on the host network but there should be no risk once the assembler has connected. It should be possible to bind it to localhost only but idk how exactly to do that (I think using netcat on 127.0.0.1 in the container would bind to localhost within the container not the host?).
The tcpdump command can be modified from the env. The example command is probably imperfect maybe others can provide suggestions.
I've added a tcpdump container that could be used to keep all the configuration required for Tulip in the same place. Of course for some CTFs this won't be useful in which case the container shuts down. The main scenario you would use this in is if you're running Tulip on the same server as the vulnbox.
It exposes the PCAP data using PCAP-Over-IP on port 11337 on the host. It exposes on the host network but there should be no risk once the assembler has connected. It should be possible to bind it to localhost only but idk how exactly to do that (I think using netcat on 127.0.0.1 in the container would bind to localhost within the container not the host?).
The tcpdump command can be modified from the env. The example command is probably imperfect maybe others can provide suggestions.