| 1 |
On Wed, Oct 13, 2010 at 6:38 AM, daid kahl <daidxor@×××××.com> wrote: |
| 2 |
>> On 10/11/2010 11:38 PM, daid kahl wrote: |
| 3 |
>> |
| 4 |
>>> However, I noticed that logins, su, and sudo are all responding |
| 5 |
>>> slowly. This was all fixed and fine once I updated my configuration |
| 6 |
>>> files, but this week it's acting up again. Before it was just su and |
| 7 |
>>> sudo that I noticed as slow (authentication takes around 20 seconds). |
| 8 |
>>> But now even logins are delayed (xdm or command line). |
| 9 |
> |
| 10 |
> On 13 October 2010 07:12, walt <w41ter@×××××.com> wrote: |
| 11 |
>> |
| 12 |
>> Whenever I see something that eventually works, but only after a long |
| 13 |
>> delay, I think of DNS problems. |
| 14 |
>> |
| 15 |
>> Who might be doing a nonsensical DNS lookup, I have no idea. But you |
| 16 |
>> might consider running a packet sniffer (wireshark, etc) while logging |
| 17 |
>> in or doing an su. Are you running your own local name server? |
| 18 |
> |
| 19 |
> Very very intersting!! |
| 20 |
> |
| 21 |
> The main correlation I've seen so far is with dhcpcd. Sometimes at my |
| 22 |
> work I get a 192. IP (which doesn't work), and other times I get a |
| 23 |
> 133. IP (which is correct). In fact, sometimes dhcp is giving me an |
| 24 |
> IP address and resolv.conf related to a university I was visiting like |
| 25 |
> a month ago. |
| 26 |
|
| 27 |
It sounds like someone at your work might be (accidentally) running a |
| 28 |
rogue DHCP server... |
| 29 |
|
| 30 |
-James |
Archives