openSUSE 11: How to proceed after this message

The dmsg tells on startup of openSUSE 11:
wlan0
WPA configured but may be unsupported by this device
WEXT auth param 4 value 0x0 -ioctl[SIOCSIWAUTH]
operation not supported

The webbrowser runs but no contact with address.

SLED 10 manages to get contact with the http://'s but not oSuse 11

Thanks SS ,Norway

sigbj wrote:
> The dmsg tells on startup of openSUSE 11:
> wlan0
> WPA configured but may be unsupported by this device
> WEXT auth param 4 value 0x0 -ioctl[SIOCSIWAUTH]
> operation not supported
>
> The webbrowser runs but no contact with address.
>
> SLED 10 manages to get contact with the http://'s but not oSuse 11
>
> Thanks SS ,Norway
>
>
What wireless card is it?

sigbj wrote:
> The dmsg tells on startup of openSUSE 11:
> wlan0
> WPA configured but may be unsupported by this device
> WEXT auth param 4 value 0x0 -ioctl[SIOCSIWAUTH]
> operation not supported
>
> The webbrowser runs but no contact with address.
>
> SLED 10 manages to get contact with the http://'s but not oSuse 11

Those two messages are not killers. How are you setting your IP? Are you using
static IP or DHCP?

When you reach this state, what are the outputs of ‘/usr/sbin/iwconfig wlan0’
and ‘/sbin/ifconfig wlan0’?

Larry

What wireless card is it?[/QUOTE]

Netgear/Atheros Comm.Inc/AR512/AR513 Multiprotocol/MAC/baseband processor (wlan0)

Using static IP
DSL-> wlanROUTER-> PC
IWCONFIG=
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key: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

IFCONFIG=
wlan0 Link encap:Ethernet HWaddr 00:18:4D:6E:0E:8C
inet addr:192.168.0.196 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 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)

Netgear/Atheros Comm.Inc/AR512/AR513 Multiprotocol/MAC/baseband processor (wlan0)

Are you sure or is it a typo? I’ve got an AR5212/5213 based Atheros card here (PCMCIA) which worked out of the box on 11.0 incl. WPA-PSK. (ath0 ! )

sigbj wrote:
> Using static IP
> DSL-> wlanROUTER-> PC
> IWCONFIG=
> wlan0 IEEE 802.11g ESSID:""
> Mode:Managed Frequency:2.412 GHz Access Point:
> Not-Associated
> Tx-Power=27 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key: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

You have not associated with your AP.

When you do the command ‘sudo /usr/sbin/iwlist wlan0 scan’, do you see your AP?

Is your network encrypted? If you are using WEP, are you inputting a passphrase,
or a hex key?

What does the output of dmesg have to say about wlan0?

Larry

You were right. It is a typing fault. You have the right typing: AR5212/AR5213. I am using WPA-PSK that on this machine only works with SLED 10, not SuSE 9.2-11.0; On a ASUS laptop SuSE 10 works fine with WPA-PSK, but on the aforemention there is trouble,getting network. Only SuSE Linux Enterprise Desktop 10, SP1,SP2 works. I use the same configuration as to IP,gateway and wlan-passphrase on this machine that has WinXP,SLED and now openSuSE 11 on a try-out.
(I will be back later with answer to Larry.)

sudo /usr/sbin/iwlist wlan0 scan=
wlan0 No scan results

dmesg=
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
IP address: 127.0.0.2/8
done wlan0 device: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
wlan0 warning: WPA configured but may be unsupported
wlan0 warning: by this device
wlan0 starting wpa_supplicant
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
wlan0 IP address: 192.168.0.196/24

