Dan,

As root, run netconf and make sure you are using dhcp for your ethernet 
card. Click the "Host name and IP network devices" button. In the next 
dialog, click the "Adapter 1" tab. The Enabled box should be checked 
(indented), and Dhcp should be selected. The Net device should show eth0, 
and the Kernel module should show your NIC driver (eepro100, for the Intel 
Pro/100 NIC I received from Qwest). Accept any changes.

Next, click the "Name server specification (DNS)" button. You should have 
Qwest's domain name server IP addresses in the text boxes for "IP of name 
server 1" and "IP of name server 2". If not, enter them. If you don't 
know, use 204.147.80.1 for the first, and 204.147.80.5 for the second. You 
do NOT need to check the "DNS is required..." box. Accept any changes.

Quit netconf. If you made any changes, then netconf should prompt you to 
restart networking. If it doesn't, you will need to do it manually (in a 
terminal, as root):
        /etc/rc.d/init.d/network restart

If the command fails, then read the error message. It may be that dhcpcd 
(the dhcp client daemon) is not installed, and therefore you are unable to 
use dhcp to get your network config. If this is the case, run rpmdrake and 
install dhcpcd. Then start networking again, as with the restart command 
above.

If you're not sure, try locate dhcpcd. My output looks like this:

[root@numidea dave]# locate dhcpcd
/etc/dhcpc/dhcpcd-eth0.cache
/etc/dhcpc/dhcpcd-eth0.info
/var/run/dhcpcd-eth0.pid
/usr/share/doc/dhcpcd-1.3.19pl1
/usr/share/doc/dhcpcd-1.3.19pl1/README
/usr/share/man/man8/dhcpcd.8.bz2
/sbin/dhcpcd
[root@numidea dave]#

Note the last item, /sbin/dhcpcd. This is the actual program you need.

If you have dhcpcd installed and running, then in a terminal, run 
ifconfig. You output should look something like this:

[root@numidea dave]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:03:47:1B:EC:68
          inet addr:10.0.0.2  Bcast:10.0.0.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING  MTU:1500  Metric:1
          RX packets:17014 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5943 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:10 Base address:0xd400
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:46 errors:0 dropped:0 overruns:0 frame:0
          TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
 
[root@numidea dave]#  

Note the IP address of device "eth0". If you only have "lo" but no "eth0", 
then your network card isn't initialized -- probably because the dhcp 
client is either not installed, or not running, or else the driver module 
failed to load. If you know which module your NIC needs, try "modprobe 
<modulename>". If you get an error message, troubleshoot -- wrong module? 
hardware conflict? module already loaded (this one is ok, that means the 
driver is already running)? Try restarting networking again (see command 
above).

Next, run route -n. Here's my output (sorry about the column formatting):

[root@numidea dave]# route -n
Kernel IP routing table
Destination  Gateway   Genmask         Flags Metric Ref    Use Iface
10.0.0.0       0.0.0.0     255.255.255.0   U        0      0       0   eth0
127.0.0.0     0.0.0.0     255.0.0.0           U       0      0      0   lo
0.0.0.0         10.0.0.1   0.0.0.0              UG     0      0     0 eth0
[root@numidea dave]#  

See the third line, starting wiith 0.0.0.0 -- this is your default route. 
Notice that it is linked to eth0 (last column). Notice the Gateway column. 
The Gateway entry is the internal IP of your Cisco 678 router. It might 
not be 10.0.0.1, I don't know if Qwest configures them all the same or 
not. But if you have a default gateway entry, then it is timie to try and 
get online. Just launch Netscape.

Hopefully a page will load. If not, then try pinging 64.37.137.83 
(www.sony.com). If you can ping the IP address, then at least you are 
hitting the web. It's a domain resolution problem. If you can't even ping 
the IP, try another known IP address, like those DNS entries I gave you 
above. If you are still stuck, then you aren't even getting outside your 
router, and possibly not even outside your PC. Try pinging your router 
(the Gateway IP address). If you can't get it, then you are stuck inside 
your PC. Time to read the Networking HOWTO and see if it can help you :-)

Good luck,
Dave

On Friday 06 April 2001 20:58, thus spake Dan Sampsel:
> Dave-
> I have switched over to the Cisco, since the internal (infernal) Intel
> 2100 would not provide net access for Linux. Where am I falling down in
> the configuration process?
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dave Sherman
> Sent: Friday, April 06, 2001 6:21 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [newbie] ADSL setup
>
>
> I am using Qwest DSL and Mandrake 7.2 at this very moment. So I know it
> works. Question: do you have the Cisco 67x router, or just the internal
> NIC? I am running the Cisco, which has its own DHCP server built-in. I
> had to configure the DHCP server to provide my DNS servers and default
> gateway. I set both my Windows and Mandrake boxes to use DHCP, and
> everything works perfectly.
>
> Dave
>
> On Friday 06 April 2001 19:54, Dan Sampsel wrote:
> > I've installed LM 7.2. I'm having a devil of a time setting up my ADSL
> > connection. Everything is functioning in MacroHard. I'm using
> > qwest.net's DSL services. A call to "tech support" yielded the
> > standard "we don't support Linux". Fine. He told me that he "doesn't
> > think" they use PPPoE, only DHCP. Great. When I setup ADSL in Linux &
> > try to fire up Netscape, I keep getting "server not found" message.
> > Trying to change Linux to DHCP+PPoE, it responds by telling me I'm
> > currently connected to the internet and gives me 2 options. A.
> > Disconnect, or, B. Change my configuration. What simple problem am I
> > overlooking?
> >
> > Daniel T. Sampsel
> > [EMAIL PROTECTED]
>
> --
> "...[W]e preach Christ crucified: a stumbling block to Jews and
> foolishness to Gentiles, but to those whom God has called, both Jews and
> Greeks, Christ the power of God and the wisdom of God." (1 Cor 1:23-24)

-- 
"...[W]e preach Christ crucified: a stumbling block to Jews and
foolishness to Gentiles, but to those whom God has called, both Jews
and Greeks, Christ the power of God and the wisdom of God."
(1 Cor 1:23-24)

Reply via email to