Discovery Cross Network Segments ?

[lyling]

I have some requirement about discovery my server from different segments.
My Server(device) is hosted on Segment 192.168.2.x.
My Clients(Software) is on Segment 192.168.1.x.

Clients can only discovery devices on the same segment 192.168.1.x;
How can i do that clients can discovery my server(device) when in different segment?

[Frankenslag]

I think that you need to talk to whoever is administering your network. I believe that multicast routing would need to be enabled between the two network segments. I also had a similar problem but it was between WIFI connected devices and wired.

[Yortw]

Hi,
I'm not familiar with this setup personally and I'm not expert enough in networking to have a definitive answer for you, sorry. I think what @Frankenslag said is true. You may also need to adjust the 'time to live' setting on the UDP sockets created, as I believe that setting is a number of 'hops' the packets are allowed to make, with each router being considered a hop, so that value may need increasing as well. Unfortunately that's all the advice I have. Hope it helps. Good luck!

[marchewek]

I'm pretty sure that one can disable multicast message routing in the infrastructure, so increasing TTL might not necessarily work. We had a case where UDP messages were not transmitted to other VLANs at all and it was solved by simple router configuration (what actually was not an easy feat in a corporate environment ;)
Please keep in mind that UDP packet delivery is anyway not guaranteed, so in parallel to discovery I'd recommend implementing explicit configuration :)

[Yortw]

Apologies for leaving this issue unattended for so long. Its likely you've moved on, so I will close it. However, in case you haven't given up, or for anyone else who stumbles across this issue;

I'm closing this as it's old and no follow up, but I think it's as stated: the network needs to be configured to support this, UDP/multicast must be supported, and it must be supported across network segments (which may involve increasing "TTL", as that isn't actually a 'time to live' but rather a number of hops, if my memory is correct).