dhcp.client

I can’t seem to get DHCP to work with QNX v4.25. When I run
dhcp.client, it just terminates without any error messages. The printed
documentation is different than the online documentation, which
indicates changes, so I’m not sure if it is stable.

Anybody else use this with success?

Jim Bormann <jim.bormann@mydomain.com> wrote:
: I can’t seem to get DHCP to work with QNX v4.25. When I run
: dhcp.client, it just terminates without any error messages. The printed
: documentation is different than the online documentation, which
: indicates changes, so I’m not sure if it is stable.

: Anybody else use this with success?

We use it all the time. There were problems in older versions of it.
What version of TCP do you have installed? Also what are you using for
your dhcp server (We have had problems with Windows based servers).

Rick…

Rick Duff Internet: rick@astra.mb.ca
Astra Network QUICS: rgduff
QNX Consulting and Custom Programming URL: http://www.astra.mb.ca
+1 (204) 987-7475 Fax: +1 (204) 987-7479

Hi,
Just have to ask this question first, you have the proper Net drivers
running, right:? I remember someone once not getting dhcp.client working
because they hadn’t started Net, the proper Net driver for their card, and
the Socket manager.

Otherwise, I use dhcp.client all the time, and haven’t really seen any
problems.

One thing you might try, is run dhcp.client in the background (with ‘&’) and
run if_up on the interface (en1 in my case). if_up will check to see if the
interface you are using has successfully been setup and is working.

dhcp.client will close part of itself off if run in the background when it
is done getting the configuration information. So seeing
" ### Done dhcp.client" soon after starting it is
normal (at least in my experience it is normal).

Hope that helps,
R B Adler


“Jim Bormann” <jim.bormann@mydomain.com> wrote in message
news:39F87EE4.FA0F0CA4@mydomain.com

I can’t seem to get DHCP to work with QNX v4.25. When I run
dhcp.client, it just terminates without any error messages. The printed
documentation is different than the online documentation, which
indicates changes, so I’m not sure if it is stable.

Anybody else use this with success?

Thanks for the reply. I have Net started, but the hardcopy doc I have says,
“Socket or Socklet shouldn’t be running when starting dhcp.client. The
dhcp.client expects to find Socket / Socklet in the /usr/ucb directory. It also
makes use of /usr/ucb/ifconfig and /usr/ucb/route…” The electronic doc is
much different, it doesn’t mention what I just quoted from hardcopy. It makes
the comment, “The TCP/IP stack must be started before dhcp.client. The minimum
commands to run under QNX4 are: Tcpip &; dhcp.client &; if_up enx”. I have no
idea what they mean by the TCP/IP stack started - I assume they mean the Net
driver for the card? And the “Tcpip &” makes no sense to me - there is no
utility / script with that name.

I now am using a static IP address, and everything works fine. I remove
references to Socket, ifconfig, and route from my startup script, and replace
them with the dhcp.client, which doesn’t work.

Thanks,
Jim

R B Adler wrote:

Hi,
Just have to ask this question first, you have the proper Net drivers
running, right:? I remember someone once not getting dhcp.client working
because they hadn’t started Net, the proper Net driver for their card, and
the Socket manager.

Otherwise, I use dhcp.client all the time, and haven’t really seen any
problems.

One thing you might try, is run dhcp.client in the background (with ‘&’) and
run if_up on the interface (en1 in my case). if_up will check to see if the
interface you are using has successfully been setup and is working.

dhcp.client will close part of itself off if run in the background when it
is done getting the configuration information. So seeing
" ### Done dhcp.client" soon after starting it is
normal (at least in my experience it is normal).

Hope that helps,
R B Adler

“Jim Bormann” <> jim.bormann@mydomain.com> > wrote in message
news:> 39F87EE4.FA0F0CA4@mydomain.com> …
I can’t seem to get DHCP to work with QNX v4.25. When I run
dhcp.client, it just terminates without any error messages. The printed
documentation is different than the online documentation, which
indicates changes, so I’m not sure if it is stable.

Anybody else use this with success?

I wonder if that is my problem - trying to use a Windows (Lose-Doze) based
server for DHCP. Maybe ol’ Slick Willy Gates got me again even without
directly using his crap…

rick@astra.mb.ca wrote:

Jim Bormann <> jim.bormann@mydomain.com> > wrote:
: I can’t seem to get DHCP to work with QNX v4.25. When I run
: dhcp.client, it just terminates without any error messages. The printed
: documentation is different than the online documentation, which
: indicates changes, so I’m not sure if it is stable.

: Anybody else use this with success?

We use it all the time. There were problems in older versions of it.
What version of TCP do you have installed? Also what are you using for
your dhcp server (We have had problems with Windows based servers).

Rick…

Rick Duff Internet: > rick@astra.mb.ca
Astra Network QUICS: rgduff
QNX Consulting and Custom Programming URL: > http://www.astra.mb.ca
+1 (204) 987-7475 Fax: +1 (204) 987-7479

The references to Tcpip are fot then version 5 beta - Tcpip (the stack)
replaces Sock[l]et. There are a few other operational differences
besides this.

Richard


Jim Bormann wrote:

Thanks for the reply. I have Net started, but the hardcopy doc I have says,
“Socket or Socklet shouldn’t be running when starting dhcp.client. The
dhcp.client expects to find Socket / Socklet in the /usr/ucb directory. It also
makes use of /usr/ucb/ifconfig and /usr/ucb/route…” The electronic doc is
much different, it doesn’t mention what I just quoted from hardcopy. It makes
the comment, “The TCP/IP stack must be started before dhcp.client. The minimum
commands to run under QNX4 are: Tcpip &; dhcp.client &; if_up enx”. I have no
idea what they mean by the TCP/IP stack started - I assume they mean the Net
driver for the card? And the “Tcpip &” makes no sense to me - there is no
utility / script with that name.

I now am using a static IP address, and everything works fine. I remove
references to Socket, ifconfig, and route from my startup script, and replace
them with the dhcp.client, which doesn’t work.

Thanks,
Jim

R B Adler wrote:

Hi,
Just have to ask this question first, you have the proper Net drivers
running, right:? I remember someone once not getting dhcp.client working
because they hadn’t started Net, the proper Net driver for their card, and
the Socket manager.

Otherwise, I use dhcp.client all the time, and haven’t really seen any
problems.

One thing you might try, is run dhcp.client in the background (with ‘&’) and
run if_up on the interface (en1 in my case). if_up will check to see if the
interface you are using has successfully been setup and is working.

dhcp.client will close part of itself off if run in the background when it
is done getting the configuration information. So seeing
" ### Done dhcp.client" soon after starting it is
normal (at least in my experience it is normal).

Hope that helps,
R B Adler

“Jim Bormann” <> jim.bormann@mydomain.com> > wrote in message
news:> 39F87EE4.FA0F0CA4@mydomain.com> …
I can’t seem to get DHCP to work with QNX v4.25. When I run
dhcp.client, it just terminates without any error messages. The printed
documentation is different than the online documentation, which
indicates changes, so I’m not sure if it is stable.

Anybody else use this with success?