In comp.sys.mac.system Semesiente <semesiente_WITHOUT_THIS@terra.es> wrote:
> Is it possible to have a LAN with two routers, each one connected to a
> different DSL line?
[quoted text clipped - 7 lines]
> desired router IP address in the router field of the Network preferences
> pane of each Mac.
Only if DHCP is out of the picture, I believe. As you've described it,
things should work fine. The complication with DHCP is that the discovery
part is done via broadcasts - if a connecting client goes to renew its
DHCP lease and there's more than one router offering DHCP services on
the network, chaos will ensue. Manual configuration should resolve this.
Other than that, each peer on the 192.169.1.xxx network should be an
equivalent member, and play happily.

Signature
*--------------------------------------------------------*
| ^Nothing is foolproof to a sufficiently talented fool^ |
| Heath Raftery, HRSoftWorks _\|/_ |
*______________________________________m_('.')_m_________*
Semesiente - 27 Sep 2006 09:46 GMT
Thanks a lot for your help, Heath. I wasn't planning to use DHCP but
static addresses.
But, according to what you say, the problem arises when there's two DHCP
servers. Thus, my setup maybe could work even with half of the Macs with
static addresses connected to a router with the DHCP disabled and the
other half of them connected to the other router with DHCP enabled and
getting addresses dinamically. If this scenario works, all I would have
to do is limit the range of dinamically provided addresses to avoid them
interfering with the static ones.
What do you think?
In article
<451a3154$0$4670$61c65585@un-2park-reader-01.sydney.pipenetworks.com.au>
,
> In comp.sys.mac.system Semesiente <semesiente_WITHOUT_THIS@terra.es> wrote:
> > Is it possible to have a LAN with two routers, each one connected to a
[quoted text clipped - 17 lines]
> Other than that, each peer on the 192.169.1.xxx network should be an
> equivalent member, and play happily.

Signature
Semesiente
Heath Raftery - 27 Sep 2006 10:59 GMT
In comp.sys.mac.system Semesiente <semesiente_WITHOUT_THIS@terra.es> wrote:
> Thanks a lot for your help, Heath. I wasn't planning to use DHCP but
> static addresses.
[quoted text clipped - 8 lines]
>
> What do you think?
I think you are right. I'm interested to hear how you go, or
what others think.

Signature
*--------------------------------------------------------*
| ^Nothing is foolproof to a sufficiently talented fool^ |
| Heath Raftery, HRSoftWorks _\|/_ |
*______________________________________m_('.')_m_________*
Semesiente - 27 Sep 2006 12:42 GMT
I will try it as soon as I have the second access.
In article
<451a4b68$0$4670$61c65585@un-2park-reader-01.sydney.pipenetworks.com.au>
,
> In comp.sys.mac.system Semesiente <semesiente_WITHOUT_THIS@terra.es> wrote:
> > Thanks a lot for your help, Heath. I wasn't planning to use DHCP but
[quoted text clipped - 12 lines]
> I think you are right. I'm interested to hear how you go, or
> what others think.

Signature
Semesiente
Semesiente - 27 Sep 2006 17:46 GMT
It works. I can have one the routers providing IP addresses through DHCP
and the other one with DHCP disabled. Both routers connected to a
switch. I can even duplicate the Build-in Ethernet network location and
activate and deactivate this new location so a Mac uses one router or
the other. Great!
In article
<semesiente_WITHOUT_THIS-97F95A.13423627092006@news.gazeta.pl>,
> I will try it as soon as I have the second access.
>
[quoted text clipped - 18 lines]
> > I think you are right. I'm interested to hear how you go, or
> > what others think.

Signature
Semesiente
Paul Sture - 27 Sep 2006 13:15 GMT
In article
<451a4b68$0$4670$61c65585@un-2park-reader-01.sydney.pipenetworks.com.au>
,
> In comp.sys.mac.system Semesiente <semesiente_WITHOUT_THIS@terra.es> wrote:
> > Thanks a lot for your help, Heath. I wasn't planning to use DHCP but
[quoted text clipped - 12 lines]
> I think you are right. I'm interested to hear how you go, or
> what others think.
I can certainly attest to the problems arising when two DHCP services
are offered on the same LAN, particularly when the one you don't want
lands you on a completely different subnet :-(
I nail my systems down to a fixed IP address as a matter of course,
making sure that the addresses I pick are outside the range offered by
DHCP (and maybe switch DHCP off altogether if the given router allows
it).
DHCP can be useful if you have visitors who want to connect their
laptops to the outside world, an internet cafe being a good example, but
I see little use for it in a home or office environment.
In the OP's situation I would simply make sure that each system is set
to use the required router in the Network Settings panel.

Signature
Paul Sture