It's UWAweek 48

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 503 articles.
Currently 3 other people reading this forum.


 UWA week 19 (1st semester, week 10) ↓
SVG not supported

Login to reply

👍?
helpful
12:01am Fri 10th May, ANONYMOUS

"Christopher McDonald" <ch*i*.*c*o*a*d@u*a*e*u*a*> wrote:
> ANONYMOUS wrote: > > > Can we pass on the names of the neighbours in command line along with the IP:port or is this not allowed > > Not permitted, because it's not what is specified on the project sheet, > and will prevent your project from being tested using some common scripts. > > It's trivial to first send a datagram to each of your neighbours, telling them your name.
I'm attempting to do this exact thing where as the station starts up it sends its name to all its neighbours (before any requests are made), then in the main server loop with select() each station picks up on neighboring station's names. But for me I'm having issues where not all the names come back, and instead only some of them do. Some others are just not received and I'm unsure as to why that would be happening even though the select() function is present and should be able to handle the availability of sockets for when they are readable. The number of names which come back is also different every time the stations are run, which is making me think that maybe the issue lies with the blocking nature of receiving datagrams (despite select()) Would you know why this is occuring?

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