Do you have your own DNS servers and domain? Or is your ISP currently
providing it for you?

Secondly, if you're connecting to two seperate ISPs, then you're probably
ending up with two different IPs for your DSL service endpoints (your ends).
I don't know a lot about DSL, not having used it yet....

-------DSL 1-----------
                                       (Netopia 7100) -------
(HUB/SWITCH) --- (other machines)
-------DSL 2-----------                                                   |

(another router)

|

(192.168.X.X unconnected network)

|

(HUB/SWITCH) ---- (office machines)


I may be off the track completely here because I am not sure that I
understood your problem correctly.

As I see it, you want your web/dns servers ("other machines" in diagram)
accessible from the internet at all times even if either DSL 1 or 2 go down.

Now if you want this to work, you have a problem - the thing is that if your
own servers are on a network class you own, then you can have a transparent
solution in the sense that if either link goes down, the routing protocols
running on the internet will route the data in over the other line. (correct
me if I am wrong here please!)

But if you're getting a subnet/ip from each isp then its a lot more complex.
You then need to tell the clients to connect to a seperate IP altogether. I
think you'll need DNS to help you out here but then you'll run into issues
like cached records and then people trying to connect to an IP that isn't
accessible. You'll also probably need to play with masquerading (something
like transparent proxying) so that whichever line the request comes over,
once it gets to the router, its piped through to the webserver.

I can't see any clear, simple solution for your needs without ISP
involvement. But then again, I am not exactly an expert - maybe someone else
can help more.

It would also help if you could clarify the problem a bit more with an ASCII
diagram.

-Ahsan Ali


----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 11, 2000 3:09 AM
Subject: network layout advice needed


>
> I have 2 dsl lines and would like to be able to offer some form of
> redundancy for my web servers. it does not have to be high tech and I
> prefer a solution that does not require co-operation from each of the
> 2 isp's. I want something that works anywhere. My idea is to put my
> primary dns server on one line, and secondary on the other, so if my
> primary line goes down, new traffic will go to the other line. I know what
> the problems are with the setup but the point is that it is easy to do
> and it doesn't require anything on the part of my isp's
>
> the problem is what goes on after that. i got iproute2 working such that
> i can pull pages from either dsl line, with 2 nics in each machine, 1
> router per dsl line, and separate hubs. but the machines cannot
communicate
> with each other unless they go out to the internet and back on the other
> line. I have tried eveyr configuration, i begged, I pleaded, i kicked the
> computers a few times, etc. sometimes it works for a few days then
suddenly
> it stops. only sends one ping, only works in promisc mode, you name it,
> I got the symptoms.
>
> so how should I set this thing up? I am willing to build my own linux
> router, and I have 2 switches and 3 hubs, plus hubs on the routers (one
> router is a netopia 7100 and it supposedly supports 2 dsl lines).
>
> here is what i need:
>
> 1. ability to access certain machines (web servers) from the internet
> through either dsl line. don't care if I need 2 nics per machine,
> separate hubs, an extra router. whatever it takes.
>
> 2. communication between the machines without going out to the net, and
> without all the flakiness
>
> 3. an internal lan with machines that do not have to be reachable from the
> net, such as my database and desktop machines. I want this to be on a
> 100mbit connection for better performance; my big hubs are 10mbit. my
> small switches are 10/100 (5 & 8 port)
>
> 4. not require cooperation from isp
>
> 5. not cost me thousands of dollars in software
>
> I would consider a central file server with www servers on each connection
> reading from one central internal machine with all the www docs, but the
> performance just transferring files has been sub-par (tried nbd)
>
> any help or advice?
>
> dtiberio
>
> also I have 2.0 and 2.2 machines. would upgrading solve this problem?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to