very basic quick wireless question

[denoobifyme]

running fully updated 2009 with latest kde on acer aspire one. Today I noticed an unlocked linksys signal, but couldn't connect on ath0. The linksys, though unlocked, says it's managed. when I try to configure my wifi, the default choice is managed. I tried both that and Auto. Without posting all the konsole data in Coffeetime's helpful Basic Networking Tips sticky, I just want to ask:

Is the reason I can't connect because the linksys signal is managed? I haven't connected wirelessly in awhile, but I seem to remember the word Open next to the ones I connected to. Am I remembering right?

[coolbreeze]

Could be that the signal is not strong enough for you to connect even though it's recognized, hope that makes sense.

[muungwana]

how strong is the signal? i was freeloading wireless network couple of months ago and i notice i couldnt connect and the connection dropped when signal strength went under 70%

[smcs_steve]

Return path signal strength is usually the killer - 70% down but up is probably much much less!
>Steve

[denoobifyme]

Usually, I can connect on 18% strength. I've never seen signal strength higher than 63%. This uunlocked one was around 28-32%, highest-level red bars and lowest-level green bars.

[AndrzejL]

Is this Your router that You try to access? Is there MAC address filtering turned on on the router?

Andy

[denoobifyme]

I don't have a router. My Acer netbook has an internal wifi Atheros. When I click on the network icon in systray and then Manage Wireless Connections, a list of available signals from other people pops up. All are locked except for one named Linksys, which is unlocked. Usually, I can access those unlocked ones. This one, it tries for thirty seconds and says Failed To Connect. Maybe the Linksys signal is just a wireless router for a home network rather than an internet connection.

[Rudge]

I have this same problem. The only way I can reconnect is reboot the box. Once it reboots it connects like it was born to do so but trying to reconnect manually, once it drops, seems imposable  

EDIT: Clicking on the widget and then clicking on the desired network with the proper credentials in the wireless connections, restarting the network from command line, and tried restarting KDE4 desktop.   Seems I have to reboot to get the connection back.   

[denoobifyme]

Requiring reboot for restored functionality is usually a tmp, cache or buffer problem. Before I posted, I tried connecting as root (I was doing some system stuff offline) just to see if I could and then relooged as user, but I didn't try rebooting. I should've.

[coolbreeze]

I have this same problem. The only way I can reconnect is reboot the box. Once it reboots it connects like it was born to do so but trying to reconnect manually, once it drops, seems imposable   

Get the same problem myself, just wondering, could it be a software problem? i'm using an Edimax Turbo wireless.