deterlab
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| deterlab [2017/05/18 14:57] – [Setup] silvio.biagioni@unitn.it | deterlab [2021/01/29 10:58] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| ===== Requirements ===== | ===== Requirements ===== | ||
| - | This exercise requires basic OS and networking knowledge, understanding of Denial of Service (DoS) and buffer overflows. It also requires | + | This exercise requires basic OS and networking knowledge, understanding of Denial of Service (DoS) and buffer overflows. It also involves |
| ===== Setup ===== | ===== Setup ===== | ||
| Before the exercise you need to perform the following steps: | Before the exercise you need to perform the following steps: | ||
| - | - Create groups of students in your class project | + | - Create groups of students in your class project |
| + | - Swap in the experiment using the related NS file: <code bash> / | ||
| + | - For each topology created, remove access to the three //client// machines for all but their attack team, and remove access to //server// and //gateway// machine for all but the automated defense team. Remove also the access to //router// for all teams. These steps can be done by running the '' | ||
| + | exp1-attack-group exp1-defense-group exp2-attack-group exp2-defense-group </ | ||
| + | |||
| + | < | ||
| + | |||
| + | In this specific case, we declare in the first line the experiment ID, and the list of the respective attack and defense groups. Therefore, the experiment '' | ||
| + | |||
| + | <REPLY END: THE LAST STEP IS NOT CLEAR. WHICH IS THE SEMANTICS OF THE SECOND LINE?> | ||
| + | |||
| + | This step will ensure that during exercise team members cannot log into machines controlled by the opposing team and spy on them. | ||
deterlab.1495112256.txt.gz · Last modified: (external edit)
