From: Andrew Morton <andrewm@uow.edu.au>
To: Christian Loth <chris@gidayu.max.uni-duisburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DHCP Problems with 3com 3c905C Tornado
Date: Thu, 04 Jan 2001 23:41:50 +1100 [thread overview]
Message-ID: <3A546F8E.ABF952F@uow.edu.au> (raw)
In-Reply-To: <20010104123139.A15097@gidayu.max.uni-duisburg.de>
Christian Loth wrote:
>
> Hello all,
Hi, Christian.
> I recently installed a system with the 3c905C
> NIC on RedHat 6.2. In our network, IP adresses
> are granted via DHCP, although every host has
> a fixed IP instead of a dynamic IP pool. The IP
> is statically coupled with the MAC adresses of
> our network.
hmm.. I've heard of this once before. Running
pump from the RH initscripts?
> The freshly installed RedHat 6.2 worked nice
> and flawlessly, and the IP was handed out correctly
> to the new machine. However after upgrading
> to the 2.2.16 RedHat Kernel RPMS, the DHCP negotiation
> no longer worked! Okay, I said, maybe it is a RedHat
> thing (they included modules both for the 90x and for the 59x
> cards, and I tried both),
Did _both_ 3c90x and 3c59x fail, or only 3c59x?
> so I downloaded 2.2.18 proper.
> I compiled in the support for the card, but also: same
> result. The old 2.2.14 RedHat kernel worked, but the
> newer kernels did not.
>
> Unfortunately the machine had to go on the net, so I had
> to switch the NIC for a DEC Tulip one, which worked flawlessly
> under 2.2.18 again. Therfore I unfortunately can't volunteer
> for testing :(, all I can say is that something happened
> between 2.2.14 and 2.2.16/2.2.18 which made DHCP inoperable
> for the 3c905C.
Thanks. I'll try to reproduce this (fat chance :().
Is there any chance you can set this arrangement up
again in the future?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-04 12:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 11:31 DHCP Problems with 3com 3c905C Tornado Christian Loth
2001-01-04 12:41 ` Andrew Morton [this message]
2001-01-04 12:43 ` Christian Loth
2001-01-04 12:59 ` Andrew Morton
2001-01-04 13:19 ` Christian Loth
2001-01-04 16:01 ` Arjan van de Ven
2001-01-04 17:25 ` Christian Loth
2001-01-04 19:07 ` idalton
2001-01-07 13:42 ` Andrew Morton
2001-01-08 7:02 ` Tim Wright
2001-01-08 9:12 ` Andrew Morton
2001-01-08 9:13 ` David Ford
2001-01-08 11:56 ` Alan Cox
2001-01-08 12:53 ` Andrew Morton
2001-01-08 13:10 ` Christian Loth
-- strict thread matches above, loose matches on Subject: below --
2001-01-04 13:11 Ingo T. Storm
2001-01-04 13:23 ` Christian Loth
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=3A546F8E.ABF952F@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=chris@gidayu.max.uni-duisburg.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.