On Wed, Feb 04, 2009 at 11:37:00AM +0900, Will Dowling wrote: > Our organisation runs quarterly LAN events on networks that simply will > not fit within a /24. Our networks are configured as 10.0.0.0/16, though > we only use IP Addresses within the first three /24's within this space. > > Whist clients can connect to the servers fine, broadcast to actually > find them in the first place does not work reliably at all. > > Worse yet, at a smaller event, we renumbered to fit everything within a > /24 network - yet it seems the steam client won't broadcast across all > available networks - if the end-user has more than a single network > interface (eg: Hamachi, OpenVPN, VMWare, second network card) - steam > will broadcast over what seems to be an arbitrary choice of interface. > > It would be awesome if Valve could allow the LAN server to be > configurable to some degree for what broadcast space to use (even if the > default is what's currently in place), and to improve the steam browser > for the above issue.
Heh..know your problem :) we run a large event every Easter (~5000 people), and this has been a problem forever :) One of the ways we've gotten around the issue is to block incoming player connections to the internal gameservers, but make them connect to the normal Valve master server, and making sure they have a server name that is unique enough to be easily picked up by filters in the browser. We've also messed with forwarding broadcasts to all segments and other weird network magic, but the first one seems to be the best on to go by. Of course, if you're party do not have a internet connection then you are out of luck :(. -- Per Kristiansen [email protected] _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
