On Thu May 11 2000 at 17:23, Robert Krueger wrote:

The reasons for your problems are now becoming evident...

>   Now, I started the DSL in Gnome by selecting the eth0 interface connection,
> which froze the connection box, but it started DSL anyway.   Here's the
> result of ifconfig at this point:

Looks good.

>    Again, here is the routing tables before bringing up the DSL connection:

>    Now here it is -after- the DSL is up:

(I wish you had improved the formating here :-)

>    Kernel IP routing table
> Destination     Gateway      Genmask          Flags Metric Ref Use Iface
> 64.209.10.12    0.0.0.0      255.255.255.252  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         64.209.10.13 0.0.0.0          UG    0      0   0   eth0

Looks fine.

>    Here is the content of the /etc/conf.modules file.
> 
> alias parport_lowlevel parport_pc
> alias eth0 tulip
> alias sound emu10k1

That also looks good.

>  Ethernet 0 is obviously not being initialized at boot time, because it hangs
> up during the initialization attempt, and won't continue the boot process.

Hmm.

What happens if you do this (call the rc scripts directly):

        /etc/rc.d/init.d/network stop
        /etc/rc.d/init.d/network start

Does this work with no complaints?

Also, try this:

        ifdown eth0
        ifup eth0

Perhaps you need entries for your IP addresses in /etc/hosts ?

> This would be my preferred way of doing this.
>   The other way is to go into Gnome, and start the Interface Connection
> dialog, and choose eth0.   When I do this, it performs similarly to the boot

gnome?  No, it isn't gnome that you are using (gnome is simply a glorified
window/task manager), but an application (probably linuxconf) that has been set
up to be started from gnome.

> process, ie, it hangs up the Interface Connection Dialog, but when I

I'm wondering if it

> Right-Click to forciby close the Dialog, my DSL is up and running fine.   The
> question of why it doesn't start up smoothly is why I'm here

Forget that brain-dead piece of **it of a config tool.  It is misleading.

> Also, I took note of  your "magic files".  I don't know exactly what to do
> with these, but I felt I should include the content of both for you to look
> at.  They are both very interesting.  This must be what Network Configuration
> Utility deals with...

YES!!  This is where the REAL configuration is done.  All that gui tool does is
write them.  Have a look at /etc/rc.d/init.d/network and you will
see that the config files in /etc/sysconfig/* are SOURCED by it.
These files are simply shell script fragments that set environment
variables.

> Anyhow, here's the result of /etc/sysconfig/network
> 
> NETWORKING=yes
> FORWARD_IPV4=no
> HOSTNAME=RAC
> GATEWAY=209.130.221.121
> GATEWAYDEV=eth0

That's all you need to specify.  Get rid of the IPX crap that
linuxconf puts in there (unless, of course, you are using IPX
networking - which you aren't).

Your gateway address doesn't match.  That would be a problem.
Comment it out, let dhcpd set this for you.

Your hostname there should be a fully qualified domain name.

> And here's the content of /etc/sysconfig/network-scripts/ifcfg-eth0
> 
> DEVICE="eth0"
> ONBOOT="no"
> BOOTPROTO="dhcp"

Thats' probably all you need in this file.

> Thankyou again for your help

The reason I don't like most config tools is becoming obvious, it
hides what is really going on.

Cheers
Tony
 -=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
  Tony Nugent <[EMAIL PROTECTED]>    Systems Administrator, RHCE
  GrowZone OnLine       (a project of) GrowZone Development Network
  POBox 475 Toowoomba Oueensland Australia 4350    Ph: 07 4637 8322
 -=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to