Hide Assignment Information
Instructions
Instructions: 1- Individual and term-long activity. 2-This an experiential learning activity with focus on networking. 3- IT MUST BE HANDSON and extend the learnings from this courses. Topics must be in one of the following areas: ---- Network Analysis with Wireshark --- Network Configuration and Security with Packet Tracer --- Network Configuration and Security in Linux Server --- Network Configuration and Security in Windows Server ---- Network Programming with Python. 4- Regardless of the topic, screenshot must be taken for each and every step. For each screenshot, add your name and student number. For example, for the student Jose Roberto 123456, add the following Roberto_Jose_123456 should be included. 5. Report must be written using the attached template. It must be comprehensive report (30 pages minimum) and well-written since it is a term long activity 6-Report, which is attached, should be submitted in PDF extension, not in doc, docx, zipped, etc. Fail to comply with this instruction will result in 3.0 mark deduction. 7-There is no DUE DATE for the activity, but END DATE. In this respect, no penalty for late submission will be attracted, but after the END DATE no work will be accepted. Can i get 30 pages file on this topic ---- Network Analysis with Wireshark i just want to see how all work is done Lab - Part Description Write a description of what this part of the lab is supposed to achieve. Be specific. DO NOT copy and paste what is provided in the lab document unless instructed to do so. What you write here should prove to your professor that you understand what you are trying to accomplish and what tools you will be using. Preparation This section is optional unless otherwise specified. Writing down what you did to prepare is good practice. It can often be used to troubleshoot problems with the lab. If you decide to write something in this section, it must be your own work. Just because there are no marks does not mean you can copy work. Observations This section may be optional but highly recommended. You should be recording what you did, unless what you did was obvious. For example, if you entered a PowerShell command to complete some assigned task, this a great place to record that so you will know what you did in the future. If you received unexpected feedback once you did something, this is a great place to record that. If you clicked OK to dismiss a dialog page, you may wish to pass on recording that. Remember that this document should be a key study and comprehension tool. Although its challenging, its recommended to write enough so that you can understand what you did, but keep it brief enough that you dont get frustrated because youre trying to read every mouse click and keystroke executed. If you decide to write something in this section, it must be your own work. Just because there are no marks, does not mean you can copy work. If you include something that you typed, you may use the Path-Char style to distinguish that text. If you record one or a series of clicks, you may use the Select-Char style to distinguish that text. You may wish include a few of your own strategic screenshots. You should not include trivial screenshots that make it difficult to find the real useful information this is not meant to be a click-by-click record of what you did. For example, if you are saving a file and want to record the name and path, you should write that as a brief note rather than including a screenshot of the file save dialog. If you decide to include screenshots in addition to those required by the lab, do not mix them together. Screenshots Some labs will specify screenshots that must be included as part of the lab. Each should be easily readable without magnifying and should be clearly labeled to indicate what is in the screenshot is showing. This part of the lab proves that you did the work correctly. You must include enough information in the screenshot to prove it is your work. For example, if your screenshot includes commands, the command prompt may show via a hostname that this is your build. You may need to include part of a window or VM title bar to show you own the build. Reflection This component is mandatory unless otherwise specified. Labs will have a section per part labeled Reflection that may suggest what should be included at minimum, although you are certainly not limited to only the suggestions. The suggestions are there for guidance regarding what you should be writing about. This is where you get to demonstrate that you understood what you did and the outcomes from your work. You do not have to include pages of explanation. You should be able to provide a brief explanation in a couple of paragraphs. Using bullet points is encouraged. If you include something that you typed, you may use the Path-Char style to distinguish that text. If you record one or a series of clicks, you may use the Select-Char style to distinguish that text. References List any references to resources quoted or paraphrased that require citation. You may place references in line rather than in a references section if you wish. Whichever option you choose, ensure you are consistent.