| 1 |
> |
| 2 |
>> > The main correlation I've seen so far is with dhcpcd. Sometimes at my |
| 3 |
>> > work I get a 192. IP (which doesn't work), and other times I get a |
| 4 |
>> > 133. IP (which is correct). In fact, sometimes dhcp is giving me an |
| 5 |
>> > IP address and resolv.conf related to a university I was visiting like |
| 6 |
>> > a month ago. |
| 7 |
>> |
| 8 |
>> It sounds like someone at your work might be (accidentally) running a |
| 9 |
>> rogue DHCP server... |
| 10 |
>> |
| 11 |
> |
| 12 |
> For the 192 address - yeah, someone has probably plugged a WLAN or ADSL |
| 13 |
> router into the local network, and other people will be have the same |
| 14 |
> problem. If they were purposely running a rogue DHCP server to perform a Man |
| 15 |
> In the Middle attack you wouldn't notice any connectivity problems (assuming |
| 16 |
> they set it up correctly). |
| 17 |
> |
| 18 |
|
| 19 |
Yes. I was getting the wireless IP. Turns out my officemate had |
| 20 |
turned off the dhcp server. >_< |
| 21 |
|
| 22 |
> |
| 23 |
> Getting the university address is very odd. AFAIK dhcpcd has no function to |
| 24 |
> fall back to the address from an expired lease. |
| 25 |
> |
| 26 |
> Grep your logs for dhcpcd and post the result. |
| 27 |
> |
| 28 |
|
| 29 |
I found the outdated static configuration file. Woops! |
| 30 |
|
| 31 |
Well, so that was a very silly problem! Non-commented dated |
| 32 |
configuration file and broken dhcp server. But the behavior was so |
| 33 |
random. And I never new that the DNS lookup would delay logins. So |
| 34 |
that was very educational. |
| 35 |
|
| 36 |
Regards, |
| 37 |
daid |
Archives