Groups > eComStation > eComStation networking > Re: Why does the 'DHCP Monitor' not work with WLAN?




Why does the 'DHCP Monitor' not work with WLAN?

Why does the 'DHCP Monitor' not work with WLAN?
Sun, 07 Oct 2007 11:36:34 -040
I am using eCS 2.0 RC2, WLAN 3.00 and GenMac 2.1 on a TPad T60 with
Intel 3945abg WiFi [8086:4227] and Pro/1000 [8086:109A].

Although I can get the IP address [and more] for the WiFi by hovering
over the WLAN widget, the DHCP Monitor always indicates that:
    "DHCP Client is not running"

Why does it think the client is not running?
  \MPTN\BIN\DHCPCD.EXE
is clearly on the task list displayed by TOP.  What is the DHCP monitor
looking for that is not there?

TIA,
Post Reply
Re: Why does the 'DHCP Monitor' not work with WLAN?
Sun, 07 Oct 2007 17:17:38 -040
Doug Bissett wrote:
> On Sun, 7 Oct 2007 15:36:34 UTC, Carl Gehr 
> <Carl.Gehr.ButNoSPAMStuff2@MCGCG.Com> wrote:
> 
>> I am using eCS 2.0 RC2, WLAN 3.00 and GenMac 2.1 on a TPad T60 with
>> Intel 3945abg WiFi [8086:4227] and Pro/1000 [8086:109A].
>>
>> Although I can get the IP address [and more] for the WiFi by hovering
>> over the WLAN widget, the DHCP Monitor always indicates that:
>>     "DHCP Client is not running"
>>
>> Why does it think the client is not running?
>>   \MPTN\BIN\DHCPCD.EXE
>> is clearly on the task list displayed by TOP.  What is the DHCP
monitor
>> looking for that is not there?
>>
>> TIA,
>> Carl
> 
> Simple. The DHCP client (DHCPCD.EXE) is NOT running, so the DHCP 
> monitor is absolutely correct, when it says it is not. The addresses 
> are determined, and assigned, in a different way by WLAN, and WLAN (or
> XWLAN) tells you the address information, as you note. The DHCP 
> monitor requires that the DHCP client be running, before it can tell 
> you anything useful. Don't try to start DHCPCD.EXE, or you will 
> confuse the whole thing, since it will attempt to assign a new 
> address, and that isn't likely to work well.
> 
> Hope this helps...
Well, Doug, it would help:
...Except when I display active tasks using both TOP and Ctrl-TaskWidget 
[in eCenter] DHCPCD.EXE IS listed as TaskID=94.  Since both tools are 
showing the same TaskID, I have to assume they are looking at the same 
thing.

Your comments do raise another question, though:
Q:  In WLAN, I have the Properties set to:
	"Retain settings from last shutdown."
     Yet, for some reason, I get a different IP assigned every once
     in a while.  It's not predictable when it will change and when
     it stays the same as it was previously.
Maybe these are related, maybe not.
-- 
TIA,
Post Reply
Re: Why does the 'DHCP Monitor' not work with WLAN?
Sun, 07 Oct 2007 19:37:16 GMT
On Sun, 7 Oct 2007 15:36:34 UTC, Carl Gehr 
<Carl.Gehr.ButNoSPAMStuff2@MCGCG.Com> wrote:

> I am using eCS 2.0 RC2, WLAN 3.00 and GenMac 2.1 on a TPad T60 with
> Intel 3945abg WiFi [8086:4227] and Pro/1000 [8086:109A].
> 
> Although I can get the IP address [and more] for the WiFi by hovering
> over the WLAN widget, the DHCP Monitor always indicates that:
>     "DHCP Client is not running"
> 
> Why does it think the client is not running?
>   \MPTN\BIN\DHCPCD.EXE
> is clearly on the task list displayed by TOP.  What is the DHCP monitor
> looking for that is not there?
> 
> TIA,
> Carl

Simple. The DHCP client (DHCPCD.EXE) is NOT running, so the DHCP 
monitor is absolutely correct, when it says it is not. The addresses 
are determined, and assigned, in a different way by WLAN, and WLAN (or
XWLAN) tells you the address information, as you note. The DHCP 
monitor requires that the DHCP client be running, before it can tell 
you anything useful. Don't try to start DHCPCD.EXE, or you will 
confuse the whole thing, since it will attempt to assign a new 
address, and that isn't likely to work well.

Hope this helps...
-- 
From the eComStation 2.0 RC2 of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Post Reply
Re: Why does the 'DHCP Monitor' not work with WLAN?
Wed, 10 Oct 2007 16:40:42 GMT
On Sun, 7 Oct 2007 21:17:38 UTC, Carl Gehr 
<Carl.Gehr.ButNoSPAMStuff2@MCGCG.Com> wrote:

> Doug Bissett wrote:
> > On Sun, 7 Oct 2007 15:36:34 UTC, Carl Gehr 
> > <Carl.Gehr.ButNoSPAMStuff2@MCGCG.Com> wrote:
> > 
> >> I am using eCS 2.0 RC2, WLAN 3.00 and GenMac 2.1 on a TPad T60
with
> >> Intel 3945abg WiFi [8086:4227] and Pro/1000 [8086:109A].
> >>
> >> Although I can get the IP address [and more] for the WiFi by
hovering
> >> over the WLAN widget, the DHCP Monitor always indicates that:
> >>     "DHCP Client is not running"
> >>
> >> Why does it think the client is not running?
> >>   \MPTN\BIN\DHCPCD.EXE
> >> is clearly on the task list displayed by TOP.  What is the DHCP
monitor
> >> looking for that is not there?
> >>
> >> TIA,
> >> Carl
> > 
> > Simple. The DHCP client (DHCPCD.EXE) is NOT running, so the DHCP 
> > monitor is absolutely correct, when it says it is not. The addresses 
> > are determined, and assigned, in a different way by WLAN, and WLAN
(or
> > XWLAN) tells you the address information, as you note. The DHCP 
> > monitor requires that the DHCP client be running, before it can tell 
> > you anything useful. Don't try to start DHCPCD.EXE, or you will 
> > confuse the whole thing, since it will attempt to assign a new 
> > address, and that isn't likely to work well.
> > 
> > Hope this helps...
> Well, Doug, it would help:
> ...Except when I display active tasks using both TOP and Ctrl-TaskWidget 
> [in eCenter] DHCPCD.EXE IS listed as TaskID=94.  Since both tools are 
> showing the same TaskID, I have to assume they are looking at the same 
> thing.

Don't know, but I suspect that WLAN might be hiding it somehow.

> Your comments do raise another question, though:
> Q:  In WLAN, I have the Properties set to:
> 	"Retain settings from last shutdown."
>      Yet, for some reason, I get a different IP assigned every once
>      in a while.  It's not predictable when it will change and when
>      it stays the same as it was previously.
> Maybe these are related, maybe not.

Probably not. "Retain settings from last shutdown", simply tells it
to
attempt to get the same address, but it is up to the DHCP server to do
that. If something else has taken the previous address (making it not 
available), you will get a new one.

-- 
From the eComStation 2.0 RC2 of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Post Reply
about | contact