Basic wireless tips

[coffeetime]

Howdy gang !


Well, since we had some issues with wireless networking, I would like to post some informations, which could help new users and also the "older ones".

OK, when you have problems with your wifi, don't panic. I now it's stressing and frustrating, but posting with negative attitude, doesn't bring nothing. So, calm down, take a deep breath and have a cup of coffee or tea. It will do you good.
Some of our favourite brands :



Before posting, check the following and include it in your post:

What do you use?
- Gnome
- KDE 4
- XFCE
- e17
- XFCE
- LXDE
- OpenBox
- Zen mini
- kernel version

To check kernel version, open Konsole, type:
uname -r

Another good info. is to specify your pc (brand, type & model). If you're using usb dongle or pcmcia card, let us know. It's also very important to state you're using encrypted wireless network. I suggest you try to make it work without encryption first. And yet another, many times over looked, but important thing:
Check, if your lapptop has a switch on/off for wireless!

Now we need to know, if your wireless controller is recognized by the system and associated with your wireless network. Open Konsole, copy/paste the following:
-lspci
-lsusb (if you use USB wireless dongle)
-iwconfig


You can also check in PCLinuxOS Control Center (PCC), if your wireless card is recongnized+loaded modul. Press on pcc icon
or hit Alt+F2 and type pcc. Than click on Hardware/Browse and configure hardware



Locate on the left side your wireless card. Click on it and you'll get needed informations:



As you can see in my case, my wifi card was recognized (PRO/Wireless 3945ABG [Golan] Network Connection) and loaded modul is iwl3945.

The most important informations, which usually show what is happening with your wireless issues are  in /etc. Open Konsole and copy/paste the following commands:

cat /etc/modprobe.conf
cat /etc/modprobe.preload
cat /etc/sysconfig/network-scripts/ifcfg-wlan0 <---this may vary(sometimes your wifi controller can be also recoginzed as eth1,ath0...)
cat /etc/modprobe.d/blacklist

When you're posting back, please post each command separately. The easiest way to do it, is:

your Konsole output

your Konsole output

etc, etc....

Sometimes, reseting wireless connection is helpful. Konsole, go root, copy/paste:
service -f network

Don't forget to check you wireless router settings (MAC filtering, hidden EESID...). First, try to "Ping" your wireless router. The most common used IP address is 192.168.1.1 [check your wireless router setup manual]. To ping the wireless router, open Konsole and type:

ping <the IP address of your router>

In my case:

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.02 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.01 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.01 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.01 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.17 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.14 ms

This acknowledges you, that you "see"/have established the connection with your wireless router.


If something went wrong, let's say that after some updates your wifi is not working as before or not at all, you can always help yourself with running Pclos Live CD. While running it, try to create wireless connection and check in PCC the above mentioned things. And remember, Live CD is for one time session only.

If you're using ndiswrapper, open Konsole, copy/paste:
ndiswrapper -l

To explore more about ndiswrapper, check out PCLinuxOS Magazine.

To understand better:
- lspci
- iwconfig
- modprobe.conf
- ifconfig


To obtain additional information from Konsole use the following commands:

Manually set wireless interface speed:

Code:

iwconfig wlan0 rate 1Mb/s fixed

[this may vary-check your wireless controller designation-ath0, wlan0, eth1...]

List wireless networks in range:

Code:

iwlist scan

List network interfaces:

Code:

ip link show

List addresses for interfaces:

Code:

ip addr show

List routing table:

Code:

ip route show

Lookup DNS ip address for name or vice versa:
[example]

Code:

host pclinuxos.com

Lookup local ip address (equivalent to host `hostname`):

Code:

hostname -i

List internet services on a system:

Code:

netstat -tupl

List active connections to/from system:

Code:

netstat -tup

Sometimes it's good to use rfkill. Rfkill is a small tool to query the state of the rfkill switches, buttons and subsystem interfaces.

Open Synaptic and install rfkill.

Rfkill-how to:

Printing the current rfkill status:

Code:

rfkill list

or

Code:

rfkill list all

Listening to events:

Code:

rfkill event

Setting/clearing a soft block:

   to get the rfkill index:
1.

Code:

rfkill list

   than

2.

Code:

rfkill block <index>|<type>

    to unblock

3  

Code:

rfkill unblock <index>|<type>

Example

$ rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes

First you must go su and than:

Code:

rfkill event unblock 0

Reboot!

It helps sometimes to unblock everything..Konsole, copy/paste:

Code:

rfkill unblock all

Reboot!


To check, if your wireless connection got authenticated, associated and ready:

Open Konsole, copy/paste:

Code:

dmesg | tail -30

Example:

