From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1P6fIe-000522-2r for garchives@archives.gentoo.org; Fri, 15 Oct 2010 08:06:00 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6AF35E08BF for ; Fri, 15 Oct 2010 08:05:58 +0000 (UTC) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.213.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 4E443E06EE for ; Fri, 15 Oct 2010 07:24:42 +0000 (UTC) Received: by yxd5 with SMTP id 5so458488yxd.40 for ; Fri, 15 Oct 2010 00:24:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=fTeYTGxoTTFhgVHDI0S6bv+TcGi7HWS/V1zfNCIpsPo=; b=x8da0PPZ/VoloFkYXq61fHGZddEuTWw2PHwdjGCjiLEKslJ/j4z0lyVTUIN3li1pEu ukPnYbWLt/HHrvn+KCHtms33SQ+z2OvRoLBwMqcnwk5Nmg509WZb1H9rv4pexh/nhen+ oz6LyIEHYErq1r1HtpAaJStqofqr2PQRAoKwE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=v3xWUDZYgvb1amZInJX0SIKeuxAmMVo3jBhShweSm6je7SU36UIEL8OrLrnczJWzRs VjxpFkQswqcVeJjjywap0pjMn26uNFeHy6mAWLLGk23005/zQ7u5f4KmrrJKceR2SQ9k xCIRrJr+813GNgu0T0vIPHpJf/OJxKPGf49Lw= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.90.95.2 with SMTP id s2mr5391340agb.130.1287127481807; Fri, 15 Oct 2010 00:24:41 -0700 (PDT) Received: by 10.90.106.3 with HTTP; Fri, 15 Oct 2010 00:24:41 -0700 (PDT) In-Reply-To: References: Date: Fri, 15 Oct 2010 16:24:41 +0900 Message-ID: Subject: Re: [gentoo-user] Re: Slow Login, Sudo, etc. From: daid kahl To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 3ea3fd97-2f71-4a84-b93e-17450051bff6 X-Archives-Hash: 27617db6fb4b4f315960daeaa7581854 > >> > The main correlation I've seen so far is with dhcpcd. =A0Sometimes at = my >> > work I get a 192. IP (which doesn't work), and other times I get a >> > 133. IP (which is correct). =A0In fact, sometimes dhcp is giving me an >> > IP address and resolv.conf related to a university I was visiting like >> > a month ago. >> >> It sounds like someone at your work might be (accidentally) running a >> rogue DHCP server... >> > > For the 192 address - yeah, someone has probably plugged a WLAN or ADSL > router into the local network, and other people will be have the same > problem. If they were purposely running a rogue DHCP server to perform a = Man > In the Middle attack you wouldn't notice any connectivity problems (assum= ing > they set it up correctly). > Yes. I was getting the wireless IP. Turns out my officemate had turned off the dhcp server. >_< > > Getting the university address is very odd. AFAIK dhcpcd has no function = to > fall back to the address from an expired lease. > > Grep your logs for dhcpcd and post the result. > I found the outdated static configuration file. Woops! Well, so that was a very silly problem! Non-commented dated configuration file and broken dhcp server. But the behavior was so random. And I never new that the DNS lookup would delay logins. So that was very educational. Regards, daid