RE: DSL Help

[<karlp ourldsfamily com>]

Okay, I've pasted the text to the bottom and the link where it was found is
after that. You'll need to switch DNS servers they list and everywhere you
see XMission, change that to your ISP. Also, if you want to open some
incoming ports, here's the commands on the Cisco to do that. If you have/get
a different router, then the syntax will be slightly different:

set nat entry add out.side.IP.addr 25 10.0.0.254 25 tcp

That will set incoming email to be delivered to your inside mail server at
IP 10.0.0.254. This will only work if you have a static IP for the
out.side.IP.addr . . .

Most good routers give you help each step of the way in a command. On my
Cisco, if I type set ? it gives me the available options after that. So, if
I type set nat ? it then shows entry as one of the options, etc...

Good luck. (I cced the list so anyone else can give corrections of
whatever I may have missed.

KLP

On Fri, 1 Mar 2002, Mugleston, Brad wrote:

Karl,

How about a little pointing?

Thanks for the response.

Brad





Individual DSL Configuration for Cisco 675 in PPP

Your IP:

Connect a management serial cable to the back of the DSL box's "MGMT" port.
This cable should then be connected to a serial port on a computer with
terminal software (ie: Hyperterminal, ZTerm, Minicomm, Telix).  The speed
the terminal software will communicate with the box will be either 9600 or
38400, no software or hardware handshaking.

If there is a "login:" prompt, type "root". At the password prompt on the
terminal, just hit ENTER for the password (there is none).  Type "enable",
then hit ENTER.

Type "show version".  The box requires v2.0.1 or higher for proper PPP
operation.  XMission recommends v2.4.3.  This is available for customer FTP
by logging into "ftp.xmission.com" with customer's account and password then
changing to the "/archive/dsl" directory.  Instructions for upgrading are
contained within the README file.  It is recommend that customers upgrade
after they get their PPP connected, if they are already on v2.0.1 or higher.

Issue the following commands to the DSL box prompt:

 set ppp wan0-0 ipcp 0.0.0.0
 set ppp wan0-0 login (xmission account name)
 set ppp wan0-0 password (xmission account password)
 set ppp restart enabled
 set bridging rfc1483 off

 set nat enabled
 set interface eth0 address 10.0.0.1
 set interface eth0 netmask 255.255.255.0

This will allow the use of IP addresses 10.0.0.2 - 10.0.0.254 for their
internal machines.  If they desire to have servers running, they will need
to setup static NAT mappings in their DSL box with "set nat entry".

The CBOS version v2.2.0 will not allow telnet from any source until
passwords have been set for both "exec" and "enable" modes.  Earlier
versions allow telnet, and in fact will allow any access to it's
configuration unless password protected.  In both circumstances, XMission
recommends you set passwords for your router with the following commands:

 set password exec (pick a password for the box)
 set password enable (pick an admin password for the box)

As a result of the Code Red worm discovered in July of 2001, we are now
recommending that all users turn off their web administration interface:

 set web disabled
 set web port 8081

Finally, save everything and reboot:

 write
 reboot

Pointing the computer to the Cisco is fairly easy.

Windows users, in the network control panel, go to the properties of your
ethernet card.

In the "IP Addressing" tab, click "specify an Ip address" and enter
"10.0.0.2"  (or .3, .4 or any number up to .254). In the "netmask", enter
"255.255.255.0".  The gateway needs to be set to the router IP of 10.0.0.1.
Switch to "DNS configuration" and enter 198.60.22.2 and 198.60.22.22 in the
"DNS Server Search Order", and "xmission.com" in the 'Domain suffix Search
Order".

Press "OK".  The computer will reboot and log on.

Mac users, in the TCP/IP control panel, select your Ethernet card, and
configure "Manually". Enter the IP 10.0.0.2 (or .3, or .4 or any number up
to .254), the netmask 255.255.255.0, and the gateway 10.0.0.1.  Specify the
name servers 198.60.22.2 and 198.60.22.22, and xmission.com in the domain.

The XMission side needs to be configured before the customer can connect


This page was found at:
http://www.xmission.com/help/dsl/cisco675indi.txt