-
Notifications
You must be signed in to change notification settings - Fork 20
VmSetup
In order to have machines that can be attacked, we will provide each team with five VM's. For most teams, this is one VM per person. But you can use the VM's however is most convenient/effective for your team.
Accessing the VM's requires a little bit of setup.
First, you will need to setup VPN access to the MSSI lab. This access requires MSSI credentials, which all MSSI students should already have. If you are not an MSSI student, please contact Chris Venghaus to get access.
You will need to create a VPN connection. You can find instructions for how to do this here: https://wiki.isi.jhu.edu/index.php/VPN
If you get stuck with these instructions, please ask on Campuswire first. If nobody from the class can help you, please contact Chris Venghaus.
Each team has 5 VM's in a contiguous IP range:
- Team Esther (Z. Wang): 192.168.200.211-215
- Team Golden Nuggets (B. Wang): 192.168.200.216-220
- Team Kronos (S. Lee): 192.168.200.221-225
- Team Roast My Professor (A. Jadullah): 192.168.200.226-230
- Team Mewtwo: 192.168.200.231-235
- Team Captcha: 192.168.200.236-240
There are two accounts on all of these VM's: professor and student. For each group, the password for "student" is different. In other words, the password for the "student" is the same on machines .211 - .215, but different for all other machines. Each team captain should contact me for the password for your team.
Once you have access to your VM, you can administer them any way you want. You may remove my access (remove the professor account), create new accounts, change passwords, etc.
Following the existing instructions, you should setup Playground and at least one bank client. The Playground class switch will be located at 192.168.200.250 at port 9090. To connect to the class switch, you need to setup your playground pnetworking configuration slightly differently.
In your local tests, you have each had your own switch running. For the class projects, you will need to connect to the class switch. In order for your VNIC to know what to do, you will create a "dummy" switch in your pnetworking config that is a pointer to the remote switch. This is setup like so:
pnetworking add class_switch switch remote 192.168.200.250 9090
When you do pnetworking status, it will tell you that the class_switch
is "on". Because it is remote, your local configuration has no way of telling if it's on or off, so it always says it is on. Hopefully, that will always be the case! I'll let you know if it goes down.
The bank server (playground) address and port will be announced separately.