Okay, this seems impossible to me...at least in a number sense....it just doesn't 
make sense, but I'll ask anyway.

    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?


--
H | "Life is the art of drawing without an eraser." - John Gardner
  +--------------------------------------------------------------------
  Ashley M. Kirchner <mailto:[EMAIL PROTECTED]>   .   303.442.6410 x130
  Director of Internet Operations / SysAdmin    .     800.441.3873 x130
  Photo Craft Laboratories, Inc.            .     3550 Arapahoe Ave, #6
  http://www.pcraft.com ..... .  .    .       Boulder, CO 80303, U.S.A.




_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to