fsKY3WgPHqdURDSg";
er.org"; posting-account="U2FsdGVkX1+1qbVLCb6K4mSsv7FQOB46"
Gecko/20101206 SUSE/3.1.7 Thunderbird/3.1.7
.os2.networking.tcp-ip:211
From: Marty
One thing, which I don't think has been mentioned here yet is that DHCP
clients tend to try to re-acquire the same address that they had
previously. They will explicitly request it from the DHCP server, and
it's the server's responsibility to decide if it is available or not.
Perhaps this, coupled with your low lease time resulted in your problem.
Your eCS lease expired, but the eCS DHCP client didn't renew it in
time (probably assumed a more sane renewal time), then the Linux machine
popped on and requested the same address (which was the address it had
held previously?). Usually explicitly releasing the DHCP lease will
undo these kinds of SNAFUs (dhcpcd -k on Linux). You can check
/var/logs/messages on Linux to get some visibility into what the DHCP
client is doing.
On 03/27/2011 11:23 AM, Pierre Jelenc wrote:
> Peter Flass writes:
>>
>> Probably something under LAN setup. You should be able to configure
>> DHCP (or not) and/or DDNS. What address/options did you assign when you
>> did the OS/2 TCP/IP configuration?
>
> Here are the LAN and WAN setup forms (I had to take screen shots, since
> they are form input fields):
>
> http://www.pierrejelenc.com/lansetup.gif
> http://www.pierrejelenc.com/wansetup.gif
>
>> You should run an ethernet monitor in promiscuous mode on Linux and log
>> all the packets. This should point you in the right direction. I
>> assume this LAN is only these two or three machines, so you're not
>> talking huge volumes of traffic.
>
> Two machines. I'll have to figure out the ethernet monitor business.
--
Reverse the parts of the e-mail address to reply by mail.
--- Internet Rex 2.31
* Origin: A noiseless patient Spider (1:261/20.999)
|
