All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: timw@splhi.com
Cc: Christian Loth <chris@gidayu.max.uni-duisburg.de>,
	linux-kernel@vger.kernel.org
Subject: Re: DHCP Problems with 3com 3c905C Tornado
Date: Mon, 08 Jan 2001 20:12:20 +1100	[thread overview]
Message-ID: <3A598474.3A69C684@uow.edu.au> (raw)
In-Reply-To: <20010104123139.A15097@gidayu.max.uni-duisburg.de> <3A58725F.A1E3CD37@uow.edu.au>, <3A58725F.A1E3CD37@uow.edu.au>; from andrewm@uow.edu.au on Mon, Jan 08, 2001 at 12:42:55AM +1100 <20010107230226.A2074@scutter.internal.splhi.com>

Tim Wright wrote:
> 
> Sounds somewhat familiar. The pump that came with RedHat 6.2 never worked
> correctly at work, but dhcpcd worked just fine (we don't have static IP
> addresses, but there are fewer machines than there are addresses in the pool,
> so effectively, we do :-). The odd thing is that I (mis?)understood in this
> case that dhcpcd was not working either (unless I'm confusing this with a
> different thread). Suffice to say that newer versions of pump seem to work
> much better, at least for me.

No, you're not confused.  Someone did mention that dhcpcd was
playing up.

Obviously, something changed between 2.2.14 and more current
kernels which broke pump.  I don't believe it's a driver change
because it also affects the 3c90x driver.  I don't have a theory
as to why this affects the 3com NICs though.  But I'm assuming
that whatever broke pump also broke dhcpcd.

I note that with 3c59x in 2.4.0, pump-0.7.3 basically freezes up.
It spits out a single bootp packet then goes to lunch.  I got
bored waiting after ten minutes. So an upgrade is definitely needed.

-
-
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/

  reply	other threads:[~2001-01-08  9:06 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
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 [this message]
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=3A598474.3A69C684@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=chris@gidayu.max.uni-duisburg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timw@splhi.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 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.