|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
||||
Forgot to mention I am running FBSD 7.1 release i386. Fresh install.
__________________
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
|
|||
You can disable bgscan, it is really usefull only when roaming is not MANUAL.
What is difference in setup with device that lost carrier and one which does not? You also can explore wlandebug(8) ... |
|
||||
Thanks for the reply richardpl,
The main difference between the two machines is the OS: one is running Windows and the other FreeBSD. wlandebug looks exactly like the magic wand that will help me identifying the problem, however the man page doesn't mention where the debug output is shown... The box is currently rebuilding world and kernel, I'll continue experimenting as soon as it finishes. Thanks again!
__________________
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
|
|||
Quote:
You could also enable ath(4) special debug options available in driver itself. Note that such ath debug options are documented only in ath source and are mostly used by developers. But enable first one by one so you dont get lost in forest of console messages. You could also sniff WLAN packets with another device while carrier get lost. But understanding such captured output is another story .... |
|
||||
Thanks!
I've began playing with wlandebug and I see that my client connects and reconnects very often to the access point. Accordingly, I see the following in my router's logs: Code:
Jan/20/2009 15:59:00 Authenticating...... 00-1e-58-a3-08-91 Jan/20/2009 15:58:59 Wireless PC connected 00-1e-58-a3-08-91 Jan/20/2009 15:57:31 Authentication Success 00-1e-58-a3-08-91 Jan/20/2009 15:57:30 Authenticating...... 00-1e-58-a3-08-91 Jan/20/2009 15:57:30 Wireless PC connected 00-1e-58-a3-08-91 Jan/20/2009 15:52:14 Authentication Success 00-1e-58-a3-08-91 Jan/20/2009 15:52:13 Authenticating...... 00-1e-58-a3-08-91 Jan/20/2009 15:52:13 Wireless PC connected 00-1e-58-a3-08-91 Jan/20/2009 15:51:18 Authenticating...... 00-1e-58-a3-08-91 Jan/20/2009 15:51:18 Wireless PC connected 00-1e-58-a3-08-91
__________________
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
|
|||
It can be a bit of a blind guess. But if you can, try to connect from a wifi-enabled windoze box. This is because this constant reconections can be caused by special instructions embedded in some router's firmware that makes the router drop conections if it detects the computer uses any non-Windoze operating system.
|
|
||||
Quote:
I am going to test connecting without WPA, just to see if the problem could come from misconfigured encryption.
__________________
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
|
|||
Well if it works from OSX you could try copying the relevant config files/folders from OSX to the BSD box. After all OSX is a BSD OS.
|
|
||||
Quote:
Anyway, I've replaced WPA2 by WEP (security is not much a concern here) and I've fixed a big part of the problem. I can now download things at 600ko/s and I have a lot less packet loss. However, sometimes everything hangs. All I could find is the following kernel log, highlighted by periodic: Code:
+ath0: device timeout +ath0: device timeout +ath0: device timeout +ath0: link state changed to DOWN +ath0: link state changed to UP +ath0: link state changed to DOWN +ath0: link state changed to UP +ath0: link state changed to DOWN +ath0: link state changed to UP +ath0: link state changed to DOWN +ath0: link state changed to UP Thanks!
__________________
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
|
||||
Forgot to mention I have configured WEP only via ifconfig, not via wpa_supplicant, simplifying the whole situation.
__________________
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
|
|||
There is a feature called that turns off the radio.. wireless isn't my forte, but consider using -powersave.
Hope it helps.. |
|
||||
Thanks for the reply BSDfan666 but disabling power saving on the interface made things go worse. I had to disable it in order to get networking working "correctly".
Is there a way to check signal strength in CLI? Thanks!
__________________
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Server-Client | c0mrade | Programming | 3 | 18th March 2009 05:22 PM |
ipsec with client nat | sicute | OpenBSD General | 0 | 30th October 2008 05:39 PM |
IM Client | schrodinger | OpenBSD Packages and Ports | 6 | 16th September 2008 02:09 PM |
DDNS Client | revzalot | OpenBSD Installation and Upgrading | 3 | 12th August 2008 02:21 AM |
Client torrent ! | gnowar | OpenBSD General | 10 | 3rd June 2008 10:50 AM |