Hi Ashley I happened to be playing around with something very similar this weekend. My ISP is forcing me to switch my IPs over to a new subnet, so I was trying to get both worling simultaneously to avoid any downtime. I ended up shortening the TTL in my DNS and biting 15 minutes of downtime :)
I tried using two different gateway boxes to my lan, as well as using two interfaces on one box suppporting both IP sets. Anyway, I quickly realized that if the internal server is using gateway A (say the Cable server) as it's default route, traffic coming into gateway B (say the DSL server) will try go out gateway A, and not back through B. Then I found that if you are using NAT, you can't have the traffic come in one interface and then leave out another (even if both interfaces are on the same box because I tried that too solving the gateway problem). It makes sense to me know, but I had to try it to figure it out. Now, based on you description, this is what I would do. I would setup your network below (but you don't need 2 network cards on the internal server, just a hub/switch) and have the internal server use the cable server as it's default route. So, all normal internal use will take advantage of the fast downloads. Then I would nfs mount your internal server data dir read only on the DSL server. Run your ftp server here and do your downloads from work through it (or uploads to it rather). This will give you faster traffic out controlled by which IP/name you use. You can of course push stuff home via the cable server to get the best speed that way. What do you think? Sounds quite doable to me. A bit of a waste of that DSL connection though. You could always ssh over to it and kick of downloads from to to make use of the bandwidth. There may of course be better solutions to this - I make no claims about being an expert on this stuff. charles ----- Original Message ----- From: "Ashley M. Kirchner" <[EMAIL PROTECTED]> > > As of today I have both DSL service (256K) as well as Cable (1.5Mb/128K). As you can tell, the upstream on the cable is puny and unfortunate for me since I tend to transfer some rather large files up to my server at work. Obviously I would favor the DSL for upstream, and the cable for downstream... (you can already guess what I'm getting at, don't you?) > > So, can it be done? All I honestly care for is *upstream* FTP transfers...nothing else. Email, WWW, *downstream* FTP, and whatever other dang traffic can go just fine over the Cable connection. Now I realize it's not easy to split up/downstream FTP connection, so even if all FTP connections go through the DSL, I'll be happy. > > I can easily have the Cable connected to one server and the DSL to another (actually, in a sense it's already setup that way, but only the cable one is on the network...the DSL server is a lone cowboy at the moment). But what I believe can't be done is somehow merge these two servers into one "network" where everyone else sitting behind them (masq machines) can have access to both. Each server has a completely different set of IPs, from two completely different providers. > > Maybe I'm dreaming, but this is about the most logical solution that I could think of: > > > [ Cable Server ] [ DSL Server] > eth0: DHCP IP from provider eth0: Static IP from provider > eth1: Static private IP eth1: Static private IP > | | > | | > \ / > \ / > +-------------+---------------+ > | > | > [ Internal Server ] > eth0: serves private network (goes to HUB) > eth1: serves eth1 on Cable Server > eth2: serves eth1 on DSL Server > > The Internal Server will then do the traffic directing, through....something, not sure yet. > > Have I gone insane yet? Does this even make sense? _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
