dhcp.client running mad ...

We’ve got a wierd problem with the QNX 4.25 / TCP/IP 4.25 dhcp.client:

It’s running mad, when it is used in a certain environment
(Netware 5.1). Here’s a small snippet from the syslog file:


Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9


As you can see, it’s requesting new addresses hundreds of time in a
second. If I use the Neutrino or a Linux DHCP client on the same
machine, everything’s OK. Also other DHCP servers are OK.

The only special thing about ths installation is: the lease time is
infinite (0xFFFFFFFF or 4294967295). Can this be a problem?

I tried with and without the ‘-b’ option, no difference. I tried
a lot of other options ( … and combinations) , too.

Any hints?


TIA,
Karsten.


Here is, what we use:

PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25O Aug 19 2002
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24Y Apr 23 2002
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.aha7scsi scsi 4.24M Mar 23 1998
//1/bin/Dev32 Dev32 4.23G Oct 04 1996
//1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev32.ser Dev.ser 4.25A Feb 14 2003
//1/bin/Dev32.ser Dev.ser 4.25A Feb 14 2003
//1/bin/Dev32.par Dev32.par 4.25A Jan 08 2001
//1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Fsys.eide eide 4.25G Apr 15 2002
//1/bin/Fatfsys Fatfsys 4.26D Aug 28 2002
//1/bin/Pipe Pipe 4.23A Feb 26 1996
//1/bin/Net Net 4.25E Apr 24 2002
//1/bin/Net.tulip Net.tulip 4.25Q Aug 30 1999
//1/bin/cron cron 4.23B Oct 30 1997
//1/usr/bin/lpsrvr lpsrvr 4.24A Jun 26 1997
//1//photon/bin/Photon Photon 1.14B Sep 03 1999
//1/
/bin/phfontpfr Photon Font 1.14H Jan 17 2001
//1/*/usr/ucb/Socket Socket 4.25H Jul 30 1999


-rwsrwxr-x 1 root root 58492 Mar 16 1999 /usr/tcprt/current/usr/ucb/dhcp.client

Here’s also a part of the logfile from the server side,
which looks perfectly OK for me:



2003/02/11 13:12:11 packet received from client <0:80:AD:91:DA:F9>, client renewer IP address = <192.168.55.3>.
2003/02/11 13:12:11 Sending BOOTP/DHCP reply to <0:80:AD:91:DA:F9> as <192.168.55.3>.
Get type:3, IPAddr: 192.168.55.3, LeaseTime:0,MacIndx:683,pIP=C0A83703
DetermineLeaseTime: proposed=0, return=3250001764, pSubnet->leaseTime=3456000
SubmitJob called with addr=192.168.55.3, leaseExpiration=4294967295, lease=0, operation=0
AMAGet() exit type=3, err=0, addr=192.168.55.3
2003/02/11 13:12:11 packet received from client <0:80:AD:91:DA:F9>, client renewer IP address = <192.168.55.3>.
2003/02/11 13:12:11 Sending BOOTP/DHCP reply to <0:80:AD:91:DA:F9> as <192.168.55.3>.
Get type:3, IPAddr: 192.168.55.3, LeaseTime:0,MacIndx:683,pIP=C0A83703
DetermineLeaseTime: proposed=0, return=3250001764, pSubnet->leaseTime=3456000
SubmitJob called with addr=192.168.55.3, leaseExpiration=4294967295, lease=0, operation=0
AMAGet() exit type=3, err=0, addr=192.168.55.3
2003/02/11 13:12:11 packet received from client <0:80:AD:91:DA:F9>, client renewer IP address = <192.168.55.3>.
2003/02/11 13:12:11 Sending BOOTP/DHCP reply to <0:80:AD:91:DA:F9> as <192.168.55.3>.
Get type:3, IPAddr: 192.168.55.3, LeaseTime:0,MacIndx:683,pIP=C0A83703
DetermineLeaseTime: proposed=0, return=3250001764, pSubnet->leaseTime=3456000
SubmitJob called with addr=192.168.55.3, leaseExpiration=4294967295, lease=0, operation=0
AMAGet() exit type=3, err=0, addr=192.168.55.3
2003/02/11 13:12:11 packet received from client <0:80:AD:91:DA:F9>, client renewer IP address = <192.168.55.3>.
2003/02/11 13:12:11 Sending BOOTP/DHCP reply to <0:80:AD:91:DA:F9> as <192.168.55.3>.
ProcessJob pass IP DN: 192_168_55_3.MNT.MNT.NLTB, hostname photon, operation 0
Get type:3, IPAddr: 192.168.55.3, LeaseTime:0,MacIndx:683,pIP=C0A83703
DetermineLeaseTime: proposed=0, return=3250001764, pSubnet->leaseTime=3456000
SubmitJob called with addr=192.168.55.3, leaseExpiration=4294967295, lease=0, operation=0
AMAGet() exit type=3, err=0, addr=192.168.55.3


| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _
\ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |
) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

Karsten.Hoffmann@mbs-software.de wrote:

We’ve got a wierd problem with the QNX 4.25 / TCP/IP 4.25 dhcp.client:

It’s running mad, when it is used in a certain environment
(Netware 5.1). Here’s a small snippet from the syslog file:


Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9

I wonder, if there’s anybody familiar with this kind of problem?


| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _
\ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |
) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

