4 of 768 articles shown, currently no other people reading this forum.
||Sat 6th Jun, 9:28pm
Hope you are doing well.
Having started revising for the exam, I've come to the realisation that covering
every single topic in the lecture slides is a Sisyphean task.
Could you perhaps suggest areas of greater importance, or strategies for studying?
||Sun 7th Jun, 7:36am
> Having started revising for the exam, I've come to the realisation that covering
> every single topic in the lecture slides is a Sisyphean task.
> Could you perhaps suggest areas of greater importance, or strategies for studying?
What you want me to say, and what is the truth, and likely quite different.
Are you now revising, or studying it for the first time?
It's clear that many pushed out their project submission, perhaps, without keeping an eye on
their exam calendar.
The material to study, and the material to be examined, is all listed on our unit Schedule
page, 11 weeks, clearly the first week is very introductory, and roughly 5 points highlighted
each week (which may not correspond directly to the titles on slides).
All of it is equally important, maybe Internetworking more important than Data
Communications, but questions will come from both areas. For example, even though there's no
detailed coding required in the exam, don't give up on the Labsheet exercises. Ask yourself
*why* a particular question on a labsheet was set, what you should have learnt when you
completed the exercise. Reflect on this stuff, rather than hoping to memorise it, as that
will help more if there's a question asking you to explain a concept using pseudo-code,
rather than just text.
(it's a 3rd-year unit; you should have a good understanding that all
material is examinable, and how to study for it. Honestly, politely,
what response were you expecting?)
||Sun 7th Jun, 12:37pm
> What you want me to say, and what is the truth, and likely quite different.
> Are you now revising, or studying it for the first time?
> It's clear that many pushed out their project submission, perhaps, without keeping an eye on
> their exam calendar.
Yes, this is true.
Although I'm not sure how this could be a surprise considering the fact that the project was
itself was released late, with the getting started page being released roughly 12 days late.
> The material to study, and the material to be examined, is all listed on our unit Schedule
> page, 11 weeks, clearly the first week is very introductory, and roughly 5 points highlighted
> each week (which may not correspond directly to the titles on slides).
> All of it is equally important, maybe Internetworking more important than Data
> Communications, but questions will come from both areas. For example, even though there's no
> detailed coding required in the exam, don't give up on the Labsheet exercises. Ask yourself
> *why* a particular question on a labsheet was set, what you should have learnt when you
> completed the exercise. Reflect on this stuff, rather than hoping to memorise it, as that
> will help more if there's a question asking you to explain a concept using pseudo-code,
> rather than just text.
> (it's a 3rd-year unit; you should have a good understanding that all
> material is examinable, and how to study for it. Honestly, politely,
> what response were you expecting?)
I suppose I deluded myself, hoping to receive some counselling.
I'm well aware of the contents listed for the unit and I appreciate you adding the weight of the
laboratory exercises as well. (Not to mention the recommended readings)
The "roughly 5 points" per week is actually around three times more.
I've listed the seemingly more important topics covered for reference.
Could you please clarify if focusing only on the points listed on the schedule is enough?
Or perhaps a list a few numbers that you don't think could be all that relevant.
1. Basic networking definitions
2. Why do users value computer networks?
3. Research interests and networking
4. The Need for Network Protocols
5. The ISO/OSI Reference Model
6. Why a Layered Model?
7. Physical Layer responsibilities
8. Data Link Layer responsibilities
9. Metrics Of Network Measurement
10. The Physical Layer and Transmission Errors
11. How Data is Placed in Frames
12. Phase Encoding of Signals
13. Error Detection and Correction
14. Hamming's Correction of Single-Bit Errors
15. Cyclic Redundancy Codes (CRCs)
16. Polynomial Codes
17. Three Levels of Data Link Layer Complexity
18. The Unrestricted Simplex Protocol
19. The Half-Duplex Stop-and-Wait Protocol
20. Detecting Frame Corruption
21. Detecting Frame Loss
22. Using simulation to develop network protocols
23. The Benefits of Network Simulation
24. The Pitfalls of Network Simulation
25. The cnet Networking Simulator
26. Defining networks using Topology Files
27. A complete stopandwait Data-Link Layer protocol
28. Rebooting each node
29. Receiving new messages for delivery
30. Transmitting across the Physical Layer
31. Handling the arrival of new physical frames
32. Improving The stop-and-wait Protocol
33. Reducing The Number Of Data Link Frames
34. The Data Link Layer - Sliding Window Protocols
35. Frame Pipelining
36. The go-back-N Protocol
37. The Selective Repeat Protocol
38. A Problem with Selective Repeat
39. A Sample selective-repeat Protocol
40. Simplified Satellite Broadcasting
41. Implications for Network Protocols
42. Conventional Channel Allocation
43. Pure ALOHA
44. Slotted ALOHA
45. Local Area Networks
46. Carrier Sense Networks
47. Factors Affecting CSMA LANs
48. Persistent CSMA Protocols
49. Non- and p-persistent CSMA Protocols
50. IEEE-802.x LAN Standards - The Ethernet System
51. Physical Properties
52. Ethernet's Contention Algorithm
53. Ethernet Addressing Schemes
54. Packet Transport Mechanisms
55. Hubs, Switches, and Collision Domains
56. Interconnecting IEEE-802.x LANs
57. IEEE-802.3 Bridges
58. Bridging Different Types of LANs
59. The IEEE-802.11 Wireless LAN protocol
60. Hidden Node, Exposed Node
61. 802.11 Collision Avoidance
62. Access-Point Association
63. Attacks Against Wireless Networks
64. Wireless Network Encryption
65. The Wired Equivalent Privacy (WEP) algorithm
66. WEP Encryption
67. Problems with WEP Encryption
68. Problems with WEP's Initialization Vector
69. WEP Authentication
70. Attacks by Patient Attackers
71. The Relationship Between Hosts and the Subnet
72. Implications for Data Link Layer software
73. Responsibilities of the Network Layer
74. An example NL responsibility - packet fragmentation and reassembly
75. Network Layer Header Management
76. The Path of Frames and Packets
77. The Two Contending Network Layer Schemes
78. Network Layer Routing Algorithms
79. The Two Classes of Routing Algorithm
80. A naive non-adaptive routing algorithm - Flooding
81. Improved Flooding Algorithms
82. Adaptive Routing - Distance Vector Routing
83. The Count-To-Infinity Problem
84. Adaptive Routing - Link State Routing
85. Congestion and Flow-Control in the Network Layer
86. End-to-end Flow Control
87. Load Shedding
88. Traffic Shaping - Leaky Bucket Algorithm
89. Traffic Shaping - Token Bucket Algorithm
90. The Requirements of Internetworking
91. The TCP/IP Protocol Architecture
92. Traditional Class-based IP Version 4 Addressing
93. Classless Inter-Domain Routing (CIDR)
94. Mapping Internet Addresses to Physical Addresses
95. The Address Resolution Protocol (ARP)
96. Configuration of Network Devices
97. Problems With Static Configuration
98. A partial solution
99. The Bootstrap Protocol (BOOTP)
100. Booting over a Network
101. Dynamic Host Configuration Protocol (DHCP)
102. The TCP/IP Protocol Dependencies
103. Internet Protocol (IP) Datagrams
104. Internet Control Message Protocol (ICMP)
105. Interesting Uses For ICMP - Traceroute
106. Internet Transport Layer Protocols
107. Port numbers
108. The Transmission Control Protocol (TCP)
109. What TCP/IP Provides to Applications
110. TCP/IP 3-way connection establishment and teardown
111. TCP/IP Retransmissions
112. TCP/IP Congestion Control
113. Network Application Program Interfaces (APIs)
114. An Example Network API - Berkeley Sockets
115. Domain Addressing
116. Establishing Sockets With OS System Calls
117. Naming Sockets
118. System Call Sequences for Connection-oriented and Connectionless I/O
119. A Client Process in the Unix Domain
120. A Server Process in the Unix Domain
121. A Remote Login Client in the Internet Domain
122. What Are Client/Server Software Architectures?
123. What Does A Client Process Do?
124. What Does A Server Process Do?
125. What is a Two-Tier Architecture?
126. What is a Three-Tier Architecture?
127. What is an 'Intranet'?
128. Characteristics Of Client/Server Architectures
129. Partitioning Client/Server Responsibilities
130. Concurrency (and hence speed) in Servers
131. Iterative Servers - managing a single connection
132. Iterative Servers - managing one process per client
133. Concurrent Servers Using select()
134. The Internet Supervisor Daemon - inetd
135. Addressing Between Heterogeneous Machines
136. Accessing Protocol and Service Information
137. Typical API Library Routines
138. Automated Development of Distributed Applications
139. The Remote Procedure Call (RPC) Paradigm
140. The RPC Execution Order
141. An Example of Transparent Access
142. Passing parameters to remote procedures
143. SUN Microsystem's RPC Compiler - rpcgen
144. Naming and Interface Binding
145. Locating and calling the server
146. Java's Remote Method Invocation (RMI)
147. Building RMI Applications
148. Semantics of RPCs and RMI
149. The External Data Representation
150. The Differences in Data Representation
151. The XDR Approach
152. The XDR Data Representation
153. The XDR Representation of some simple types
154. The XDR Representation of some complex types
155. The SunOS XDR Library
156. Converting complex data structures
157. Object Serialization in Java
158. Serialized Java Applets
159. TCP/IP Overview and Vulnerabilities
160. Packet Sniffing
161. TCP/IP port scanning
162. Stealth port scanning
163. Internet protocol (IP) spoofing
164. UDP Packet Spoofing
165. TCP/IP Sequence Number Attacks
166. Denial of Service (DoS) Attacks
167. The smurf DDoS Attack
168. The SYN -Flood Attack
169. Distributed Denial of Service (DDoS) Attacks
170. Security at Network Boundaries
171. Packet filtering at network boundaries
172. Possible packet filtering criteria
173. Developing a Firewall Policy
174. Packet filtering with iptables
175. Packet lifetimes using iptables
176. An introduction to filtering rules
177. Examining packets on specific interfaces
178. IP Masquerading
179. An Example of IP Masquerading
180. Network Address Translation (NAT)
181. Network Address Translation (NAT)
182. Connection Tracking
183. Tracking FTP Connections
184. Intraorganization Firewalls
185. A DeMilitarized Zone (DMZ) Subnet
186. Virtual Private Networks and IPSec
187. The Security Case for Virtual Private Networks
||Mon 8th Jun, 4:44am
> Although I'm not sure how this could be a surprise considering the fact that the project was
> itself was released late, with the getting started page being released roughly 12 days late.
Released Friday 24th April, in the week that it was always due to come out:
with the first student seeking clarification on Sun 26th April, over the long weekend:
When first released, Getting Started was a section on the single project page, but later that day a new
Getting Started page was written; certainly there by Wed 29th:
Very unsure where you get your 12 days from. ?
Then, some appear to have started the project later than others:
> The "roughly 5 points" per week is actually around three times more.
> I've listed the seemingly more important topics covered for reference.
What you have simply provided is a list of the titles of each lecture slide.
It's bordering on childish.
Every unit's lectures have many slides; the slide titles are not the distinct
topics to be studied, they simply identify the material on the slide.
I'll reiterate that each of our assessable lectures have about 5 topics to study,
as identified on our Schedule page.