Re: Accessing Multiple ISPs on the fly



Beau:

Thanks, I'm trying to digest all the info you gave me. How do I dual
home the PCs (one is where the "My Documents" and Printers reside and the
other is the machine with the billing app) so they are always "related" to
the client machines?

ps:
The reasons I'm doing this are:
a) The LAN is set-up and running with a 32 port (+ one input) switch
connected through an ADSL router to one ISP. We recently contracted another
ADSL connection with a second (cheaper) ISP. We don't want to throw away the
present - good - switch to buy a new one.
b) We don't want to disconnect the previous ISP until (and if) the new
one proves to be better. Meanwhile we'll be testing both simultaneously,
allowing the user to change between them. If (big if) it might be worth our
while to have both ISPs together we would leave the setup permanently.

Michu


"Beau" wrote:

> I am assuming that your WAN connections are going through two differnet
> routers. There are a combination of issues here. I believe in order to do
> this you have to do three things. First, setup each router to route
> different IP subnets (e.g. router A IP subnet = 192.168.1.0 and Router B IP
> subnet = 10.0.0.0). Second, each batch file should be setup to add the
> workstation to the other subnet if it is used to reset the IP configuration.
> Third, in-order-to keep the connection to the node that is hosting the "My
> Documents" share you will have to dual home it in both private IP subnets
> (e.g. give it an IP address on the192.168.1.0 network and the 10.0.0.0
> network). Giving the node that has the "My Documents' share an IP in each
> subnet will enable it to properly respond to requests without breaking the
> connections.
>
> Switches respond at layer two and could care less what the IP address is.
> Its the routers that care. This, in theory, should solve your problem.
>
> I am not sure why you have decided to set your network up like this. But,
> if it is for load balancing purposes there are several reasonably priced
> routers out there that will bond the WAN channels from different ISPs and
> enable proper load balancing. i hope this helped.
>
> Beau
>
> Just a few dual WAN for load balancing. i have not checked this list. i
> got it from dslreports.com.
>
> Symantec VPN 200
> Nexland Pro800
> BroDigit NFR3024
> Hawking FR24
> Xincom XC-DPG402
> Xincom XC-DPG502
> Xincom XC-DPG602
> OvisLink MN200
> HotBrick Firewall VPN 600/2
> HotBrick Firewall VPN 1200/2
> ZyXel ZyWall 35
> Linksys RV082
> Edimax BR-6104K
> Xterasys XR-4106
> Pheenet BIG-02/4
.



Relevant Pages

  • RE: FreeBSD router two DSL connections
    ... >Subject: RE: FreeBSD router two DSL connections ... suppose I'm a small ISP and I go get a ... and blocked by ATT or Sprint, or my peer routers, in the ... >> letsseenow, these are full duplex 'pipes', can ...
    (freebsd-questions)
  • Re: handling hsrp connections from isp
    ... I've got two connections to the same ISP (connected to two of their ... routers), with HSRP running on their routers. ... Load balancing across connections is not a concern here -- I am just ... But the question is dealing with the two HSRP connections from the ...
    (comp.dcom.sys.cisco)
  • ICS and WFW my expose shares ...to 3 party.
    ... If two private parties are connected to the ISP via a router acting as DHCP ... of the same non routable Subnet i.g. ... nomal way to share if one party owns all connections.) ...
    (microsoft.public.windowsxp.general)
  • Re: Server in a NAT subet?
    ... and I am not sure what happens if I publish the routers ... Ignoring any 'Acceptable Use Policy' or 'Terms of Use' that your ISP may ... address/port of the real server, then it's essentially the same as above. ... ISPs place on incoming connections. ...
    (comp.os.linux.networking)
  • Re: Subnetting and masking
    ... you cannot route individuals addresses where routers are over-lapping ... If these routers are in different locations then the ISP will route them ... subnets, then they would route a 32 address subnet and you would subnet it ...
    (microsoft.public.win2000.networking)