The dhcp.client is probably not handling the infinit lease time properly
as this effects the timing that determines when the client will renew
the address. Does a smaller lease time work properly? A problem report
will be generated to verify the behavior of all versions.

Thanks

Dave

Karsten.Hoffmann@mbs-software.de wrote:

We’ve got a wierd problem with the QNX 4.25 / TCP/IP 4.25 dhcp.client:

It’s running mad, when it is used in a certain environment
(Netware 5.1). Here’s a small snippet from the syslog file:


Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9
Feb 11 13:07:31 node<<1>> dhclient: DHCPREQUEST to en1
Feb 11 13:07:31 node<<1>> dhclient: DHCPACK from 0:80:ad:91:da:f9


As you can see, it’s requesting new addresses hundreds of time in a
second. If I use the Neutrino or a Linux DHCP client on the same
machine, everything’s OK. Also other DHCP servers are OK.

The only special thing about ths installation is: the lease time is
infinite (0xFFFFFFFF or 4294967295). Can this be a problem?

I tried with and without the ‘-b’ option, no difference. I tried
a lot of other options ( … and combinations) , too.

Any hints?


TIA,
Karsten.


Here is, what we use:

PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25O Aug 19 2002
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24Y Apr 23 2002
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.aha7scsi scsi 4.24M Mar 23 1998
//1/bin/Dev32 Dev32 4.23G Oct 04 1996
//1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev32.ser Dev.ser 4.25A Feb 14 2003
//1/bin/Dev32.ser Dev.ser 4.25A Feb 14 2003
//1/bin/Dev32.par Dev32.par 4.25A Jan 08 2001
//1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Fsys.eide eide 4.25G Apr 15 2002
//1/bin/Fatfsys Fatfsys 4.26D Aug 28 2002
//1/bin/Pipe Pipe 4.23A Feb 26 1996
//1/bin/Net Net 4.25E Apr 24 2002
//1/bin/Net.tulip Net.tulip 4.25Q Aug 30 1999
//1/bin/cron cron 4.23B Oct 30 1997
//1/usr/bin/lpsrvr lpsrvr 4.24A Jun 26 1997
//1//photon/bin/Photon Photon 1.14B Sep 03 1999
//1/
/bin/phfontpfr Photon Font 1.14H Jan 17 2001
//1/*/usr/ucb/Socket Socket 4.25H Jul 30 1999


-rwsrwxr-x 1 root root 58492 Mar 16 1999 /usr/tcprt/current/usr/ucb/dhcp.client

Here’s also a part of the logfile from the server side,
which looks perfectly OK for me:



2003/02/11 13:12:11 packet received from client <0:80:AD:91:DA:F9>, client renewer IP address = <192.168.55.3>.
2003/02/11 13:12:11 Sending BOOTP/DHCP reply to <0:80:AD:91:DA:F9> as <192.168.55.3>.
Get type:3, IPAddr: 192.168.55.3, LeaseTime:0,MacIndx:683,pIP=C0A83703
DetermineLeaseTime: proposed=0, return=3250001764, pSubnet->leaseTime=3456000
SubmitJob called with addr=192.168.55.3, leaseExpiration=4294967295, lease=0, operation=0
AMAGet() exit type=3, err=0, addr=192.168.55.3
2003/02/11 13:12:11 packet received from client <0:80:AD:91:DA:F9>, client renewer IP address = <192.168.55.3>.
2003/02/11 13:12:11 Sending BOOTP/DHCP reply to <0:80:AD:91:DA:F9> as <192.168.55.3>.
Get type:3, IPAddr: 192.168.55.3, LeaseTime:0,MacIndx:683,pIP=C0A83703
DetermineLeaseTime: proposed=0, return=3250001764, pSubnet->leaseTime=3456000
SubmitJob called with addr=192.168.55.3, leaseExpiration=4294967295, lease=0, operation=0
AMAGet() exit type=3, err=0, addr=192.168.55.3
2003/02/11 13:12:11 packet received from client <0:80:AD:91:DA:F9>, client renewer IP address = <192.168.55.3>.
2003/02/11 13:12:11 Sending BOOTP/DHCP reply to <0:80:AD:91:DA:F9> as <192.168.55.3>.
Get type:3, IPAddr: 192.168.55.3, LeaseTime:0,MacIndx:683,pIP=C0A83703
DetermineLeaseTime: proposed=0, return=3250001764, pSubnet->leaseTime=3456000
SubmitJob called with addr=192.168.55.3, leaseExpiration=4294967295, lease=0, operation=0
AMAGet() exit type=3, err=0, addr=192.168.55.3
2003/02/11 13:12:11 packet received from client <0:80:AD:91:DA:F9>, client renewer IP address = <192.168.55.3>.
2003/02/11 13:12:11 Sending BOOTP/DHCP reply to <0:80:AD:91:DA:F9> as <192.168.55.3>.
ProcessJob pass IP DN: 192_168_55_3.MNT.MNT.NLTB, hostname photon, operation 0
Get type:3, IPAddr: 192.168.55.3, LeaseTime:0,MacIndx:683,pIP=C0A83703
DetermineLeaseTime: proposed=0, return=3250001764, pSubnet->leaseTime=3456000
SubmitJob called with addr=192.168.55.3, leaseExpiration=4294967295, lease=0, operation=0
AMAGet() exit type=3, err=0, addr=192.168.55.3