I happen to be in a situation where I have both a DSL and CABLE connection to internet up for the time being... (Until the DSL contract month runs out).
It affords a nifty opportunity to do some experiments. Of course I tested the speeds of both and it varies between 200 and 500 % faster on the Cable connection. (Nice). At first I used single machines connected independently to the respective IPs for testing, but it slowly dawned on me that I could hook everything up on the lan, to the same subnet and then just reset the GateWay target on individual machines as needed, for any of 6 machines. So currently I have two internet outlets and two gateway routers on 192.168.0.0/24 Here's the technical part: Assume I have loaded a web page that downloads a video to my cache as it plays. Assume further there are several of these to be played one by one. After playing one, if I reset my GW (and I have also rest /etc/resolv.conf to use that gw address for dns [probably not totally necessary]). Followed by /etc/init.d/net.eth0 restart. Will the browser, which has not been restarted, now use the new gateway when I run the next link (or for testing, run the same link again), or will it continue on the same route (which is still available), that is, will the browser (firefox) continue using the original GW until the browser itself is restarted? I know I could track all this with tcpdump but it gets sort of cumbersome unless you've memorized the necessary commands to filter output down to something more usable. I usually get so tangled up with tcpdump I spend more time on it than the project at hand. I don't use it very frequently so inevitably spend gobs of time at `man tcpdump' instead of tending to what I started to do. Why I ask is that the site I'm doing this on requires me to login and then relocate the stuff I want to see if I have to restart the browser. I wanted to try to gauge if there was much of a noticeable difference with the two IP connections. And it would be handy to just step through the links changine the GW intermittently. -- [email protected] mailing list
