How To: Manual Network Configuration without the need for Network Manager

[afeasfaerw23231233]

Hi, I finally got the native driver rtl8187 installed. But this time I cannot connect even without encryption.

Here's the result:

coppen@coppen-laptop:~$ iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wmaster0  Interface doesn't support scanning.

wlan0     No scan results

coppen@coppen-laptop:~$ sudo ifconfig wlan0 down
[sudo] password for coppen: 
coppen@coppen-laptop:~$ sudo dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on   LPF/wlan0/00:22:43:74:7b:05
Sending on   Socket/fallback
DHCPRELEASE on wlan0 to 192.168.123.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
coppen@coppen-laptop:~$ sudo ifconfig wlan0 up
coppen@coppen-laptop:~$ sudo iwconfig wlan0 essid "homerouter269x"
coppen@coppen-laptop:~$ sudo iwconfig wlan0 mode Managed
coppen@coppen-laptop:~$ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:22:43:74:7b:05
Sending on   LPF/wlan0/00:22:43:74:7b:05
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Then I tried install wicd and wicd connected immediately. But wicd suffered from random disconnection due to the lack of a suffix on ESSID as you mentioned on the first post.
Why this time I can't get dhclient work with the native driver?
Thanks!

EDIT: or is their any method to add a suffix for ESSID in wicd? Sorry that it is off-topic.