[SOLVED] Wifi at boot?

SavoTU · 08-13-2014, 05:02 AM

I have been trying to setup my wireless to work at boot but am now stuck.

I can get wifi to work if i run

Code:

wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan1

before restarting rc.inet1 which makes me think i have that set up correctly

wpa_supplicant does not seem to start if i just run /etc/rc.d/rc.inet1 restart wlan1

log

Code:

Aug 13 10:48:59 home logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo down
Aug 13 10:48:59 home logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo 127.0.0.1
Aug 13 10:48:59 home logger: /etc/rc.d/rc.inet1:  /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
Aug 13 10:48:59 home logger: /etc/rc.d/rc.inet1:  eth0 interface is not configured in /etc/rc.d/rc.inet1.conf
Aug 13 10:48:59 home logger: /etc/rc.d/rc.inet1:  eth1 interface does not exist (yet)
Aug 13 10:48:59 home logger: /etc/rc.d/rc.inet1:  eth2 interface does not exist (yet)
Aug 13 10:48:59 home logger: /etc/rc.d/rc.inet1:  eth3 interface does not exist (yet)
Aug 13 10:48:59 home logger: /etc/rc.d/rc.inet1:  /sbin/dhcpcd -t 10  wlan1
Aug 13 10:48:59 home dhcpcd[24964]: version 6.0.5 starting
Aug 13 10:48:59 home kernel: [51421.584191] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Aug 13 10:48:59 home dhcpcd[24964]: wlan1: waiting for carrier
Aug 13 10:49:17 home dhcpcd[24964]: exited
Aug 13 10:49:17 home logger: /etc/rc.d/rc.inet1:  eth5 interface does not exist (yet)

/etc/wpa_supplicant.conf

Code:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

network={
  scan_ssid=1
  proto=RSN
  auth_alg=OPEN 
  ssid="OpenWrt"
  key_mgmt=WPA-PSK
  pairwise=TKIP CCMP
  group=TKIP CCMP
  psk="*********************"
}

/etc/rc.d/rc.inet1.conf

Code:

IFNAME[4]="wlan1"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
WLAN_ESSID[4]=OpenWrt
WLAN_MODE[4]=Managed
WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPAWAIT[4]=20
#WLAN_WPADRIVER[4]="ndiswrapper"

business_kid · 08-13-2014, 06:31 AM

why wlan1? Why not wlan0?

anyhow, what have you set up in /etc/rc.wireless.conf? That's a better place to set up wireless. Then just blank the rc.inet1 settings.

Alien Bob · 08-13-2014, 07:06 AM

Quote:

Originally Posted by business_kid

why wlan1? Why not wlan0?

anyhow, what have you set up in /etc/rc.wireless.conf? That's a better place to set up wireless. Then just blank the rc.inet1 settings.

Wrong answer.

Never use rc.wireless.conf please, use rc.inet1.conf also for your wireless configuration.
In "man rc.inet1.conf" you will find "/etc/rc.d/rc.wireless.conf - configuration parameter file ( deprecated )".

More about the topic here: http://alien.slackbook.org/dokuwiki/...onf_deprecated

Eric

SavoTU · 08-13-2014, 12:05 PM

I think its wlan1 from when i had two wifi cards in.

Do either of you have any ideas why wpa_supplicant is not starting when the network is started?

WhiteWolf1776 · 08-13-2014, 01:29 PM

These lines should not be needed:
WLAN_ESSID[4]=OpenWrt
WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"

This should be set in the /etc/wpa_supplicant.conf and can be handled with the wpa_gui if you are in x and want it just handled.

I've also never needed these lines:
WLAN_MODE[4]=Managed
WLAN_WPAWAIT[4]=20

and would recommend leaving these lines commented out:
IPADDR[4]=""
NETMASK[4]=""

SavoTU · 08-13-2014, 02:19 PM

Thanks for the response I have tried removing the lines above but it has not helped, also the WLAN_WPAWAIT[4]=20 i have tried without and with different values but that has not helped either.

Any other ideas?

Didier Spaier · 08-13-2014, 02:22 PM

Quote:

Originally Posted by SavoTU

Any other ideas?

Did you try NetworkManager (then "nm-applet &" to display the connection widget)?

SavoTU · 08-13-2014, 02:30 PM

My problem started when i wanted to upgrade from runlevel 3, as soon as i stop kde my network goes down, i stopped networkmanager and decided to use wpa_supplement.

If i start wpa_supplement manually then run /etc/rc.d/rc.inet1 restart wlan1 I have no problems (that is how i am online now) but as far as i understand it just running /etc/rc.d/rc.inet1 should trigger wpa to connect which would give me wifi at boot.

louigi600 · 08-13-2014, 03:52 PM

I've noticed that on some wireless cards it's necessary to unload and reload it's driver modules after deconfiguring/stoppong the interface, failing to do that resulted in the inability to reassociate it to any access point.
Could it be that you're hitting a similar issue ?

Martinus2u · 08-13-2014, 04:53 PM

I've done something similar ages ago and documented it here:

http://www.frogge.de/pepper/p50ij/p50ij.html#wlan

ymmv

coldbeer · 08-13-2014, 09:42 PM

Quote:

Originally Posted by SavoTU

My problem started when i wanted to upgrade from runlevel 3, as soon as i stop kde my network goes down, i stopped networkmanager and decided to use wpa_supplement.

If i start wpa_supplement manually then run /etc/rc.d/rc.inet1 restart wlan1 I have no problems (that is how i am online now) but as far as i understand it just running /etc/rc.d/rc.inet1 should trigger wpa to connect which would give me wifi at boot.

Do you have eth0 parameters still set at the top of rc.inet1.conf? Once you have the wireless working manually, if you still have eth0 params set, the networks will clash on a reboot. You should comment out any ethx params in rc.inet1.conf and only have the wlan params in order to have it boot to wlan.

Goobers · 08-13-2014, 11:43 PM

I've since switched to using WICD since I want to be able to use my laptop with multiple networks without too much hassle. However, I did use inet1 and supplicant before that.

Quote:

Originally Posted by SavoTU

/etc/rc.d/rc.inet1.conf

Code:

IFNAME[4]="wlan1"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
WLAN_ESSID[4]=OpenWrt
WLAN_MODE[4]=Managed
WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPAWAIT[4]=20
#WLAN_WPADRIVER[4]="ndiswrapper"

I only have

Code:

IFNAME[4]="wlan0"
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]="systemname"
WLAN_ESSID[4]=ssidname
WLAN_WPA[4]="wpa_supplicant"

everything else stays commented out...

that line for wpapsk in inet1 is incorrect... looks like you chopped out a chunk of the example line.

try commenting out yours until only those 5 are left.

SavoTU · 08-15-2014, 04:53 AM

Thanks for the suggestions. I have edited my config files made sure rc.wireless is -x rebooted my pc but still inet1 is not starting wpa_supplicant.

Alien Bob · 08-15-2014, 05:07 AM

Quote:

Originally Posted by SavoTU

Thanks for the suggestions. I have edited my config files made sure rc.wireless is -x rebooted my pc but still inet1 is not starting wpa_supplicant.

Eh, "made sure rc.wireless is -x"? You removed the executable bit from rc.wireless? That will be the cause then, rc.wireless needs to be executable because that is what starts wpa_supplicant.

Eric

SavoTU · 08-15-2014, 05:14 AM

Thanks i feel silly now but it is working as expected. I had assumed that since rc.wireless.conf was deprecated the same would be true of rc.wireless.