is there a definitive HOWTO to set up wireless?

kevison · 07-21-2016, 10:11 AM

I am using network manager to handle wireless on my 14.2 box. When I log in I have a shell script to set up wlan0 (iwconfig wlan0 essid <...> key <....> etc...) however in order to get wireless turned on or connected I have to go to my network status in XFCE to connect to my wireless box.

Is there a definitive HOWTO set up wireless using network manager so that I I dont have to always run iwconfig or use XFCE to connect to my wireless? I havent found any consistent instructions.

Any help to link to a definitive howto would be appreciated.

thanks

RadicalDreamer · 07-21-2016, 11:32 AM

I used the wicd package in extra!

bassmadrigal · 07-22-2016, 09:52 AM

If you only intend on connecting to one wireless network, you can easily set up the system to connect to it using just /etc/rc.d/rc.inet1.conf and /etc/wpa_supplicant.conf. However, before you do that, make sure you clear your cusomizations by running netconfig and selecting loopback. Once that is done, you can continue by setting up your wpa_supplicant.conf file by running the following as root.

Code:

wpa_passphrase $YOUR_SSID $YOUR_PASSWD >> /etc/wpa_supplicant.conf

Then edit your /etc/rc.d/rc.inet1.conf file and remove the pound sign from the below sections under the fifth (labeled as [4]) adapter:

Code:

IFNAME[4]="wlan0"
USE_DHCP[4]="yes"
WLAN_WPA[4]="wpa_supplicant"

You might need to specify the WLAN_WPADRIVER[4] depending on what your device uses. Most wireless cards nowadays use nl80211.

Once that is done, you should be able to bring up the interface with:

Code:

/etc/rc.d/rc.inet1 wlan0_start

If that works, then you should be done and the next time you reboot, you should have wireless as soon as rc.inet1 is processed during the startup.

kevison · 07-23-2016, 06:05 PM

Quote:

Originally Posted by bassmadrigal

If you only intend on connecting to one wireless network, you can easily set up the system to connect to it using just /etc/rc.d/rc.inet1.conf and /etc/wpa_supplicant.conf. However, before you do that, make sure you clear your cusomizations by running netconfig and selecting loopback. Once that is done, you can continue by setting up your wpa_supplicant.conf file by running the following as root.

Code:

wpa_passphrase $YOUR_SSID $YOUR_PASSWD >> /etc/wpa_supplicant.conf

Then edit your /etc/rc.d/rc.inet1.conf file and remove the pound sign from the below sections under the fifth (labeled as [4]) adapter:

Code:

IFNAME[4]="wlan0"
USE_DHCP[4]="yes"
WLAN_WPA[4]="wpa_supplicant"

You might need to specify the WLAN_WPADRIVER[4] depending on what your device uses. Most wireless cards nowadays use nl80211.

Once that is done, you should be able to bring up the interface with:

Code:

/etc/rc.d/rc.inet1 wlan0_start

If that works, then you should be done and the next time you reboot, you should have wireless as soon as rc.inet1 is processed during the startup.

This is assuming a person is using WPA correct? It a person is using WEP (yeah I know...) would this still apply?

Alien Bob · 07-23-2016, 06:35 PM

You may find some more info (on WEP too) here: http://alien.slackbook.org/dokuwiki/...in_rcinet1conf

bassmadrigal · 07-23-2016, 07:11 PM

Quote:

Originally Posted by kevison

This is assuming a person is using WPA correct? It a person is using WEP (yeah I know...) would this still apply?

<soapbox>As you seem to already be aware, WEP is not a good thing to be using... if you have the ability to use WPA, I would highly recommended it. </soapbox>

But, if you do insist to use WEP, you can just modify /etc/rc.d/rc.inet1.conf. Just uncomment the pertinent sections and put in your information. Alien Bob's link should provide you more detailed information.

kevison · 07-23-2016, 07:24 PM

Thanks guys! I will post back when I get this up and going. Tired of having to have a ethernet cable floating all over the place lol.

kevison · 07-27-2016, 02:26 PM

Another question I have is how do I cause the wireless to active when I login without having to start XFCE?

bassmadrigal · 07-27-2016, 03:31 PM

If you did set it up the way I posted, it should be up and running before you even get your text login prompt. You don't even have to start a GUI.

kevison · 07-28-2016, 07:35 AM

Quote:

Originally Posted by bassmadrigal

If you did set it up the way I posted, it should be up and running before you even get your text login prompt. You don't even have to start a GUI.

Here is my rc.inet1.conf wlan0 section:

Code:

## config information for wlan0... using wep... and yes i know thats not a necessarily good.... :p 
IFNAME[4]="wlan0"
USE_DHCP[4]="yes"
WLAN_ESSID[4]=<my ssid here>
WLAN_MODE[4]=Managed
WLAN_KEY[4]="<(wep hex value here)>"

I had run netconfig and set to loopback. However after boot up and login i try to ping a website but it says unknown at the CLI. So... what am I missing?

onebuck · 07-28-2016, 11:09 AM

Hi,

Do you have the gateway defined in '/etc/rc.d/rc.inet1.conf'?

Code:

# Default gateway IP address:                                                                                                                                      
GATEWAY="192.168.NNN.NNN"

Replace 'NNN.NNN' with your LAN settings.

Hope this helps.
Have fun & enjoy!

bassmadrigal · 07-28-2016, 11:47 AM

@onebuck, having a gateway specified shouldn't be required since dhcp is set to yes, but it probably wouldn't hurt to add it to check.

@kevison, let's do some checking to see if we can figure out what's going on.

When you get to your command prompt and log in, what is the output of the following commands?

Code:

iwconfig
ifconfig
cat /etc/resolv.conf
ping 192.168.1.1   # Or whatever your IP address is for your router/gateway
ping google.com

If you don't have a connection after all that, try typing /etc/rc.d/rc.inet1 wlan0_restart and provide the output of all those commands again.

onebuck · 07-28-2016, 02:02 PM

Hi,

I know, but have been in the habit of using a gateway in my '/etc/rc.d/rc.inet1.conf'. Same with my '/etc/resolv.conf'. I leave my files as static and really have no problems. I move between systems so often that it is just a habit from long ago.

EDIT: at kevison in addition to requested output, please post the kernel route table from cli; 'route -n'

Thanks for clearing it for others!