How to Have Master Server Specify Default Local Network

[wuench]

Yeah I guess that would be an issue. Selecting an address or registering all of them seems like the only options.

Another option, is multicast or even UPnP. UPnP advertises on a known multicast address. If you beaconed using UPnP, then have the clients pick it up there would be no configuration needed to find services, and you would no longer be tied to subnets. It's really simple since it uses UDP and HTTP/XML to advertise services. If you are worried about multiple master servers on the same subnet you could advertise the unique ID and have the clients pick one at install time, or even select at runtime or via a menu.

For multicast (non UPnP) you would just have to use an address that isn't a known one and maybe allow the user configure it (to avoid conflicts and allow multiple Master Servers). Then run your protocols over it. Multicasts (and UPnP) are non-routable in most consumer setups (multicast routing protocols do exist though, most people are running them).

And if you use UPnP then when IPv6 starts hitting you hopefully won't need to change too much plumbing, just add the link local multicast address it advertises on.

Anyway it seems ideal for what you are trying to do. I realize they are probably major changes but some things to keep in mind for the future.

[Dean Roddey]

You 'da man!!! Thanks.

Highlighting my complete lack of knowledge regarding network issues, I had no idea that you could set the order... Thanks very much for your help!

I just put up a .20 version. Can you help me make sure that I've dealt with this issue by going back and putting the order back the way it was, restart your system and make sure that the problem is still there. Then upgrade to .20 and leave it in that bad order and make sure that it's no longer a problem? .20 should deal with this issue correctly and not require you to adjust the order of interfaces.

[TurboSam]

Dean, I just saw your request, and I'd be happy to test out .20. I should be able to try it tonight...

[Dean Roddey]

Dean, I just saw your request, and I'd be happy to test out .20. I should be able to try it tonight...

OK, thanks. Note that there's no particular advantage to re-doing the rearrangement of the interfaces once you move to .20, so you don't really need to move them back again after you confirm it works. It might make sense to do so just for completeness sake, but CQC won't need it and there won't be any extra hit either way anymore.

[TurboSam]

Dean, everything works fine in .20.

While using .19, I set the order in which the network connections are accessed to make the .192 network last on the preferred list, and master server could not find it. Once I upgraded both computers to .20 (leaving the "bad" order intact), I had no problem and the AppControl on the 192 network was found and worked.

Let me know if I can do anything else.

[Dean Roddey]

Nope, that's all I needed to know. That should insure that all will be well for other folks. Thanks.