From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Slow Login, Sudo, etc.
Date: Thu, 14 Oct 2010 11:57:36 +1100 [thread overview]
Message-ID: <AANLkTikNmb_mrhXXCvan7T2X0app8=24m65FdOy5G-MX@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=ddp84gR-a-xBpLhJzqwOhbd-0CPsSAS2VeWhe@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
> > The main correlation I've seen so far is with dhcpcd. Sometimes at my
> > work I get a 192. IP (which doesn't work), and other times I get a
> > 133. IP (which is correct). In 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 (assuming
they set it up correctly).
When dhcpcd fails to get a response from a DHCP server it will typically
fall back to Zeroconf/RFC3927 behavior and assign a a169.245.x.y address.
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.
[-- Attachment #2: Type: text/html, Size: 1341 bytes --]
next prev parent reply other threads:[~2010-10-14 0:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 6:38 [gentoo-user] Slow Login, Sudo, etc daid kahl
2010-10-12 7:12 ` [gentoo-user] " daid kahl
2010-10-12 7:13 ` daid kahl
2010-10-12 14:42 ` [gentoo-user] " Paul Hartman
2010-10-12 22:12 ` [gentoo-user] " walt
2010-10-13 13:38 ` daid kahl
2010-10-14 0:28 ` James Ausmus
2010-10-14 0:57 ` Adam Carter [this message]
2010-10-15 7:24 ` daid kahl
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='AANLkTikNmb_mrhXXCvan7T2X0app8=24m65FdOy5G-MX@mail.gmail.com' \
--to=adamcarter3@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox