Tony Nugent wrote:
(I wish you had improved the formating here :-)
I do apologize for that.
>
> 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?
Maybe, maybe not...
When I did the above "...stop", I got : "Disabling IPv4 automatic
defragmentation [ OK ] "
When I did the above "...start", I got: "Bringing up interface lo"
no mention of trying to bring up eth0.
>
>
> Also, try this:
>
> ifdown eth0
> ifup eth0
OK, things are getting more interesting at this point. ( Note, I'm doing all
these in this exact order )
I executed "ifdown eth0" and it hung up on the command line, and never
returned to the prompt.
But....... I shifted back into Gnome, brought up the Connection Interface
Dialog, selected eth0, pressed OK, and it immediately went online, just like it
would if I selected my modem connection. The dialog box did not hang up this
time, I suspect because the command "ifdown eth0" actually did initialize eth0.,
even though it hung and would not return the command prompt.
>
>
> Perhaps you need entries for your IP addresses in /etc/hosts ?
I don't understand. I don't have IP addresses to enter, as they are assigned
differently each time I log on by the server. In fact, I double-checked with my
ISP on this, and they confirmed this fact. Only the DNS Primary and Secondary's
can be used.
>
>
> > 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.
Yeah, I figured, but when you're learning, a ton of documents and HOWTO's keep
reiterating to use the GUI's like NetConfig, LinuxConf, etc for your work. Most
of the stuff you're showing me now I have never seen, nor do I have any
explanations of how to do this manually in my 5" stack of printed-out documentaion
I am regularly adding to. Between the help that Donald Becker gave me to get my
tulip driver working with my ethernet card, and the help you are giving me now, I
will have to write several pages of notes on how to do these things, or, God
forbid, my system crashes and I have to remeber all this stuff. ( No way, Jose...
)
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.
That was my goof, I couldn't find an explanation of what to put here, or when,
so I stuck something in there.
>
>
> Your hostname there should be a fully qualified domain name.
( ...hand goes up ) Ok, my ISP is "frontiernet.net", is that a fully
qualified domain name?
I consulted my Linux Install and Configuration Little Black Book, but that
doesn't explain this.
>
>
> The reason I don't like most config tools is becoming obvious, it
> hides what is really going on.
I'm new to Linux, but not new to computers. I started out programming in Basic
27 years ago, was raised on DOS, and spent the last 16 years programming
semi-professionaly in C++, so I too really like to know whats going on in the
background, and have a higher level of comfort at the command line. In fact,
truth be told, I installed Linux for the primary purpose of putting my C++ skills
to work developing Linux applications of some sort, but I haven't got to that
point yet, as I've spent all my time getting (or trying to...) my hardware to
work. Printers, sound, CD-ROM, modem, DSL, etc. It's not so bad. I'm still
learning important things I need to know, but what a learning curve this is
turning out to be......
Anyhow, back to business... I will change those two files as you suggested, plus
whatever else you asked me to change. Do you have an idea why it's hanging up
yet? I really think we're very close.
Thanks,
Robert
P.S. - I not sure of proper procedure here, but I've been copying the mailing list
so our work can benefit others. Hope that's considered proper.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
