public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "L. C. Robinson" <lcr@onewest.net>
To: blinux-list@redhat.com
Subject: Re: Verizon DSL with RH 7.2-- Help?
Date: Wed, 15 May 2002 19:45:26 -0600 (MDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0205151835560.1054-100000@rupin.localnet> (raw)
In-Reply-To: <000c01c1fae2$75f025b0$60c3fea9@twrnet.com>

On Mon, 13 May 2002, Dave Hunt wrote,
[concerning his efforts to get DSL to work]:

> Just before rebooting, I moved the file
> "/etc/sysconfig/network-scripts/ifcfg-eth0" to my root
> directory, so the Ethernet device wouldn't come up at boot

Humm....  I don't have DSL, and don't use rp-pppoe, so I can
only make some general observations about the "ifcfg-eth0"
config file, which we can hope can put you on the path to
a solution.  Red Hat uses the /sbin/ifup bash script to bring
up various network interfaces, such as eth0 (the first ethernet
card interface).  ifup is, in turn, used by other GUI utilities,
and by the boot scripts (eg, /etc/rc.d/init.d/network), etc.
If you check through these two scripts, you will see that they
check the ifcfg-eth0 file for a variable "ONBOOT=yes|no" to see whether
to bring up the interface at boot time.  If ifcfg-eth0 is
missing, you will likely be unable to bring up eth0 at all,
at least through the normal redhat utilities.  Does the Roaring
Penguin package provide an alternative script and config setup?
Probably not, since they have apparently provided rpm packages
for Red Hat; they likely follow the usual conventions.

Anyway, the network config files (and some others) are documented
in /usr/doc/initscripts-*/sysconfig.txt (or is it
/usr/share/doc/...), including the ifcfg-<interface-name> ones,
so that may help in terms of text mode configuration.  Note that
the ifup script is also documented here (you might just say "ifup
eth0", perhaps, to connect, once everything is configured right)?

Hope this helps, LCR

Complete original question follows (lengthy):

On Mon, 13 May 2002, Dave Hunt wrote:

> I downloaded the latest i386 rpm of rp-pppoe (a user-space
> PPPOE client from Roaring Penguin).  My Redhat system shipped
> with a corrupted copy of this package.  I replaced it with the
> new copy, (uninstalled the bad, and installed the new with "rpm
> -Uvh).

> Next, I ran the provided setup script.  It asks a few
> questions, and modifies several configuration files.  The files
> got modified as I'd been led to expect.  Using the Redhat setup
> tool, I turned off unnecessary services, like dhcpd, httpd, for
> instance.  Just before rebooting, I moved the file
> "/etc/sysconfig/network-scripts/ifcfg-eth0" to my root
> directory, so the Ethernet device wouldn't come up at boot
> time, with the "pump" dhcp client.  Finally, I restarted.

> Using the Rp-PPPOE, one is supposed to bring up the ADSL
> connection with "ADSL-start".  When I do this, It tries to
> connect, and quits with a "timeout" error.  What may I have
> missed?  Any help is appreciated.

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid





  reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Dave Hunt
 ` L. C. Robinson [this message]
   ` Dave Hunt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0205151835560.1054-100000@rupin.localnet \
    --to=lcr@onewest.net \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).