Can we pass on the names of the neighbours in command line along with the IP:port or is this not allowed

ANONYMOUS wrote: 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.

"Christopher McDonald" <ch*i*.*c*o*a*d@u*a*e*u*a*> wrote: 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?

ANONYMOUS wrote: One possibility - if you're starting all of your station servers from a script then, when one of them transmits that first 'hello' datagram, its destination server might not have started yet. The datagram is transmitted, but there's no server at the destination host and port there to receive it. Try - before transmitting your first datagram, sleep(2) to give all servers a chance to start. ??

Hmm, I tried that and it didn’t seem to work

ANONYMOUS wrote: I appreciate that no-one likes the phrase, but "it works for me" : create/bind to your TCP and UDP sockets sleep(2) transmit a 'hello' datagram to your neighbours enter your select() loop ..... receive 'hello' datagrams from neighbours

Sorry, forgot to add - I don't use the station names for anything, other than naming the final destination station, and to help with debug printing.

Yeah, my code is near identical to that format and it was not working, I added a timeout into the select() of 10s and now it gets the neighbours every time (with almost no change to the actual time to get all the names - near instant)

ANONYMOUS wrote: Glad that something's working for you, though I can see how allowing the select() call to unblock after 10sec would help the datagrams arrive. It sounds like you don't have all the important descriptors set in your readset.