It's UWAweek 47

help3002

This forum is provided to promote discussion amongst students enrolled in CITS3002 Computer Networks.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message. How do I ask a good question?

Displaying the 3 articles in this topic
Showing 3 of 503 articles.
Currently 37 other people reading this forum.


 UWA week 22 (1st semester, study break) ↓
SVG not supported

Login to reply

👍?
helpful
6:36pm Tue 28th May, ANONYMOUS

Develop an implementation in pseudo-code, with a syntax similar to C, Python, or Java, that simulates the behaviour of the 1-persistent CSMA/CD protocol over 100Mbps Ethernet. The simulation should support N identical nodes, each wishing to transmit a frame to other nodes at random intervals. Assume that Ethernet employs a fixed slot-time, and that collision detection and resolution takes exactly one slot-time. For this exam question, how can you know if binary exponential back-off is used or not, or is it up to us whether or not we implement it?


SVG not supported

Login to reply

👍?
helpful
8:43pm Fri 31st May, Oliver F.

Binary exponential back-off is a part of the standard Ethernet protocol and thus will be implemented I think.


 UWA week 23 (1st semester, 1st exam week) ↓
SVG not supported

Login to reply

👍?
helpful
2:14pm Tue 4th Jun, Christopher M.

ANONYMOUS wrote:
> For this exam question, how can you know if binary exponential back-off is used or not, or is it up to us whether or not we implement it?
Yes, your pseudo-code should include an 'implementation' of binary-exponential backoff, as the delays of each node (based on their observations of collisions) will affect when they transmit/retransmit in the future and, thus, affect how the medium is utilised.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy