I considered suggesting an arrangement like this, with the interconnect 
outside the wireless segments.  I discarded that "solution" because it 
requires creation of a third segment, to which the routers and the ISP 
gateways are attached, and a bunch of route configuration so that each knows 
about all the things it needs to.
  And, as you've found, at most one of the ISP connections can supply 
dynamic addressing.  With 216.x.x.x and 10.x.x.x devices on the same segment 
with a hub (shudder shudder), who provides routing between the two?  (Or do 
you let traffic to local resources go out one ISP, across the Internet, and 
in through the other -- which, by the way, shouldn't work for the 10.x.x.x 
addresses....
  Yes, you can build it that way, but doing so *properly* is an awful lot of 
effort, compared to the crossover, for very little gain.

David Gillett



On 9 Oct 2006 at 8:32, Brian McCarthy wrote:

Date sent:      	Mon, 9 Oct 2006 08:32:30 -0600
Send reply to:  	Personal Computer Hardware discussion List
             	<[log in to unmask]>
From:           	Brian McCarthy <[log in to unmask]>
Subject:        	Re: [PCBUILD] Cable AND dsl
To:             	[log in to unmask]

> Again. I beg to differ...
> 
> I have two wireless access ppoints (routers) in my computer lab;
> - each is connected to a different ISP - One has a static IP and the other 
> is dynamic.
> - the static IP is 10.x.x.x - The dynamic is 216.x.x.x (WAN side)
> - the LAN side IPs are both 192.x.x.x (.254 and .253 respectively.
> - both are plugged into a four port hub which is plugged into the wall and 
> from there to the wiring closet.
> - I am sharing three printers, a scanner, a DVD RAM, and an NT File Server. 
> I have XP on 18 student work stations and '98 on four workstations.
> - When a notebook (or two) comes into my classroom the wireless network 
> thingee pops up with two choices. It doesn't matter which WAC they pick 
> EVERYTHING is there for everyone.
> - I don't have a crossover in ANY of the hookups. (Ain't autosensing hubs 
> grand?)
> 
> The DHCP thing makes sense, though... It's not been a problem (I'm guessing) 
> because I use static IPs on my LAN. 'n the only time the WACs are used is 
> when people bring 'puters in from outside. Oh, And the two teachers in 
> adjoing clasrooms that leach the signal. They've probably been just hittin' 
> on it 'til they come up with a free lease. Hmmm...
> 
> Anyway... My two cents worth...
> 
> Brian D. McCarthy
> 
> >From: David Gillett <[log in to unmask]>
> >Reply-To: Personal Computer Hardware discussion List              
> ><[log in to unmask]>
> >To: [log in to unmask]
> >Subject: Re: [PCBUILD] Cable AND dsl
> >Date: Mon, 9 Oct 2006 00:30:41 -0700
> >
> >On 6 Oct 2006 at 10:16, garytennesen wrote:
> >
> > > I have an update:  I now have cable internet and DSL internet at my home
> > > with a wireless router on each.  When cable goes down (and it already 
> >has) I
> > > have everybody go to the system tray and change SSID's from "cable" to
> > > "DSL."
> > >
> > > Here's where I could use some expertise:
> > >
> > > we have shared drives and printers on our 6-computer home network -- 
> >when 2,
> > > active internet surfer/users move to the DSL router, their resources are
> > > unavailable to those of us who haven't switched over yet.
> > >
> > > This goes back to my original question ~ is there a way to multi-link 
> >both
> > > services so that they are somewhat redundant and serving one network
> > > segment?
> >
> >   Yes, but it's not quite trivial.
> >
> >   You'll need a crossover cable between one of the LAN ports on Router A 
> >and
> >one on Router B.  But before you connect it, you need to make sure their 
> >LAN
> >configurations are compatible and/but not conflicting.
> >
> >   Each one needs its own address on the household segment, and its own 
> >pool
> >of DHCP addresses.  For instance, you might make Router A x.x.x.1, serving
> >up addresses x.x.x.2-x.x.x.127, and Router B x.x.x.254 serving up 
> >x.x.x.128-
> >x.x.x.253.  (If you have printers with their own addresses, modify these
> >ranges to exclude them, or set them up as reservations.)
> >   Once you then install the crossover, all of your devices will be on a
> >single segment, but which gateway they use will depend on who they got 
> >their
> >DHCP info from.
> >
> >   With slightly fancier routers, you could have each forward traffic to 
> >the
> >other if its Internet connection was down, but your routers probably don't
> >support that.
> >
> >David Gillett
> >
> >          PCBUILD maintains hundreds of useful files for download
> >                      visit our download web page at:
> >                   http://freepctech.com/downloads.shtml
> 
>          PCBUILD maintains hundreds of useful files for download
>                      visit our download web page at:
>                   http://freepctech.com/downloads.shtml

         PCBUILD maintains hundreds of useful files for download
                     visit our download web page at:
                  http://freepctech.com/downloads.shtml