Failure to acquire IP over DHCP

[Suvayu Ali]

On Thu, Aug 30, 2012 at 10:43:59AM -0400, Mark Haney wrote:
> On 08/30/2012 10:36 AM, Suvayu Ali wrote:
> >Hi,
> >
> >I have a weird problem; at my office every time I try to connect to my
> >wall outlet, my laptop gets assigned an internal IP (192.168.0.114) and
> >I cannot access the internet.  However everything works as expected when
> >I use any other wall outlets.  To add to this, when other laptops
> >connect to my wall outlet, they  work properly.
> >
> >This is a dump of my network connection (with DHCP enabled):
> ><http://pastebin.com/7bsXDMBP>.  And the relevant bits from
> >/var/log/messages (when I get assigned the wrong IP):
> ><http://pastebin.com/9eZTprqk>
> 
> What is the IP subnet that DHCP hands out?  Is it on a different subnet from
> 192.168.0.x?
> 

My understanding of networks is next to nothing; by subnet do you mean
the netmask field as reported by ifconfig?  If so I have quoted that
below:

eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
  inet 192.168.0.114  netmask 255.255.255.0  broadcast 192.168.0.255
  inet6 fe80::f2de:f1ff:fe37:c76c  prefixlen 64  scopeid 0x20<link>
  ether f0:de:f1:37:c7:6c  txqueuelen 1000  (Ethernet)
  RX packets 1465427  bytes 2094516052 (1.9 GiB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 717576  bytes 56236036 (53.6 MiB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 20  memory 0xf2500000-f2520000  

> Sounds almost like the MAC address of your laptop has been assigned an IP
> from the DHCP server.  Why that keeps from getting internet access depends
> on the subnet question above, methinks.
> 

-- 
Suvayu

Open source is the future. It sets us free.