search

mfthomps / Labtainers

Labtainers: A Docker-based cyber lab framework
https://nps.edu/web/c3o/labtainers
263 stars 66 forks source link

TCP/IP lab issues #29

Open mfthomps opened 4 years ago

mfthomps commented 4 years ago

The syn flood attack is not feasible in some environments. Consider revising lab manual to reflect this, and to simply highlight the observation of the backlog. The "reverse shell" goal tests for a specific string. Either direct the student to cat such a file, or simply test for the server name in the shell prompt.

enck commented 2 years ago

I'm also having issues with the TCP RST attack. nping thinks it is setting the sequence number correctly, but when running wireshark from the main shell in the VM (not from a container), the sequence number of the sent RST packet is something very different. My guess is that this is a limitation of the container environment. Maybe additional POSIX capabilities need to be given to the containers?

mfthomps commented 2 years ago

In your main VM wireshark, did you set the protocol preference to uncheck relative sequence numbers? I see the same sequence numbers in both wiresharks when that is done.

ayok007 commented 10 months ago

i had the same issue of sequence number ( relative seq num), but when i used raw seq number it was working well.