$ dmesg | tail -30
ADDRCONF(NETDEV_UP): eth0: link is not ready
iwlagn 0000:02:00.0: firmware: requesting iwlwifi-5000-2.ucode
iwlagn 0000:02:00.0: loaded firmware version 8.24.2.12
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
NET: Registered protocol family 17
usbcore: registered new interface driver snd-usb-audio
wlan0: direct probe to AP 00:18:f8:cd:08:55 (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:18:f8:cd:08:55 (try 1)
wlan0: authenticated
wlan0: associate with AP 00:18:f8:cd:08:55 (try 1)
wlan0: RX AssocResp from 00:18:f8:cd:08:55 (capab=0x401 status=0 aid=3)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
martian source 255.255.255.255 from 192.168.1.1, on dev wlan0
ll header: ff:ff:ff:ff:ff:ff:00:18:f8:cd:08:53:08:00
wlan0: no IPv6 routers present

When there're problems with your wifi connection, don't forget it's NOT every time Linux problem. Blame it on the lazy manufacturer! So check the Linux wireless database, before buying. It will save you time, money and nerves.

Since Linux works almost everywhere, check, if your wireless router supports Linux software, like:
- DD-WRT
- Tomato

Believe me, it's stable and works like a charm.

If you managed to make your wifi working, please post back, as it can help some sad & frustrated Pclos user out there.










 

[Clawinus]

Hi coffetime,

thanks for the information on wifi problems. a
I have trouble, too, and will use your advise.

But I have a question re the screen images in your text.
When I click on them to get them enlarged
I am automatically transferred to the site:
http://img158.imageshack.us/my.php?image=pcc1.png

which my browser declares to be suspicious.

Is this transfer intended?

Many thanks Clawinus

[CtrlAltDel]

Good post coffeetime..

I'll just add that if it's a laptop with an on/off switch, the switch must be in the on position BEFORE booting the laptop..  If you're at the desktop when you switch it on, you will need to reboot..

Cheers,


CtrlAltDel

[gseaman]

I bought a dlink wireless card for my desktop computer over a year ago. My wife needed the router next to her computer since I don't think there are any wireless cards with drivers for win98, (long story). I eventually got it working in 2007. It worked immediately in minime. In 2009.1, I had to go back to ndiswrapper. Each time there was an upgrade, I lost my wireless. I use mostly my laptop, so I haven't tried to hard to find a fix, but I decided to try again. After going through each step of this guide, I checked wpa_supplicant.conf and realized that although I kept entering my wpa2 password into pcc and it 'seemed' to be remembering it, the wpa_supplicant.conf did not have it. So I scrolled up the file for the example and put the password where it was supposed to be. Voila, wireless was back.

Sorry for the long story. Here's my point. PCC does not do exactly what it seems to be doing. Wireless configuration should be all in one file (or at least specific information should be in only one place.) This way it doesn't matter which front-end software is being used it still works the same.

I think in some cases we've blamed the drivers for problems in PCC.

Galen

[gseaman]

You are right. I 'knew' they had to be somewhere. Why then, I wonder, did wireless only work for me when I put the info into /etc/wpa_supplicant.conf? Could it be hardcoded into ndiswrapper? It couldn't be the driver itself, since it's a windows driver.

Galen

[wolfy]

I like the tips and see the rt2500 ralink card is listed there asthros too but it doesn't work on my desktop 2009.1 yes the old 2008 2007 did but it should work on the newer hope you find a fix . Asus Eeepc laptop doesn't boot any of them at all tried everything in options at boot must not see the hardware like the ssd drive maybe oh well zen linux works on it

[Joble]

oh well zen linux works on it

Good, then enjoy it.  eeepc issues have been improved, worked on etc.... but, depending on the model number there are issues with wireless, webcam, drives, etc... etc....  On any distro.

[linuxnoobatron]

Hello all  

I installed PCLOS on my desktop this morning. Set up was pretty easy but I am
having some issues with my belkin N1 wireless USB Receiver.
It's picking up my network and the others which are in the area, but it wont connect..


Now it is also saying that it is a "Railtech"  Something or other and not a belkin. So I'm thinking it's a driver thing... But I was also thinking that if it was a driver issue that it wouldn't see any of the networks in the area?

Any idea's?

[The Chief]

I don't think there are any wireless cards with drivers for win98

Not true.  I ran a LinkSys PCMCIA wireless card under Win 98 for years.   It came with a CD containing Win 98, Win 2K and Win XP drivers.

And now run it just fine under PCLOS. 

Check for drivers on the manufacturers web site.

Of course, what you say may be true for anything in current production....

Sorry I'm so late - just stumbled across this....   

[Sparky]

Thank you for that post on basic wireless tips.

I do not really have any problem in getting onto the in web but have noticed that when ever I move away from the wireless AP I am still connected to the wireless but cant get to the web. I mean leaving the room where the AP is situated and going into the kitchen. Trust me its not a big apartment. Using MS windows the wireless works strong from that point but I'm having trouble with PClinuxOS.

I have a Toshiba Satilite A215-S7437 running PCLOS 2009 with KDE 4.3.1. I love that OS. Thats like my biggest issue at the moment. As a result I am kind of forced to stay in the room very close to the AP. Any help on this would be great. Oh, and my kernel version is 2.6.26.8.tex3.

Thanks guys
 

[prestonwynn]

Does this also apply with Clearwire, if I have the 4G+ hotspot?
Everytime i boot up my laptop it recognizes the hotspot bit after about 5 or 10 minutes it cuts out.
Not sure what to do and im  new to pclinuxos gnome.
4256220684-Arthur
Please help!!

[smileeb]

Hello all  

I installed PCLOS on my desktop this morning. Set up was pretty easy but I am
having some issues with my belkin N1 wireless USB Receiver.
It's picking up my network and the others which are in the area, but it wont connect..

Any idea's?

It sounds like these are password protect sites of your neighbors and you need their permission and password.
There is a strong possibility they will not give you the password to use their wireless.

[5]

hi there coffeetime

good post, but id include some more topics on it, if you could amend your original post, please:

1: in case of new laptops, how to get the firmware/win driver and incorporate it to pclos

2. ndiswrapper vs wp supplicant

3. using n(draft not anymore) network links on linux, since i noticed folks having trouble with it, var posts on the net

4. wifi kill switches, hardware vs software, including the bios settings(enable vs disable note, the general terms)

5. setting up the router/wireless modem via web browser in order to set min common denominator security connection/maybe radius etc, whatever you think of putting there if you feel like doing it, basic info on what to touch, what not on:
                                                                                                                             a) cable tv modem
                                                                                                                             b) adsl
                                                                                                                             c) generic router for home network

that would round up the problem solving to even the greater level than it is at present, and its wuite nice