public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter <heisspf@skyinet.net>
To: chuck@gelm.net
Cc: ray@comarre.com, linux-newbie@vger.kernel.org
Subject: Re: Netconfig Fail
Date: Sat, 8 Oct 2005 11:22:02 -0400	[thread overview]
Message-ID: <20051008112202.1589c0c3.heisspf@skyinet.net> (raw)
In-Reply-To: <43465A15.5090708@gelm.net>

On Fri, 07 Oct 2005 07:20:53 -0400
chuck gelm <chuck@gelm.net> wrote:

> Hi, Peter & Ray:
> 
>   Peter, if you add this line to /etc/rc.d/syslog.conf,
> 
> local0.*     /var/log/dhcpcd.log

Does not like the command: command not found.

If I separate local 0.* I get: "not valid identifier"

> 
>   then when you 'dhcpcd -d eth[01] it will put debug lines
>   into /var/log/dhcpcd.log  (See 'man dhcpcd')

Saw it, unfortunately it does not work.

> > Yes neither in Fedora nor in DSL had I to enter anything. In Fedora I just
> > had to activate eth1, eth0 was taken by the onboard LAN card.
> 
>   It seems to me that Fedora is finding your add-on PCI card and
> assigning it eth0, yet Slackware is assigning it eth1 !?
> 
>   I expected, since you disabled the on-board ether device,
> all distributions would only find a 'eth0'.
> 
>   So, if Slackware assigns it 'eth1' and your rc.inet1.conf assigns
> DHCP to eth0, it will not work.

Slackware assigns eth0, not eth1. It is Fedora which still reads both since info stored in a file, activates then eth1 correctly for the external LAN card.
 
>   Run dhcpcd from a console. If Slackware sees your PCI NIC as eth1;
> dhcpcd eth1

Running dhcpcd eth0 from the consoles does nothing. Just sits for a while and returns to command mode.

>   If that works, you can either edit rc.inet1.conf or add
> 'dhcpcd eth1' to rc.local.
> 
> HTH, Chuck


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  parent reply	other threads:[~2005-10-08 15:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06 13:15 Netconfig Fail Peter
2005-10-06  7:33 ` Ray Olszewski
2005-10-07 16:23   ` Peter
2005-10-07  5:49     ` Ray Olszewski
2005-10-07 11:20     ` chuck gelm
2005-10-07 17:23       ` Ray Olszewski
2005-10-08 15:43         ` Peter
2005-10-08 15:22       ` Peter [this message]
2005-10-07 11:36     ` chuck gelm
2005-10-08 15:39       ` Peter
2005-10-08  4:18         ` Ray Olszewski
     [not found] ` <200510052204.15272.david@fierbaugh.org>
2005-10-06 14:54   ` Peter
2005-10-06 12:53     ` David Fierbaugh
2005-10-06 18:52 ` chuck gelm
  -- strict thread matches above, loose matches on Subject: below --
2005-10-08 18:33 Peter
2005-10-08 16:01 ` Ray Olszewski
2005-10-09  1:33   ` Peter
2005-10-09  7:04     ` Peter
2005-10-09 15:29     ` Peter
2005-10-09 18:00       ` chuck gelm
2005-10-09  7:08 Peter

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=20051008112202.1589c0c3.heisspf@skyinet.net \
    --to=heisspf@skyinet.net \
    --cc=chuck@gelm.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ray@comarre.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