sys-apps/baselayout-2.0.0 sys-apps/openrc-0.4.3-r2 net-wireless/wpa_supplicant-0.6.4 net-misc/dhcpdcd-4.0.7 When I execute "/etc/init.d/net.wlan0 start", dhcpcd does not start. # /etc/init.d/net.wlan0 start * Caching service dependencies... [ ok ] * Bringing up interface wlan0 * Starting wpa_supplicant on wlan0... [ ok ] * Starting wpa_cli on wlan0... [ ok ] * Backgrounding ...... * WARNING: net.wlan0 has started, but is inactive /var/log/message is like follow: May 24 13:11:59 note01 wlan0: direct probe to AP ##:##:##:##:##:## try 1 May 24 13:11:59 note01 wlan0 direct probe responded May 24 13:11:59 note01 wlan0: authenticate with AP ##:##:##:##:##:## May 24 13:11:59 note01 wlan0: authenticated May 24 13:11:59 note01 wlan0: associate with AP ##:##:##:##:##:## May 24 13:11:59 note01 wlan0: RX ReassocResp from ##:##:##:##:##:## (capab=0x431 status=0 aid=3) May 24 13:11:59 note01 wlan0: associated May 24 13:11:59 note01 wpa_cli: interface wlan0 CONNECTED But I execute "dhcpcd -d wlan0" manually, dhcpcd start. # dhcpcd -d wlan0 wlan0: dhcpcd 4.0.7 starting wlan0: hardware address = ##:##:##:##:##:## wlan0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT wlan0: broadcasting for a lease wlan0: sending DHCP_DISCOVER with xid 0x10dcd01c, next in 3.65 seconds wlan0: offered ###.###.###.### from ###.###.###.### wlan0: checking ###.###.###.### is available on attached networks wlan0: sending ARP probe (1 of 3), next in 1.54 seconds wlan0: sending ARP probe (2 of 3), next in 1.60 seconds wlan0: sending ARP probe (3 of 3), next in 2.00 seconds wlan0: sending DHCP_REQUEST with xid 0x10dcd01c, next in 4.51 seconds wlan0: acknowledged ###.###.###.### from ###.###.###.### wlan0: leased ###.###.###.### for 3600 seconds wlan0: adding IP address ###.###.###.###/## wlan0: adding route to 0.0.0.0/0 via ###.###.###.### wlan0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND wlan0: forking to background My /etc/conf.d/net is follow: modules="wpa_supplicant" wpa_supplicant_wlan0="-Dwext" config_wlan0="dhcp" Why dhcpcd does not start, when net.wlan0 is executed.
> * WARNING: net.wlan0 has started, but is inactive Looks like a problem with your wireless driver. Is this still an issue?
