From: CaT <cat@zip.com.au>
To: Dragan Stancevic <visitor@valinux.com>
Cc: Andrey Savochkin <saw@saw.sw.com.sg>, linux-kernel@vger.kernel.org
Subject: Re: eepro100 + 2.2.18 + laptop problems
Date: Tue, 20 Feb 2001 09:42:19 +1100 [thread overview]
Message-ID: <20010220094219.F365@zip.com.au> (raw)
In-Reply-To: <20010211224033.G352@zip.com.au> <20010213092638.A11218@saw.sw.com.sg> <20010213151409.Q352@zip.com.au> <20010220092106.D365@zip.com.au> <20010219153702.C24311@valinux.com> <20010220093301.E365@zip.com.au> <20010219154410.A10730@valinux.com>
In-Reply-To: <20010219154410.A10730@valinux.com>; from visitor@valinux.com on Mon, Feb 19, 2001 at 03:44:10PM -0800
On Mon, Feb 19, 2001 at 03:44:10PM -0800, Dragan Stancevic wrote:
> On Tue, Feb 20, 2001, CaT <cat@zip.com.au> wrote:
> ;
> ; None. This is before any traffic gets put through it. At worst the
> ; card has the wrong IP for the network but that is not always the case
> ; from memory.
>
> So where does that card get the address from, are you doing DHCP?
Set manually. In debian-speak: ifup eth0 where:
iface eth0 inet static
address 10.1.1.2
netmask 255.255.255.0
network 10.1.1.0
broadcast 10.1.1.255
gateway 10.1.1.1
So basically that does an ifconfig and route command I believe (or the
equivalent)
--
CaT (cat@zip.com.au) *** Jenna has joined the channel.
<cat> speaking of mental giants..
<Jenna> me, a giant, bullshit
<Jenna> And i'm not mental
- An IRC session, 20/12/2000
next prev parent reply other threads:[~2001-02-19 22:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 11:40 eepro100 + 2.2.18 + laptop problems CaT
2001-02-13 1:26 ` Andrey Savochkin
2001-02-13 4:14 ` CaT
2001-02-19 22:21 ` CaT
2001-02-19 22:49 ` Andrey Savochkin
2001-02-20 0:18 ` Ion Badulescu
2001-02-20 0:31 ` CaT
2001-02-20 7:40 ` CaT
2001-02-20 10:00 ` Ion Badulescu
2001-02-20 10:18 ` CaT
2001-02-19 23:37 ` Dragan Stancevic
2001-02-19 22:33 ` CaT
2001-02-19 23:44 ` Dragan Stancevic
2001-02-19 22:42 ` CaT [this message]
2001-03-04 22:23 ` CaT
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=20010220094219.F365@zip.com.au \
--to=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
--cc=visitor@valinux.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