WiFi Cannot Scan

[tinypoodle]

udhcpc is an applet of busybox, like most commands in Core Base.
There is no conflict whatsoever, if that's what you meant to ask.

[eltone]

And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead   

hi,
Current revision == 6.21.0
dhcpcd.tcz rev.  == 5.2.12

Title:      dhcpcd.tcz
Description:   A RFC2131 compliant DHCP client.
Version:   5.2.12
Author:      Roy Marples
Original-site:   http://roy.marples.name/projects/dhcpcd
Copying-policy:   BSD
Size:      44K
Extension_by:   Arslan S.
Tags:    RFC2131 compliant DHCP client.
Comments:   This extension is PPI compatible.
Change-log:   2010/07/05 First Version 5.2.5
      2010/11/06 Updated to 5.2.8
      2011/02/03 Updated to 5.2.10
      2011/03/14 Updated to 5.2.11
Current:   2011/04/10 Updated to 5.2.12

Please update . . .
eltone
PS. Like/dislike udhcpc; it's broken and needs to be fixed

[Juanito]

Please stop this - udhcpc is not broken and does not need to be fixed - way back in this thread you even posted from a wifi connection made with udhcpc.

If you'd like dhcpcd to be updated, please pm the maintainer

[eltone]

Please stop this - udhcpc is not broken and does not need to be fixed - way back in this thread you even posted from a wifi connection made with udhcpc.

If you'd like dhcpcd to be updated, please pm the maintainer

CORRECTION!
Dear Juanito:

'dhcpcd' was/is not in this threads original intent.  It was a suggestion by someone else!

'udhcpc' is VERY unstable on two machines.  PC #2 has a WLAN adapter that has it's driver compiled into the 3.8.13 Kernel.  There is no need to cut it's firmware like PC #1 AND it still fails to get a consistant IP address just like PC #1.  I would like to start a new thread when I find time  to troubleshoot PC #2.

Sincerely,
eltone
PS.  no offense 

Current udhcpc revision == 1.22.1
TCP 5.1 udhcpc version == 1.20.2

[gerald_clark]

Do not start a new thread for an existing discussion.  It merely deprives readers from understanding what has already been discussed.

[tinypoodle]

This thread now being 125 posts long, I have not noticed any evidence that udhcpc would be "broken" or "unstable".

In your log attached to Reply #114 everything appears to be perfect to me, not sure what your issue is.

In case you attempt to run any dhcp client on an interface without first having established a fully functional net link, of course there will be no response from any server, that is only expected!

[eltone]

This thread now being 125 posts long, I have not noticed any evidence that udhcpc would be "broken" or "unstable".

In your log attached to Reply #114 everything appears to be perfect to me, not sure what your issue is.

In case you attempt to run any dhcp client on an interface without first having established a fully functional net link, of course there will be no response from any server, that is only expected!

Dear tinypoodle:

The only CLI instructions needed by PC #2 to post this note:

$ tce-load -i wireless_tools

$ sudo iwconfig wlan0 essid eltonenetwork

$ sudo iwconfig wlan0 key 6789abcdef

$ sudo iwconfig

$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid

Q: If udhcpc fails to fetch an IP address following a cold boot, using the same CLI indexing, what's the cause?  This occurs frequently on two separate PC's!

Sincerely,
eltone

[tinypoodle]

Did you check parameters of your link as advized in Reply #113?

[bmarkus]

And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead   

hi,
Current revision == 6.21.0
dhcpcd.tcz rev.  == 5.2.12

Title:      dhcpcd.tcz
Description:   A RFC2131 compliant DHCP client.
Version:   5.2.12
Author:      Roy Marples
Original-site:   http://roy.marples.name/projects/dhcpcd
Copying-policy:   BSD
Size:      44K
Extension_by:   Arslan S.
Tags:    RFC2131 compliant DHCP client.
Comments:   This extension is PPI compatible.
Change-log:   2010/07/05 First Version 5.2.5
      2010/11/06 Updated to 5.2.8
      2011/02/03 Updated to 5.2.10
      2011/03/14 Updated to 5.2.11
Current:   2011/04/10 Updated to 5.2.12

Please update . . .
eltone
PS. Like/dislike udhcpc; it's broken and needs to be fixed

Why do you think an update would solve the problem? If you are unhappy with udhcpc you can try dhcp.tcz the official ISC client. But trust others, it IS NOT an udhcp issue!

[eltone]

Remember that extension deps are recursive, there is no need to have most of those extensions named in onboot.lst

hi,

I just established udhcpc finding an IP address fiasco linked to invalid extensions named in onboot.lst!

Q: How can invalid onboot.lst extensions get blacklisted from ever existing in onboot.lst?

eltone

[tinypoodle]

Use "apps" for extension maintenance.

[Rich]

Hi eltone
You are attempting take a quote by gerald_clark and use it out of context.
The existing discussion is about wireless network connections. You are now starting a new topic and that should be in a
separate thread.

[eltone]

Why do you think an update would solve the problem? If you are unhappy with udhcpc you can try dhcp.tcz the official ISC client. But trust others, it IS NOT an udhcp issue!

Dear bmarkus:

Here is the problem, if I take the functional LiveUSB w/udhcpc to another PC, udhcpc freezes 80% and fully functions the other 20% of the time!

'dhcp.tcz' is not in the tc-4.x repo, so I just installed the 'dhcpcd.tcz'  DHCP client on my stable 4.77 LiveUSB, to test:

Code: [Select]


tc@box:~$ sudo dhcpcd wlan0 -X 192.168.0.64 -h box
dhcpcd[2266]: version 5.2.12 starting
dhcpcd[2266]: wlan0: waiting for carrier
dhcpcd[2266]: wlan0: carrier acquired
dhcpcd[2266]: wlan0: broadcasting for a lease
dhcpcd[2266]: wlan0: offered 192.168.0.64 from 192.168.0.1
dhcpcd[2266]: wlan0: acknowledged 192.168.0.64 from 192.168.0.1
dhcpcd[2266]: wlan0: checking for 192.168.0.64
dhcpcd[2266]: wlan0: leased 192.168.0.64 for 86400 seconds
dhcpcd[2266]: forked to background, child pid 2303
tc@box:~$

It appears dhcpcd accepted the static IP address, but NO AP connection, yet NO errors were trapped!

To post this note, udhcpc was used:

Code: [Select]

c@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending select for 192.168.0.64...
Lease of 192.168.0.64 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 205.171.9.25
adding dns 8.8.4.4
adding dns 205.171.6.25
adding dns 8.8.8.8
tc@box:~$


This dialog indicates dhcpcd didn't add the dns server addresses!
Q:  How can the essential dns servers be functional w/dhcpcd?

Sincerely,
eltone

[bmarkus]

Do you have the same problem connecting to other AP/router or just this one?

[gerald_clark]

Your claims do not match your evidence.
You could not get an IP address  if you were not associated to an access point.

I don't know how you are specifying 4 dns servers. Only 3 can be used.