Article View: ak.os.linux
Article #174Re: damn @home cable modem....
From: Wayne Gabler
Date: Tue, 21 Dec 1999 00:00
Date: Tue, 21 Dec 1999 00:00
232 lines
8728 bytes
8728 bytes
On Mon, 20 Dec 1999 20:44:25 GMT, "DRE4D" <dre4d@home.com> wrote:
KPLUG Home
Cox@Home and Linux
------------------------------------------------------------------------
mini-HOWTO for cable modems and Cox@Home Written by: Neil Schneider
This document shows the steps I used to get Cox@Home configured under
Linux.
The first step is to configure the ethernet card to use with the cable
modem. If you already have a network configured, and don't want to
expose
your whole network to the Internet, you may choose to add a second
card.
The ethernet HOWTO has information on configuring two interfaces. The
LILO
documentation including the LILO - Mini HOWTO tells how to use the
append=
line in /etc/lilo.conf to automatically probe for the second card.
Then set
up the second card. It may be necessary to remove the first card to
run the
configuration software for the second card. Then replace the original
card.
Once both cards are properly configured add the line
append="ether=0,0,eth1" to the end of the paragraph in /etc/lilo.conf
which
applies to Linux. Run lilo, and reboot and test whether Linux
recognizes
the new card. You can do this by looking in the Control Panel, Network
Configuration and both cards should show up there. If you aren't using
X-windows you can use the ifconfig program. From the command line just
issue the command ifconfig and all your interfaces should show. Check
man
ifconfig for information.
Next step is to configure the IP address using either ifconfig or the
Network Configuration tool in Control Panel.
First I will describe using the Network Configuration tool . Call
Control
Panel then double click on the Network Configuration Icon. With
"Names"
highlighted , add your DNS name in the box for Hostname. Then add the
domain name in the proper box. Next go to the names section, and add
the IP
addresses for the Primary and Secondary DNS Server. They should be
listed
on the printout that you were given when they installed your cable
modem.
These are the servers that convert names, like www.kernel-panic.com to
IP
addresses.
If you're not using X-Windows, then go to /etc and using your favorite
editor, edit the file /etc/sysconfig/network. It should look similar
to
this
NETWORKING=yes
HOSTNAME=YOURHOSTNAME
DOMAINNAME=domain.im.in.home.net
GATEWAY=###.###.###.1 (your IP address with the last number changed to
1)
GATEWAYDEV=ethX (the ethernet device connected to your cable modem)
Then you need edit /etc/resolv.conf. The data in this file tells your
internet applications where to send DNS inquiries. The first line
tells
which domain to look in and has a format like search
domain.im.in.home.com
The next lines are for the DNS servers. The format is
nameserver ###.###.###.###
where ###.###.###.### is the IP address for the DNS server on
domain.im.in.home.com. (Replace domain.im.in.home.com with your real
domain.) Next is the hosts section. Using the Red Hat Network
Configuration
tool, click on add and enter your IP address and your name, I used the
DNS
name that Cox@Home gave me and then a nickname, if you want one.
Without X-Windows, use you editor to edit /etc/hosts. It looks similar
to:
IP Address Hostname Alias
127.0.0.1 localhost. localhost.localdomain
###.###.###.### YOURHOSTNAME
AN.ALIAS.FOR.YOURHOSTNAME
Next comes the interfaces section. With the Red Hat Network
Configuration
tool, click on add. A dialog box will appear. Choose ethernet. Enter
your
IP number and Netmask and the network and broadcast addresses should
be
filled in automatically. Then choose, whether you want the interface
to
come up at boot time and if you want any user to be able to
activate/deactivate the interface. In Interface configuration
protocols
choose none. You're finished with this section.
From command line, go to /etc/sysconfig/network-scripts/ifcfg-ethX,
where
ethX is the device connected to your cable modem. Edit this file,
DEVICE=ethX The name for your device
USERCTL=yes
ONBOOT=yes If you want the interface to come up when you boot
BOOTPROTO=none
BROADCAST=###.###.###.### This should be given in your documentation
NETWORK=###.###.###.### Same as your IP address, with last number 0
NETMASK=255.255.255.0 Check you documentation, this should be
correct
IPADDR=###.###.###.### Your IP address
Now we move to routing. In the Network Configuration set the default
gateway to your IP address from Cox@Home and default gateway device to
the
device connected to your cable modem. Use the add function and enter
ethX ,
The designation for this device the network address, The same as your
IP
address with the last number changed to 0 and netmask and then for
gateway,
your IP address again. If the interface doesn't appear activated in
the
interface section, make it so.
From command line, go to /etc/sysconfig/static-routes
ethX Your interface device net ###.###.###.### Your IP address
netmask 255.255.255.0 This should be the same, check you
documentation gw ###.###.###.###
Your IP address, this make it the gateway device
To activate the new settings from the command line, go to
/etc/rc.d/init.d
and issue the command ./network stop and then ./network start
Now, go to an xterm, or from the command line ping your modem by
typing
ping xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is your IP address. After
about
4 lines hit Ctrl C . Unless you get a network unreachable message,
your
computer is recognizing your modem.
Next ping your Default gateway, same command but now the
xxx.xxx.xxx.xxx is
the IP for the Default Gateway. The default gateway IP address is
usually
the same as yours with the number after the last "." set to 1.
Now test your two DNS servers. This can be done by issuing the command
nslookup with your assigned DNS name as the argument. If all this
succeeds
you should get a response like :
[me@my_computer]# nslookup YOUR_DNS_NAME
Server: LOCAL_SERVER.sdca.home.com
Address: xxx.xxx.xxx.xxx
Non-authoritative answer:
Name: YOUR_DNS_NAME.LOCAL_PROXY_SERVER.sdca.home.com
Address: xxx.xxx.xxx.xxx
You can check the secondary DNS server by using the command nslookup
-query
xxx.xxx.xxx.xxx host where xxx.xxx.xxx.xxx is the IP address of the
secondary DNS server and host is the DNS name of your machine. For
more
information on nslookup see man nslookup
You're all set. Don't forget to set your mail server name and news
server
name, in their associated software. Cox uses mail and news
respectively,
but to make them work properly you may have to add the SubDomain to
these.
You may want to check the Network Administrator's Guide (NAG for
short) for
help with some of these issues. On my Red Hat system it's available in
HTML
format for reading from a browser in
/usr/doc/HTML/ldp/nag-1.0/index.html.
It's also available from O'Reilly as the Linux Network Administrator's
Guide.
------------------------------------------------------------------------
Related Links
* Phil Karn's Roadrunner page.
* Christopher Seawood's Linux RoadRunner Setup page.
* Marke Wolfe's Configuring Redhat Linux for Southwestern Cable's
RoadRunner Service.
* Cable Modem mini-HOWTO.
* DHCPcd mini-HOWTO.
* The IP Masquerade mini-HOWTO. See Phil Karn's RR page for more
masquerade links.
* The sdnet.cablemodems newsgroup.
* The Cox@Home and RoadRunner homepages.
------------------------------------------------------------------------
Howard C. Griffith
Modified: 03-Jun-1999
>ok here it is
>i have @home service but i cant connect out with 'nix
>looked in config.moduals...sees the card
>disabled pnp
>even manulaly added the configuration for my dhcp
>got localhost.localdomain set right
>wtf
>when i boot it freezes on starting interface eth0
>for like 5 mins
>then it just fails and continues
>any ideas?
>
Technical Details
Message-ID:
<385ee2f0.5548164@news>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<Jyw74.61602$ri.243938@news1.rdc1.bc.home.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f92c8,acaefd79169e07bf X-Google-Attributes: gidf92c8,public From: wgabler@home.com (Wayne Gabler) Subject: Re: damn @home cable modem.... Date: 1999/12/21 Message-ID: <385ee2f0.5548164@news> X-Deja-AN: 563235526 Content-Transfer-Encoding: 7bit References: <Jyw74.61602$ri.243938@news1.rdc1.bc.home.com> Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@home.net X-Trace: news1.rdc1.ab.home.com 945742635 24.64.112.115 (Mon, 20 Dec 1999 18:17:15 PST) Organization: @home Network MIME-Version: 1.0 NNTP-Posting-Date: Mon, 20 Dec 1999 18:17:15 PST Newsgroups: ak.os.linux