![]() |
NETWORKING-DSL
FOR DSL ON PPPoE click here
From: arnie asherman1@uswest.net or --
arnie sherman frenomulax@bigfoot.com
Tested on Caldera Open Linux 2.2
arnie wrote:
>
> After several installs (and help from several sources), I
have come up
> with the steps needed to connect through my DSL line w/ a
dynamically
> assigned IP address, in a far simpler and more stable
configuration than
> before. I'd like to offer this up as a Step by Step.
Please take a look
> at this and offer any recommended changes, additions,
etc. I'd
> especially like comments about security, and using a
static IP..
> -----
> This is to help set up DSL access in Linux. Specifically,
this details
> the steps I have taken to configure the following
system:
>
> Pentium 133 PC w/ PCI bus
> 3Com 3C900B-TPO Ethernet Card (PCI)
> Cisco 675 External Router (their documents refer to this
as a 'Router'
> and as a 'Modem')
> Caldera Open Linux 2.2
I'm running a "plain-jane" P60 pc - all ISA/VLB, no PCI, no plug-n-pray. 32M ram, 1.6G HD, CD, 3.5 floppy D-Link D-220 ethernet card (ISA) Motorola cablemodem ("installed" by RoadRunner) Caldera Open Linux 2.2 (tell me how to ID the kernel and I will).
> This assumes you will be
setting up a single machine for access only,
> and do not wish to use it as a gateway for other
hosts.
>
> I am using US West as my access provider. They provide
the card and
> router as their standard package. You can also get an
internal router,
> but I opted for the external. If you use different
hardware, OS Version,
> access provider, or ISP, you may need to adjust these
instructions
> accordingly. In my case, I have installed the card, and
have it working
> properly in Win95. I assume your router is configured and
working
> properly. US West provides assistance in setting up under
windows (but
> not Linux).
RoadRunner Midsouth uses only Motorola equipment. The provided a SMC PCI card with the original install, but it's not usable in this hardware. There is no internal modem available. When I originally asked the tech to install on my NT Server, they weren't sure it was a Windows system.... <g>
> My ISP uses dynamically
assigned IP addresses. If you have a static IP,
> you may need to modify these steps. I am starting from a
fresh install,
> and chose not to configure the ethernet interface during
install.
RR uses 1hr leases on a dynamic system. You normally get the same address every hour, but not if the system is down when your time is up. Very frustrating...
> 1) The 3com card requires the
3c59x module to function. Load it w/
> COAS>Kernel, and enable boot time loading. If you have
a different card,
> use the appropriate module.
>
> 2) Configure the ethernet card, with
COAS>Network>Ethernet Interfaces.
> Adjust the following
> settings:
> a) PNP configuration - leave set at 'Disabled'
> b) Interface Address - change to 10.0.0.2
> c) network mask - leave set to 255.255.255.0
> d) broadcast address - leave set to 0.0.0.255
> e) default route - change setting to enabled, and
enter value 10.0.0.1
> f) change 'Init at boot time' to enabled
When I config my D-Link with COAS, nothing changes, even after reboot. When I return to COAS after rebooting, the original setting have returned.After manual editing /etc/sysconfig/network-scripts/ifcfg-eth0 as per Caldera Knowledge Base Ref#990713-0004, I get the following COAS settings:PNP configuration - disabled.
Interface address - 0.0.0.0
Network mask - 255.255.255.0
Broadcase address - 0,0,0,255
Default route - disabled
Init at boot time - enabled
These settings work, along with the manual changes, and I can access the 'net via eth0 and RoadRunner.
> 3) Restart your computer. You
should now be able to ping 10.0.0.0
> through 10.0.0.2. You should be able to telnet to your
router at
> 10.0.0.1, and log onto the CBOS operating system. You
should also be
> able to telnet to your localhost at 10.0.0.2, if you have
this service
> enabled.
I have no way of knowing (presently) what address has been assigned by RoadRunner to my modem/connection. I can ping any net address I want, tho the times are slower in many cases than the times returned by my 56K dialup NT box.
> 4) In /etc/resolv.conf comment
out the default entries for your local
> machine, and add the following lines, substituting the IP
addresses for
> your ISPs nameservers for xxx.xxx.xxx.x
>
> search
> # primary nameserver
> nameserver xxx.xxx.xxx.x
> # secondary nameserver
> nameserver xxx.xxx.xxx.x
> 5) Restart your computer. You
should now be able to surf w/ Netscape, as
> well as send and receive email, once you have configured
your software.