I used to help run a 200-300 bi anual lan party in the wash dc area for a few years, and back then, it was limited to the 192.168 class c addresses. It *was* a pain, however we simply just combined two class Cs to get around the IP restriction issues. We considered putting up a small homemade router between the classes to minimize broadcasts, but didn't want to segment the lan, and therefor players from eachother.
It is kinda dumb, however it was easily fixed. There were issues with the lan client server browser finding all servers reliably, however it wasn't too bad. We always had enough game servers. This might have been Valve's rationale to only allow class c. even two class Cs caused issues with broadcasts, let alone a class B. Doesn't fully make networking sense, but there you have it. Kev Jordan Toor wrote: > It doesn't. If the server is operating with sv_lan 1, if you try to join via > Hamachi, the server tells you that you need to have a class C address. > > I have to retest, but I believe it rejects anything other than a class C > address. > > I was that person Morgan was talking about, but basically I believe the > server is visible on any class private network, but I don't think you can > join it. > > Don't have time to retest, but if anyone else has knowledge about it, > advise. (Might test it tomorrow) > > Jordan Toor > > On Tue, Feb 3, 2009 at 2:29 AM, Tony Paloma <[email protected]> wrote: > >> Hamachi operates on 5.0.0.0/8 and I'm pretty sure it works just fine on >> sv_lan 1. >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Morgan >> Humes >> Sent: Monday, February 02, 2009 11:01 PM >> To: [email protected] >> Subject: [hlds_linux] sv_lan - Class C Space? >> >> So I was having a conversation with a friend on how hlds claims that sv_lan >> only works with Class C Address space. This is an epic fail if it is >> indeed >> true. RFC 1918 does define private address space in Classes A, B, and C. >> Thus a LAN Party could easily use any of the following private address >> spaces: >> >> 10.0.0.0 - 10.255.255.255 (10/8 prefix) >> 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) >> 192.168.0.0 - 192.168.255.255 (192.168/16 prefix) >> >> (Note, taken from RFC 1918 section 3 - http://tools.ietf.org/html/rfc1918) >> >> For those who are not well versed in networking, the above 10/8 is a Class >> A >> range, 172.16/12 is Class B, and 192.168/16 is Class C. >> >> Thoughts? >> >> Morgan >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
