Under OpenSuse 11.2 i cannot connect to my wireless network. Sometimes computer doesn’t see network, sometimes computer cannot connect to it.
Encryption: WPA & WPA2 Personal
Kernel driver: ath5k
Also I am embarrassed that in lspci and yast written various models of my wifi adapter.
kNetworkmanager is a buggy software, i would recommend not to use it. I had/has the same issue with WPA & WPA2 enabled networks, so i don’t use kNetwork manager any more for them. I use ifup and it works like a charm.
Go to YaST -> Network Devices -> Network Settings and change the method to ifup and setup your network after it.
I already read it, but the network really does not work
kNetworkmanager is a buggy software, i would recommend not to use it. I had/has the same issue with WPA & WPA2 enabled networks, so i don’t use kNetwork manager any more for them. I use ifup and it works like a charm.
Go to YaST -> Network Devices -> Network Settings and change the method to ifup and setup your network after it.
On 02/17/2010 11:56 AM, miksayer wrote:
>
> caf4926;2122367 Wrote:
>> ‘HCL/Laptops/Asus - openSUSE’
>> (http://en.opensuse.org/HCL/Laptops/Asus#Asus_Eee_PC_xxxx_X)
>
> I already read it, but the network really does not work
>
>> kNetworkmanager is a buggy software, i would recommend not to use it.
>> I had/has the same issue with WPA & WPA2 enabled networks, so i don’t
>> use kNetwork manager any more for them. I use ifup and it works like a
>> charm.
>> Go to YaST -> Network Devices -> Network Settings and change the method
>> to ifup and setup your network after it.
>>
>> You can also try wicd instead of KNM.
>
> I use gnome network manager
I dispute the claim that kNM is buggy. It was true that 11.2 had a bug, but that
has been corrected. I find wicd to be inconvenient to use.
To help in debugging this problem, please attempt to make a wireless connection
and post the output of the following:
You had the wire connected. All your output shows that uyou had a connection
with eth0. If using NM, disconnect the wire, or if you are using ifup, then the
following:
ifdown eth0
ifup wlan0
and repeat the previous commands.
The info in your previous post showed that wlan0 had authenticated and
associated. Thus the problem is with routing or name serving.
BTW: When you posted the “Encryption key”, you told the world your wifi
encryption secret. NEVER run iwconfig as root and post the output without
deleting that info.
linux-ra0h:/home/miksayer # /usr/sbin/iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:"HNet"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
linux-ra0h:/home/miksayer # /sbin/ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1776 (1.7 Kb) TX bytes:1776 (1.7 Kb)
wlan0 Link encap:Ethernet HWaddr 00:22:43:80:BC:95
inet addr:192.168.1.37 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::222:43ff:fe80:bc95/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:873 (873.0 b) TX bytes:2501 (2.4 Kb)
wmaster0 Link encap:UNSPEC HWaddr 00-22-43-80-BC-95-38-30-00-00-00-00-00-00-00-00
UP RUNNING MTU:0 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
linux-ra0h:/home/miksayer # /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
linux-ra0h:/home/miksayer # cat /etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
nameserver 192.168.1.1
On 02/18/2010 05:36 AM, miksayer wrote:
>
> with ifup:
>
> Code:
> --------------------
> linux-ra0h:/home/miksayer # /usr/sbin/iwconfig
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> wmaster0 no wireless extensions.
>
> wlan0 IEEE 802.11bg ESSID:“HNet”
> Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
> Tx-Power=20 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> linux-ra0h:/home/miksayer # /sbin/ifconfig
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:24 errors:0 dropped:0 overruns:0 frame:0
> TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1776 (1.7 Kb) TX bytes:1776 (1.7 Kb)
>
> wlan0 Link encap:Ethernet HWaddr 00:22:43:80:BC:95
> inet addr:192.168.1.37 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::222:43ff:fe80:bc95/64 Scope:Link
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:873 (873.0 b) TX bytes:2501 (2.4 Kb)
>
> wmaster0 Link encap:UNSPEC HWaddr 00-22-43-80-BC-95-38-30-00-00-00-00-00-00-00-00
> UP RUNNING MTU:0 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> linux-ra0h:/home/miksayer # /sbin/route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> linux-ra0h:/home/miksayer # cat /etc/resolv.conf
> ### /etc/resolv.conf file autogenerated by netconfig!
> #
> # Before you change this file manually, consider to define the
> # static DNS configuration using the following variables in the
> # /etc/sysconfig/network/config file:
> # NETCONFIG_DNS_STATIC_SEARCHLIST
> # NETCONFIG_DNS_STATIC_SERVERS
> # NETCONFIG_DNS_FORWARDER
> # or disable DNS configuration updates via netconfig by setting:
> # NETCONFIG_DNS_POLICY=’’
> #
> # See also the netconfig(8) manual page and other documentation.
> #
> # Note: Manual change of this file disables netconfig too, but
> # may get lost when this file contains comments or empty lines
> # only, the netconfig settings are same with settings in this
> # file and in case of a “netconfig update -f” call.
> #
> ### Please remove (at least) this line when you modify the file!
> nameserver 192.168.1.1
>
Your wireless device has not authenticated/associated, yet you have an IP and an
SSID. That implies you are using a static IP. If so, you failed to set the
routing in the YaST configuration.
Is your network encrypted? If so, you did not get the encryption key set
correctly. For WPA/WPA2, use a passphrase. For WEP, you must use a hex key.
On 02/18/2010 04:06 PM, miksayer wrote:
>
> lwfinger;2123144 Wrote:
>> On 02/18/2010 05:36 AM, miksayer wrote:
>>
>> Is your network encrypted? If so, you did not get the encryption key
>> set
>> correctly. For WPA/WPA2, use a passphrase. For WEP, you must use a hex
>> key.
>
> where should I set this key?
With ifup, use YaST => Network Devices => Network Settings. With NM, under the
“Manage Connections” option in the applet.
No, ESSID of my network is visible. Just then the computer for some reason did not see my network(although at that and this time I was near the router). Now iwlist scan output is