the infamous linux wifi monster strikes

[Robert Holtzman]

On Tue, 14 Apr 2009, wirechief wrote:

> Well I would issue  dhclient eth0  or eth1  whichever is detected. see
> how that works.

Thanks for the reply.

What I got was (and I don't know how to interpret it):

There is already a pid file /var/run/dhclient.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:15:00:4a:a3:4c
Sending on   LPF/eth1/00:15:00:4a:a3:4c
Sending on   Socket/fallback
DHCPREQUEST of 192.168.1.100 on eth1 to 255.255.255.255 port 67
DHCPREQUEST of 192.168.1.100 on eth1 to 255.255.255.255 port 67
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPOFFER of 192.168.1.100 from 192.168.1.1
DHCPREQUEST of 192.168.1.100 on eth1 to 255.255.255.255 port 67
DHCPACK of 192.168.1.100 from 192.168.1.1
bound to 192.168.1.100 -- renewal in 37716 seconds.

Any ideas?

-- 
Bob Holtzman
"If you think you're getting free lunch,
  check the price of the beer"