>
> I've discovered the /etc/network/interfaces file -- I think I should
> fix things there.
>
>
yes, that is the correct location now
> Side Note:
>
> If /etc/init.d/network has been discontinued and the functionality
> moved to /etc/network/interfaces, perhaps someone should update Debian
Quoth kmself@ix.netcom.com,
> So -- should I configure /etc/network/interfaces, delete
> /etc/init.d/network, and pray everything works from
> /etc/init.d/networking?
I had a machine which somehow managed to get assigned a wrong default
gateway, which was causing me all sorts of grief. I eventual
On Thu, Sep 21, 2000 at 03:01:05PM -0500, will trillich ([EMAIL PROTECTED])
wrote:
> On Mon, Sep 18, 2000 at 06:26:47PM -0700, kmself@ix.netcom.com wrote:
> > Could someone set me straight on the distinction between
> > /etc/init.d/network and the definition files under /etc/network:
> > interfa
On Mon, Sep 18, 2000 at 06:26:47PM -0700, kmself@ix.netcom.com wrote:
> Could someone set me straight on the distinction between
> /etc/init.d/network and the definition files under /etc/network:
> interfaces, options, and spoof-protect.
>
> We've got a balky server which doesn't like coming on-
On 13-Nov-97 [EMAIL PROTECTED] wrote:
>When the system boots /etc/init.d/network is run (I know this is true
>because I added some echo statements & watched the screen while it booted.)
>Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/
>network by hand afterwards, ever
-Original Message-
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Date: Thursday, November 13, 1997 7:19 AM
Subject: /etc/init.d/network
>Howdy all.
>
>I've got one machine that's really got me stumped. I've been with
>Debian since before 0.91 was released
On Thu, 13 Nov 1997 [EMAIL PROTECTED] wrote:
> When the system boots /etc/init.d/network is run (I know this is true
> because I added some echo statements & watched the screen while it booted.)
> Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/
> network by hand afterw
>
> Well...
>
> in the /etc/init.d/network file is the following lines inserted?
>
> /sbin/ifconfig eth0 up
> /sbin/ifconfig eth0 host_name netmask 255.255.255.0
>
> Add the kernel routing table
>
> /sbin/route add -net 198.168.1.0 dev eth0
> /sbin/route add -host host_name dev eth0
>
Here's
>
>
> Hi Chuck,
>
> This sort of thing can happen if you have a domain name in .../networks
> instead of an IP number. Another time it happened to me when I did a
> "tidy-up" of /etc/hosts and removed an important domain-IP pairing.
>
When you say ".../networks" you mean "/etc/networks" - rig
[EMAIL PROTECTED] wrote:
>
> Howdy all.
>
> I've had two network cards in this machine: first, an HP 100VG PCI and
> then an Eagle NE2000 ISA. Both exhibit the same problem. Which is...
>
> When the system boots /etc/init.d/network is run (I know this is true
> because I added some echo state
>
> On Thu, 13 Nov 1997 [EMAIL PROTECTED] wrote:
>
> > I've had two network cards in this machine: first, an HP 100VG PCI and
> > then an Eagle NE2000 ISA. Both exhibit the same problem. Which is...
>
> Are you using them as modules or did you compile the drivers in?
> Just a random guess..
>
Did you try sticking an "ifconfig" in at the end of /etc/init.d/network to
see if the interface is up at that particular moment?
Maybe something else is shutting it down somewhere else ???
Later,
Kevin
-Original Message-
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: debian-user@li
12 matches
Mail list logo
