It's UWAweek 17 (1st semester, week 8)

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 selected article
Showing 1 of 256 articles.
Currently 2 other people reading this forum.


 UWA week 11 (1st semester, week 3) ↓
SVG not supported

Login to reply

👍?
helpful
3:28pm Thu 14th Mar, Christopher M.

"Cameron Locke" <21*3*2*2@s*u*e*t*u*a*e*u*a*> wrote:
> For Lab 2, STOPANDWAIT2 has a variable called ber, set to 0.00005, is this the probability of frame corruption? If not, how is frame corruption handled in this topology?
It stands for 'bit error rate' - the probability that one-or-more bits in a frame will be corrupted.
> I've managed to get the Negative Acknowledgement working (or at least, when a corrupt frame is identified, it sends one, and the message is resent), but every time a message that has a corrupted frame is noted, the resent message will also be corrupt, and I'm not sure if that's on my end yet.
Yes, there's an additional problem that needs to be solved. It's easy to detect a damaged frame, and send back a negative-acknowledgement, but what needs to happen if that negative-acknowledgement frame is damaged?

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  5:07AM Sep 06 2023
Privacy policy