unable to associate with wireless access point at home
Hi,
I have dell E1505 laptop, which has a Intel PRO/Wireless 3945ABG card. I'm running slackware 12.0, with kernel 2.6.21. The device it self works fine under linux. Using the native driver (so not ndiswrapper) I can connect to wireless networks just fine. Until about a week ago, everything was ok. But then suddenly, I started having trouble finding my wirless access point at home. Doing "/sbin/iwlist scan" I often cannot find the SSID belonging to my home connection. Under windows it shows up just fine. I have the following script to create a wireless connection: Code:
#!/bin/bash So my question is, why do I have no troubles under windows and why suddenly do I have them under linux? Help me please. |
Quote:
Quote:
|
Quote:
Quote:
That the hell?? Why so inconsistent? |
Quote:
|
It seems that getting closer to the AP helps. The AP is in another room.
But how come windows can pick up the signal without much problem, while under linux I need to move closer? |
You keep asking questions that compare ClippyOS with GNU/Linux but not supplying any data to work with. That doesn't help us to help you. You know perfectly well a lot of vendors see absolutely no market in GNU/Linux. So the fact a lot of drivers *just work* is not a tribute to standards, vendors or whatever but only to those who managed to hack a driver together.
|
Quote:
I know I should give you all the information possible but I just don't know what to do next. I just don't even know where to begin. Should I change something in the AP to get it to make the signal stronger? Should I report the signal strenth I'm getting in my room? Should I update the driver. Change the kernel? Are there any log files I can look at? Any config files I should edit? I rarly ever come to this forum anymore because I mostly am able to figure out problems on my own. But this time I'm stuck. So can you please help me?! If it helps anything, here is the output of iwlist scan with my AP (finally) on it. Code:
eth1 Scan completed : |
Let's dissect the situation:
0. "It Just Works" in Windows, 1. it works intermittently in GNU/Linux, 2. behaviour changed at a defined point in time, 3. symptoms are not finding SSID. The situation seems one-sided, behaviour changed at a distinct point in time so there is a starting point looking for changes: "about one week ago". So let's ask questions that try to find out what changed over time: Questions: 0. So what changed?: answer incomplete, 1. (re)configuration on the machine?: not answered at all, 2. (re)configuration of the AP?: not answered at all, 3. Software updates?: answer not complete, 4. Any other APs near?: answer incomplete, 5. Does iwconfig (<- should be wpa_cli) (..) show any clues?: not answered at all. Additions: 0. "It seems that getting closer to the AP helps. The AP is in another room", 1. Output showing WPA_PSK (TKIP) usage. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
|
Okey so lets stop biting each others head off and get on with it then.
Quote:
And I changed nothing in my hardware. 1 & 2. Do you really think that I woulden't mention that if I had?? 4. Okey, I admit, I should of listed more completly. The thing is, because the problem is not very reproducable, I can't just give you the output of iwlist now (I associated with my AP just fine just now). I'll have to wait for the problem to occure again and see if there are possible interferences. 5. wpa_cli ? I didn't know this program even existed. I will check out it's man page to figure out how to work it. I also admit I should probebly have played a bit with iwconfig to see if I could get an association like that. Maybe it will report error's whch can help solve the problem. Like I said, it has little use to do all of this now. I'll wait until the problem reoccures and we will take it from there. Quote:
That said, maybe I should try that. Quote:
Thanks, your help is appreciated. |
Reading your post in more detail, I see that you are linking to a different driver then the one I use. I use the driver "ipw3945" and it seems you are refering to "iwlwifi". If nothing else works, I'll try that driver.
Thanks again. |
Quote:
Quote:
|
Only time I had connect problems.. my neighbor kept jumping channels and trying to use my channel which would then show his ap because his router and range extender beat my routers power output. so i just had a chat with him... no problems now.
I knew i was on ch 8 he was on 1-2-4-6-8-11 etc. said he was just trying to set it up. thought my router went out at first. (i dont use clippy) |
All times are GMT -5. The time now is 08:21 PM. |