Failure to acquire IP over DHCP

[Suvayu Ali]

On Fri, Aug 31, 2012 at 01:50:04AM +0200, Suvayu Ali wrote:
> 
> Thanks a lot for the hints.  I'm meeting the admin in person tomorrow,
> these comments will surely be useful.
> 

This is just to update the list, the problem is indeed someone not
following the regulations.  As you can see from the output below,
someone is running an entire (unapproved) network in their office.
Probably they want WiFi since the official WiFi is pretty weak in our
building.

In the output below, 192.168.0.114 is the IP my laptop gets assigned.

# nmap -sn 192.168.0.0-255

Starting Nmap 6.01 ( http://nmap.org ) at 2012-08-31 14:40 CEST
Nmap scan report for 192.168.0.1
Host is up (0.00066s latency).
MAC Address: C8:3A:35:5E:E3:90 (Tenda Technology Co.)
Nmap scan report for 192.168.0.100
Host is up (0.33s latency).
MAC Address: 88:30:8A:36:A9:2A (Murata Manufactuaring Co.)
Nmap scan report for 192.168.0.104
Host is up (0.015s latency).
MAC Address: 98:0C:82:64:FE:1B (Samsung Electro Mechanics)
Nmap scan report for 192.168.0.114
Host is up.
Nmap scan report for 192.168.0.118
Host is up (0.14s latency).
MAC Address: 90:4C:E5:56:BF:03 (Hon Hai Precision Ind. Co.)
Nmap scan report for 192.168.0.129
Host is up (0.060s latency).
MAC Address: A8:26:D9:36:A6:1A (HTC)
Nmap scan report for 192.168.0.196
Host is up (0.43s latency).
MAC Address: 38:16:D1:83:46:B2 (Samsung Electronics Co.)
Nmap done: 256 IP addresses (7 hosts up) scanned in 63.80 seconds

Thanks for all the pointers and discussion.  It was quite educational
for me.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.