That still doesn't solve the problems of: 1. Single homed outbound channel of SRCDS 2. Single homed inbound channel, selection by +ip or first connection to Master browser. 3. Single advertised public IP address for the server.
You'd still be using only one pipe for externally initiated connections. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Steve Dalberg > Sent: 11 November 2005 08:59 > To: hlds_linux@list.valvesoftware.com > Subject: Re: [hlds_linux] Re: srcds with multiple ip address > > K1ll3rD wrote: > > Replying packets will use the same NIC as the packet came > in from for > > it's gateway. > This is referenced in RFC 1122 as Strong End Station Model, > check you OS on how to implement Strong ES model, as it > varies from platform to platform... Still, this will not > work on the same subnet (ie, 2 connections to same carrier) > > And yes, my day job is a Network Engineer, which is the only > reason I know that off the top of my head... One of 5 RFC's > I know by number... > > Later, > Steve > > _______________________________________________ > 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