some from /var/log/messages=
Aug 1 12:52:32 linux-9srs ifup: wlan0 device: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
Aug 1 12:52:32 linux-9srs ifup-wireless: wlan0 warning: WPA configured but may be unsupported
Aug 1 12:52:32 linux-9srs ifup-wireless: wlan0 warning: by this device
Aug 1 12:52:32 linux-9srs ifup-wireless: wlan0 starting wpa_supplicant
Aug 1 12:52:33 linux-9srs kernel: NET: Registered protocol family 17
Aug 1 12:52:33 linux-9srs ifup: wlan0
Aug 1 22:07:05 linux-9srs ifup: lo
Aug 1 22:07:05 linux-9srs ifup: lo
Aug 1 22:07:05 linux-9srs ifup: IP address: 127.0.0.1/8
Aug 1 22:07:05 linux-9srs ifup:
Aug 1 22:07:05 linux-9srs ifup:
Aug 1 22:07:05 linux-9srs ifup: IP address: 127.0.0.2/8
Aug 1 22:07:05 linux-9srs ifup:
Aug 1 22:07:06 linux-9srs ifup: wlan0 device: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
Aug 1 22:07:06 linux-9srs ifup-wireless: wlan0 warning: WPA configured but may be unsupported
Aug 1 22:07:06 linux-9srs ifup-wireless: wlan0 warning: by this device
Aug 1 22:07:06 linux-9srs ifup-wireless: wlan0 starting wpa_supplicant
Aug 1 22:07:06 linux-9srs kernel: NET: Registered protocol family 17
Aug 1 22:07:06 linux-9srs ifup: wlan0
Aug 1 22:30:06 linux-9srs ifup: wlan0 device: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
Aug 1 22:30:06 linux-9srs ifup-wireless: wlan0 warning: WPA configured but may be unsupported
Aug 1 22:30:06 linux-9srs ifup-wireless: wlan0 warning: by this device
Aug 1 22:30:06 linux-9srs ifup-wireless: wlan0 starting wpa_supplicant
Aug 1 22:30:09 linux-9srs kernel: NET: Registered protocol family 17
Aug 1 22:30:09 linux-9srs ifup: wlan0
Aug 1 22:30:09 linux-9srs ifup: IP address: 192.168.0.196/24
Aug 2 20:09:22 linux-9srs ifup: wlan0 device: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
Aug 2 20:09:22 linux-9srs ifup-wireless: wlan0 warning: WPA configured but may be unsupported
Aug 2 20:09:22 linux-9srs ifup-wireless: wlan0 warning: by this device
Aug 2 20:09:22 linux-9srs ifup-wireless: wlan0 starting wpa_supplicant
Aug 2 20:09:23 linux-9srs kernel: NET: Registered protocol family 17
Aug 2 20:09:23 linux-9srs ifup: wlan0
Aug 2 20:09:23 linux-9srs ifup: IP address: 192.168.0.196/24
Aug 2 20:12:12 linux-9srs sudo: root : TTY=tty6 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/iwlist wlan0 scan

Additional info as to SuSE 9.2-11.0

None of the above can connect to network/internet anyhow. Only SuSE 8.2 and SLED 10 manage to do this.

As to openSUSE 11 it seems to be extremely nice going through the installation procedure without any stop. Only problem I have is getting LILO installed in other than MBR. GRUB does it, but any try to have LILO into anywhere than MBR will not work. That is the only problem I have had with number 11. After the installation there is a tendency for eleven to freeze the mouse and the keyboard and I have to be extremely cautious and let all processes run completely through before I use those. The problem might be that the machine is too special and too old.(?).

For a few years back an update of SuSE 8.2 killed the BIOS video in some way. Consoles could after this only be reached by vga=normal not the lilo.conf setup with vga=0x391 (I dont remember quite) Also installation failed that there were no console with messages except with vga=normal. On the later versions 9.2 9.3 10.1 10.2 10.3 11.0 they all were running with their specific vga=0xXXX. Even after the grafic card was changed the problem with SuSE 8.2 vga lilo.conf choice remained the same, so it could not be the grafic cards console part that had been destroyed. I doubt this is important for the topic above, but wanted to mention it. In new installations with SuSE 8.2, 8.2 did not manage to identify the old network card again. Mysterious. I now have a new netcard, but SuSE 9.2-11 are not able connect with it.
Well, to much off the topic.
Where is your spankee-bankee avatar,69_rs_ss, I probably deserve it?

sigbj wrote:
> sudo /usr/sbin/iwlist wlan0 scan=
> wlan0 No scan results

Unless you get scan results, you will never make a connection. As you are using
ifup to control this device, you need to make sure that the output of
/sbin/ifconfig shows that the device is UP before trying the scan. In addition,
it is possible for iwlist to return no results at the beginning. Please try
several times to see if you get any results. I hope the AP does not have a
hidden SSID.

Larry

Several tries do not give positiv feedback. Responses are negative.
ESSID is not hidden.
I use a WPA-PSK passphrase of 32 chars and non-dictionary; and the chars work on the other machines, both Win and Lin.

I am exactly at this point, with an exception. My wifi card is:

‘Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)’ (quoted by hand).

My AP is a Linksys WRT54GL v1.1 with ddWRT v23 SP2, that is used in a lot of other machines (both windows and linux, opensuse 11.1 among others).

This same wireless card works fine on other environments (other APs I supose, don’t know about encryption modes).

  • I can ‘see’ other APs but not mine, even I am at 2m…20m of a repeater. Other APs are

  • The log tells ‘WPA configured but may be unsupported’. My AP is WPA2-PSK.

Any help is sincerely appreciated

Rummidge wrote:
>
> * The log tells ‘WPA configured but may be unsupported’. My AP is
> WPA2-PSK.

Please do not hijack a thread. Your wireless card is different than
was used by the OP, thus anyone interested in an Intel card might miss it.

Does “I can see other AP’s” mean that the command

sudo /usr/sbin/iwlist scan

does return scan data, but not for your AP? BTW, the message above
does not cause a problem. WPA2 is supported.

You are missing some vital information. Saying you have openSUSE 11 is
not sufficient. Is it 11.0 or 11.1? They are very different! Are you
using NetworkManager or the traditional ifup method for configuration?