[ltp] Please help me pick out my next thinkpad

Marius Gedminas linux-thinkpad@linux-thinkpad.org
Thu, 12 Jun 2008 13:51:39 +0300


--IrhDeMKUP4DT/M7F
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 11, 2008 at 10:44:23PM -0700, John Jason Jordan wrote:
> Ever since my upgrade from Gutsy x86_64 to Hardy x86_64 I have been
> using the 4965. Previously I used a Netgear PCMCIA card because of
> problems with the 4965.
>=20
> The situation is now tolerable, but I still get random disconnects, or
> sometimes I remain connected but lose my DHCP lease. For example,
> sitting in the library at the university almost directly under an
> access point, wicd shows 95%, I connect without problem. I access the
> library catalog, find what I want, and then go to writing a text
> document. Fifteen minutes later I need to access the library catalog
> again and discover that I have been disconnected, or that I am still
> connected but my DHCP lease is gone.

That sounds like you either

  (A) have two DHCP daemons running in parallel

or

  (B) have a buggy Network Manager that doesn't understand you successfully
      acquired a DHCP lease.

I suffered from condition (A) a while back.  IIUC it was the combination of
Ubuntu/Debian's network configuration scripts interpreting my "please
bring up eth1 automatically" config in /etc/network/interfaces by "hey,
let's run dhclient3 on it" while at the same time network-manager
interpreted the same configuration as "hey, let me run *my* dhcp client
on it".  Every 10 minutes or so one of the DHCP clients would drop all
existing IP addresses from the interface and start requesting new ones.

My coworker suffers from condition (B) now.  The log files clearly show
network manager spawning dhclient, dhclient acquiring a lease, and then
60 seconds later network manager claiming falsely that the DHCP lease
could not be acquired, then unconfiguring the interface.  He has a Cisco
Aironet wireless card, although I've no idea how a driver could trigger
this bug in n-m.

Marius Gedminas
--=20
The reason computer chips are so small is that computers don't eat much.

--IrhDeMKUP4DT/M7F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIUP+7kVdEXeem148RAl2TAJsFOqbqWBCkVvkBo6vxt0UgfBYo1QCfRifF
57178uSYVM3DF2vizvg9t64=
=vmK1
-----END PGP SIGNATURE-----

--IrhDeMKUP4DT/M7F--