Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Howard R. Hansen who wrote (11540)	11/23/2000 12:24:54 AM
From: Greg from Edmonton	Respond to of 14778

Hmm, well I'm just "at the preliminary planning stages" for now on this one and I haven't done anything like this yet (i.e. advanced routing / load balancing / traffic shaping / QoS). Perhaps outside the scope of my current knowledge and experience, for now. You raise several good points. Now that I think of it, simply having two gateways would be altogether different and not necessarily load-balanced or high-availability. ...set up a Linux box as a router that will forward the Internet connection to the Win2k server, which will in turn pass it on to its DHCP clients This statement leads me to believe that the Win2k server also has routing enabled, and acts as intermediary between the workstations and the Linux router? My current solution is to create a shell script that switches the default route from one interface to the other (and using the appropriate gateway). Done via a script to modify the routing tables as-needed? I was primarily thinking of how such an application would apply to my friend's situation. In his case, the SMTP access for client machines would not be an issue because he is running a mail server internally.