Let's just say that netmanager is not my favourite utility.  In this
particular case, I'd say that if you want to use netmanager (and not
modify the enumerators to launch dhcp.client yourself... Which is
something that is definitely worth considering since it gives you more
control), the best thing to do is to change netmanager to match your
system.

The source is here (look for the do_dhcp function).
http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/utils/n/n
etmanager/netmanager.c?root=core_networking&rev=409&system=exsy1001&view
=markup

As I can tell from this thread, it's unlikely that one setting will work
for everyone :>

	Robert.


-----Original Message-----
From: Mario Charest [mailto:community-noreply@qnx.com] 
Sent: Friday, January 30, 2009 11:01 AM
To: general-networking
Subject: RE: dhcp.client startup trouble

The cisco switches we're using take 30 seconds to auto-negotiate the
link...

> -----Original Message-----
> From: Robert Craig [mailto:community-noreply@qnx.com]
> Sent: January-30-09 10:51 AM
> To: general-networking
> Subject: RE: dhcp.client startup trouble
> 
> I think that what's happening is that your network card is taking too 
> long to auto-negotiate the link.  This results in dhcp.client (which 
> is started with the -T10 option by netmanager) to time out and exit 
> with an error.  Unfortunately, this timeout value is hard-coded in 
> netmanager.c (look at the do_dhcp function).  I'm not sure about 
> increasing this value in the product.  While netmanager is waiting for

> dhcp.client to complete, the booting process stops, so if your network

> card doesn't work, this results in an extra 10 seconds for the boot 
> process to complete.  (Of course, you can always come back with "but 
> without a network connection, I can't do anything anyway, but that's 
> another issue :>).
> 
> Here's a custom x86 build of netmanager that has that timeout 
> increased to 20 seconds to try out.  (Backup and then replace
/bin/netmanager).
> Let me know if that works out for you.
> 
> 	Robert.
> 
> -----Original Message-----
> From: James Puckett [mailto:community-noreply@qnx.com]
> Sent: Thursday, January 29, 2009 6:31 PM
> To: general-networking
> Subject: dhcp.client startup trouble
> 
> I'm running 6.4.0 on a Gigabyte G31M-ES2L motherboard (which uses the 
> RTL 8111C LAN chip) and a dual core CPU.
> 
> I have the network mode in net.cfg set to dhcp but on a reboot 
> dhcp.client is not started.  I added it to rc.local but it doesn't 
> work correctly.  dhcp.client is started and running when I log in but 
> ifconfig doesn't show an IP address (not even 0.0.0.0).  If at that 
> point I reconfigure the network via phlip, the initial instance of 
> dhcp.client is killed, a new one is started, and I get a valid IP 
> address.  It will also start working if I manually restart
dhcp.client.
> 
> However, if I invoke dhcp.client in .profile for the root account I 
> get different behavior.  If I log in as soon as I can after a reboot I

> get the same behavior as above.  If I wait ten seconds before logging 
> in ifconfig reports an IP of 0.0.0.0 for around 15 seconds and then 
> gets a valid IP.  If I let the machine sit on the login screen for 
> around 30 seconds before I log in everything is fine.
> 
> 
> Also on a side note, I left the machine on last night and when I came 
> in today io-pkt-v4-hc was alternating between the cores about once a 
> second taking 100% CPU time.  I was unable to slay io-pkt-v4-hc and 
> reset the machine with a shutdown command.
> 
> Anyone have any ideas?
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post21030
> 
> 
> 
>...

ifconfig will stop reporting an IP if dhcp.client stops running, so
that's still consistent with dhcp.client timing out.  Maybe I need to
bump up the timeout even more.  Here's another version with a 60 second
timeout.  The problem here is that dhcp.client goes into exponential
back off, so if the interface doesn't come up early on, it could take a
much longer time to get assigned an address.

In terms of your other issues, I'd seriously wonder about the hardware.
The fact that the NIC doesn't show up in pci -vvvv is a bad thing.  If
the NIC doesn't show up in the PCI server, the stack isn't going to be
able to do much with it.  By "reboot" do you mean software reboot or a
power cycle?

    R. 

-----Original Message-----
From: James Puckett [mailto:community-noreply@qnx.com] 
Sent: Friday, January 30, 2009 3:09 PM
To: general-networking
Subject: Re: RE: dhcp.client startup trouble

I tried the new netmanager, thanks for providing it.

It's still doing the same thing however.  When I log in ifconfig reports
an IP of 0.0.0.0 for 5-10 seconds then it stops reporting an IP at all.
During the period that ifconfig reports the 0.0.0.0 IP, nicinfo shows
that the link is up.  After ifconfig stops reporting any IP I run
dhcp.client manually and everything works.

While testing the new netmanager I came across some other strange
behavior.  About every five reboots I can't get dhcp.client to work at
all.  ifconfig shows an ethernet adapter and nicinfo shows that the link
is down but the nic does not show up in the output of pci -vvv.  If I
kill io-pkt-v4-hc and restart it it won't recognize the nic.  I
discussed this with a co-worker and he said that he saw the same
behavior on a separate, identically configured machine.

I've attached the output of sloginfo and pci -vvv for both cases.

_______________________________________________
General
http://community.qnx.com/sf/go/post21135