1) TOP show DHCPCD running as Task 77
2) Killed DHCPCD
3) Ran CMD to restart WiFi connection on LAN1
3) TOP says DHCPCD running as Task 109
4) Closed DHCPMon and Restarted it.
5) The three status lines:
DDNS host name: Not Registered
IP address: Not Configured
Status: DHCP client is not running
6) Display: Configuration->Current_configuration
====> Totally blank
As I said, this did work up until a couple of months ago. The main
piece of info that I want displayed is my IP address.
THANKS for the suggestions.
Carl
On Sat, 07 Oct 2006 10:21:24 -0400, Lewis G Rosenthal wrote:
>I just run the script again to activate the interface. I, too, get the
>"DHCP Client is not running" message. It's probably a timing thing,
>where we kill off the one instance but need to insert a do nothing loop
>(or a few of them) to wait long enough before we try to start it up
>again. The problem is probably more noticeable with the faster machines
>than it might have been some years ago, but I never ran this stuff on
>the older hardware (ThinkPad 360-era).
>
>I'll see if I can experiment with this before Warpstock (read: this
>weekend), and even touch on it during my workshop.
>
>Run TOP the next time and see whether DHCPCD may be exiting. Or, kill it
>from TOP and then run the script. See what you get.
>
>On 10/06/06 09:31 pm, Carl Gehr thus wrote :
>> Lewis,
>> I don't think that's my problem...
>>
>> In this case, the DHCP Monitor shows:
>> Settings->Monitor_Interface->LAN1
>> Status: DHCP Client is not running.
>>
>> The first of the above is as it should be. The second is wrong!
>> i.e., When I display the active tasks [Ctrl-Task_List on eCenter],
>> there, right at the top is:
>> DHCPCD.EXE (82)
>> Methinks DHCPMON is confused! And, it did not work this way a while
>> back. But, I've forgotten when it changed or what I might have done to
>> cause the change. FWIW, the DHCP Monitor is V4.1.
>>
>> Carl
>>
>> On Mon, 25 Sep 2006 09:37:25 -0400, Lewis G Rosenthal wrote:
>>
>>
>>> Carl, I've found that when that issue occurs, I simply wait a bit, and
>>> then re-start DHCPMON. Eventually, it gets the idea that the interface
>>> it previously accessed is no longer there, and gets the new information.
>>> Bug? Probably. I haven't seen it overly persistent, however.
>>>
>>> On 09/24/06 11:57 pm, Carl Gehr thus wrote :
>>>
>>>> Lewis,
>>>>
>>>> In the set of commands you show below [I use them almost verbatim.],
>>>> there is the command that stops the DHCP Monitor. [ dhcpmon -t ]
>>>>
>>>> BUT, I have had problems trying to get the monitor back so it will
>>>> display the status, config, etc., of the newly started LAN1. I've
>>>> tried specifying:
>>>> dhcpmon -i LAN1
>>>> but this seems to do absolutely nothing.
>>>>
>>>> Can this be done? What, if anything, am I missing?
>>>>
>>>> TIA,
>>>> Carl
>>>>
>>>>
><snip>
>
>--
>Lewis
>------------------------------------------------------------
>Lewis G Rosenthal, CNA, CLP, CLE
>Rosenthal & Rosenthal, LLC
>Accountants / Network Consultants
> New York / Northern Virginia www.2rosenthals.com
>eComStation Consultants www.ecomstation.com
>Novell Users Int'l www.novell.com/openenterpriseserver
>Need a managed Wi-Fi hotspot? www.hautspot.com
>------------------------------------------------------------
>
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>This message is sent to you because you are subscribed to
> the mailing list <os2-wireless_users@2rosenthals.com>.
>To unsubscribe, E-mail to: <os2-wireless_users-off@2rosenthals.com>
>To switch to the DIGEST mode, E-mail to <os2-wireless_users-digest@2rosenthals.com>
>To switch to the INDEX mode, E-mail to <os2-wireless_users-index@2rosenthals.com>
>Send administrative queries to <os2-wireless_users-request@2rosenthals.com>
>To subscribe (new addresses), E-mail to: <os2-wireless_users-on@2rosenthals.com> and reply to the confirmation email.
>
>This list is hosted by Rosenthal & Rosenthal
>P.O. Box 281, Deer Park, NY 11729-0281. Non-
>electronic communications related to content
>contained in these messages should be directed
>to the above address. (CAN-SPAM Act of 2003)
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
Nazaj na seznam