RE: [TCLUG:9401] Cisco 675 questions

[Andrew Dubman <adubman@bellmicro.com>]

I have just that setup.  If you connect directely to the 675, use the cross
cable (it's yellow).

If you go thru a hub or switch, use normal ethernet cable.
As the 675 does DHCP and NAT, it doesn't care how many computers are on it. 

AS Jeremy Smith said, DHCP does NAT so there's no need for anything else to
do IP masquerading.

I have a Window$ machine, a Sparc 20 running RH6 and a PC running RH6 all on
at the same time, It works real schweet.

Andy
adubman@bellmicro.com
adubman@uswest.net
+++++++++++++++++++++++++++

-----Original Message-----
From: psp@printwareinc.com [mailto:psp@printwareinc.com]
Sent: Monday, October 25, 1999 11:51 AM
To: tclug-list@mn-linux.org
Subject: [TCLUG:9401] Cisco 675 questions


When I installed my Cisco 675 router during installation of my USWest ADSL
line, it was clear that it was configured as a DHCP server. My sole client
computer was configured as a DHCP client, and wwas assigned 10.0.0.1 at
boot. Hmmm, why not get a hub, connect more clients and have them all share
the connection?

USWest says that I can connect multiple clients, but they won't help out on
any internal network problems I may encounter. (The tech I talked with said
I needed a crossover cable going from the Cisco to my hub, then changed his
mind...which is it?)

In this situtation, why do I need a separate box for IP Masquerading? I know
lots of you have worked hard to set up IP Masq boxes on your ADSL lines, so
I assume are other benefits than simply sharing the connection. Is the
USWest Cisco configuration "standard" throughout USWest, or could it be that
say, St. Paul uses one setup, Mpls another, etc.

Phil Plumbo
St. Paul




---------------------------------------------------------------------
To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
For additional commands, e-mail: tclug-list-help@mn-linux.org