Using wireless USB connection

I can not manage to have working the wireless USB connection. I am
setting everything and seems to go OK but I do not get a connection.
This is what I get using iwconfig:

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"pat"
Mode:Managed Frequency:2.412 GHz Access Point:
00:14:BF:B9:18:73
Bit Rate=48 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:...[removed]...[2]
Link Quality=72/100 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I don't have any issues using the same connection on Windows, it's only
on Linux I have the problem (SUSE 11.0). Could someone help please?

Thanks,

George

George wrote:
[color=blue]
> I can not manage to have working the wireless USB connection. I am
> setting everything and seems to go OK but I do not get a connection.
> This is what I get using iwconfig:
>
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> wmaster0 no wireless extensions.
>
> wlan0 IEEE 802.11g ESSID:"pat"
> Mode:Managed Frequency:2.412 GHz Access Point:
> 00:14:BF:B9:18:73
> Bit Rate=48 Mb/s Tx-Power=27 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:...[removed]...[2]
> Link Quality=72/100 Signal level=-44 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> I don't have any issues using the same connection on Windows, it's only
> on Linux I have the problem (SUSE 11.0). Could someone help please?
>
> Thanks,
>
> George[/color]

At this point you have your wlan0 interface configured correctly. You still
need to get an IP address via DHCP from your wifi router. Under root try
something like :

ifup wlan0

Then check it with ifconfig.

blackcat escribió:[color=blue]
> George wrote:
>[color=green]
>> I can not manage to have working the wireless USB connection. I am
>> setting everything and seems to go OK but I do not get a connection.
>> This is what I get using iwconfig:
>>
>> lo no wireless extensions.
>>
>> eth0 no wireless extensions.
>>
>> wmaster0 no wireless extensions.
>>
>> wlan0 IEEE 802.11g ESSID:"pat"
>> Mode:Managed Frequency:2.412 GHz Access Point:
>> 00:14:BF:B9:18:73
>> Bit Rate=48 Mb/s Tx-Power=27 dBm
>> Retry min limit:7 RTS thr:off Fragment thr=2352 B
>> Encryption key:...[removed]...[2]
>> Link Quality=72/100 Signal level=-44 dBm
>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>
>> I don't have any issues using the same connection on Windows, it's only
>> on Linux I have the problem (SUSE 11.0). Could someone help please?
>>
>> Thanks,
>>
>> George[/color]
>
> At this point you have your wlan0 interface configured correctly. You still
> need to get an IP address via DHCP from your wifi router. Under root try
> something like :
>
> ifup wlan0
>
> Then check it with ifconfig.
>[/color]

I tried that, but it does not seem to get an IP address. This is what I
get with ifstatus:

# ifstatus wlan0
wlan0
wlan0 dhcpcd is still waiting for data
wlan0 is up

I also tried ifrenew wlan0, but there is no change.

George wrote:
[color=blue]
> blackcat escribió:[color=green]
>> George wrote:
>>[color=darkred]
>>> I can not manage to have working the wireless USB connection. I am
>>> setting everything and seems to go OK but I do not get a connection.
>>> This is what I get using iwconfig:
>>>
>>> lo no wireless extensions.
>>>
>>> eth0 no wireless extensions.
>>>
>>> wmaster0 no wireless extensions.
>>>
>>> wlan0 IEEE 802.11g ESSID:"pat"
>>> Mode:Managed Frequency:2.412 GHz Access Point:
>>> 00:14:BF:B9:18:73
>>> Bit Rate=48 Mb/s Tx-Power=27 dBm
>>> Retry min limit:7 RTS thr:off Fragment thr=2352 B
>>> Encryption key:...[removed]...[2]
>>> Link Quality=72/100 Signal level=-44 dBm
>>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>>
>>> I don't have any issues using the same connection on Windows, it's only
>>> on Linux I have the problem (SUSE 11.0). Could someone help please?
>>>
>>> Thanks,
>>>
>>> George[/color]
>>
>> At this point you have your wlan0 interface configured correctly. You
>> still need to get an IP address via DHCP from your wifi router. Under
>> root try something like :
>>
>> ifup wlan0
>>
>> Then check it with ifconfig.
>>[/color]
>
> I tried that, but it does not seem to get an IP address. This is what I
> get with ifstatus:
>
> # ifstatus wlan0
> wlan0
> wlan0 dhcpcd is still waiting for data
> wlan0 is up
>
> I also tried ifrenew wlan0, but there is no change.[/color]

Ok then it probably means that the configuration you show up there is wrong.
How did you get this Access Point of 00:14:BF:B9:18:73 ? Is it the one
associated with your wifi usb adapter ? You should replace this by the real
access point by doing something like :

iwconfig wlan0 ap any

You can also set the rate at 54Mb/s with :

iwconfig wlan0 rate 54M

Then do a new iwconfig (or a iwlist wlan0 scanning essid pat) to check your
access point. If you get the right one this time the ifup should get an IP
address. Come back to tell us the result of this test.

blackcat escribió:
[color=blue]
>
> Ok then it probably means that the configuration you show up there is wrong.
> How did you get this Access Point of 00:14:BF:B9:18:73 ? Is it the one
> associated with your wifi usb adapter ? You should replace this by the real
> access point by doing something like :
>
> iwconfig wlan0 ap any
>
> You can also set the rate at 54Mb/s with :
>
> iwconfig wlan0 rate 54M
>
> Then do a new iwconfig (or a iwlist wlan0 scanning essid pat) to check your
> access point. If you get the right one this time the ifup should get an IP
> address. Come back to tell us the result of this test.
>[/color]

I have gone further now, I have an IP but yet I am not able to connect
to the internet with it. This is what I get now:

# ifstatus wlan0
wlan0
wlan0 DHCP client (dhcpcd) is running
IPADDR='192.168.1.102'
NETMASK='255.255.255.0'
GATEWAYS='192.168.1.1'
DNSSERVERS='194.168.4.100 194.168.8.100'
REBINDTIME='75600'
DHCPCHADDR='00:12:17:81:ab:b5'
wlan0 is up
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
qlen 1000
link/ether 00:12:17:81:ab:b5 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.102/24 brd 192.168.1.255 scope global wlan0
inet6 fe80::212:17ff:fe81:abb5/64 scope link
valid_lft forever preferred_lft forever
wlan0 IP address: 192.168.1.102/24
Configured routes for interface wlan0:
169.254.0.0 - 255.255.0.0 wlan0
Active routes for interface wlan0:
192.168.1.0/24 proto kernel scope link src 192.168.1.102
169.254.0.0/16 scope link
1 of 1 configured routes for interface wlan0 up
bssid=00:14:bf:b9:18:73
ssid=pat
id=0
pairwise_cipher=TKIP
group_cipher=TKIP
key_mgmt=WPA-PSK
wpa_state=COMPLETED
ip_address=192.168.1.102

George wrote:[color=blue]
>
> I have gone further now, I have an IP but yet I am not able to connect
> to the internet with it. This is what I get now:
>
> # ifstatus wlan0
> wlan0
> wlan0 DHCP client (dhcpcd) is running
> IPADDR='192.168.1.102'
> NETMASK='255.255.255.0'
> GATEWAYS='192.168.1.1'
> DNSSERVERS='194.168.4.100 194.168.8.100'
> REBINDTIME='75600'
> DHCPCHADDR='00:12:17:81:ab:b5'
> wlan0 is up
> 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> qlen 1000
> link/ether 00:12:17:81:ab:b5 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.102/24 brd 192.168.1.255 scope global wlan0
> inet6 fe80::212:17ff:fe81:abb5/64 scope link
> valid_lft forever preferred_lft forever
> wlan0 IP address: 192.168.1.102/24
> Configured routes for interface wlan0:
> 169.254.0.0 - 255.255.0.0 wlan0
> Active routes for interface wlan0:
> 192.168.1.0/24 proto kernel scope link src 192.168.1.102
> 169.254.0.0/16 scope link
> 1 of 1 configured routes for interface wlan0 up
> bssid=00:14:bf:b9:18:73
> ssid=pat
> id=0
> pairwise_cipher=TKIP
> group_cipher=TKIP
> key_mgmt=WPA-PSK
> wpa_state=COMPLETED
> ip_address=192.168.1.102[/color]

Good. We are going further. Now it may be just a problem of default route or
DNS config. Do you have these 2 DNS servers in /etc/resolv.conf ? What you
can do is edit /etc/resolv.conf and put something like :

domain yourdomain.net
nameserver 194.168.4.100
nameserver 194.168.8.100

Then you need to edit /etc/sysconfig/network/dhcp and set
DHCLIENT_MODIFY_RESOLV_CONF="no"
It will keep resolv.conf unmodified. Also check on your ISP website if these
2 servers are the right one advised to use.

Can you ping any of these 2 DNS servers ? Give us your routing table with :

route -n

The line with 0.0.0.0 should point to 192.168.1.1

blackcat escribió:[color=blue]
> George wrote:[color=green]
>> I have gone further now, I have an IP but yet I am not able to connect
>> to the internet with it. This is what I get now:
>>
>> # ifstatus wlan0
>> wlan0
>> wlan0 DHCP client (dhcpcd) is running
>> IPADDR='192.168.1.102'
>> NETMASK='255.255.255.0'
>> GATEWAYS='192.168.1.1'
>> DNSSERVERS='194.168.4.100 194.168.8.100'
>> REBINDTIME='75600'
>> DHCPCHADDR='00:12:17:81:ab:b5'
>> wlan0 is up
>> 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>> qlen 1000
>> link/ether 00:12:17:81:ab:b5 brd ff:ff:ff:ff:ff:ff
>> inet 192.168.1.102/24 brd 192.168.1.255 scope global wlan0
>> inet6 fe80::212:17ff:fe81:abb5/64 scope link
>> valid_lft forever preferred_lft forever
>> wlan0 IP address: 192.168.1.102/24
>> Configured routes for interface wlan0:
>> 169.254.0.0 - 255.255.0.0 wlan0
>> Active routes for interface wlan0:
>> 192.168.1.0/24 proto kernel scope link src 192.168.1.102
>> 169.254.0.0/16 scope link
>> 1 of 1 configured routes for interface wlan0 up
>> bssid=00:14:bf:b9:18:73
>> ssid=pat
>> id=0
>> pairwise_cipher=TKIP
>> group_cipher=TKIP
>> key_mgmt=WPA-PSK
>> wpa_state=COMPLETED
>> ip_address=192.168.1.102[/color]
>
> Good. We are going further. Now it may be just a problem of default route or
> DNS config. Do you have these 2 DNS servers in /etc/resolv.conf ? What you
> can do is edit /etc/resolv.conf and put something like :
>
> domain yourdomain.net
> nameserver 194.168.4.100
> nameserver 194.168.8.100
>
> Then you need to edit /etc/sysconfig/network/dhcp and set
> DHCLIENT_MODIFY_RESOLV_CONF="no"
> It will keep resolv.conf unmodified. Also check on your ISP website if these
> 2 servers are the right one advised to use.
>
> Can you ping any of these 2 DNS servers ? Give us your routing table with :
>
> route -n
>
> The line with 0.0.0.0 should point to 192.168.1.1
>
>[/color]
First, many thanks for your help!

I do have the right entries in resolv.conf. These DNS servers are the
right ones. If I set that entry in dhcp to "no", it still does not work
and then my wired connection does not work either, so I put it back to
"yes" (otherwise I would not be able to send this!).

Here is what you asked:
# 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 eth0
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 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

and I can ping the DNS servers.

George <george@somewhere.earth> writes:
[color=blue]
>blackcat escribió:[color=green]
>> George wrote:[color=darkred]
>>> I have gone further now, I have an IP but yet I am not able to connect
>>> to the internet with it. This is what I get now:
>>>
>>> # ifstatus wlan0
>>> wlan0
>>> wlan0 DHCP client (dhcpcd) is running
>>> IPADDR='192.168.1.102'
>>> NETMASK='255.255.255.0'
>>> GATEWAYS='192.168.1.1'
>>> DNSSERVERS='194.168.4.100 194.168.8.100'
>>> REBINDTIME='75600'
>>> DHCPCHADDR='00:12:17:81:ab:b5'
>>> wlan0 is up
>>> 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>> qlen 1000
>>> link/ether 00:12:17:81:ab:b5 brd ff:ff:ff:ff:ff:ff
>>> inet 192.168.1.102/24 brd 192.168.1.255 scope global wlan0
>>> inet6 fe80::212:17ff:fe81:abb5/64 scope link
>>> valid_lft forever preferred_lft forever
>>> wlan0 IP address: 192.168.1.102/24
>>> Configured routes for interface wlan0:
>>> 169.254.0.0 - 255.255.0.0 wlan0
>>> Active routes for interface wlan0:
>>> 192.168.1.0/24 proto kernel scope link src 192.168.1.102
>>> 169.254.0.0/16 scope link
>>> 1 of 1 configured routes for interface wlan0 up
>>> bssid=00:14:bf:b9:18:73
>>> ssid=pat
>>> id=0
>>> pairwise_cipher=TKIP
>>> group_cipher=TKIP
>>> key_mgmt=WPA-PSK
>>> wpa_state=COMPLETED
>>> ip_address=192.168.1.102[/color]
>>
>> Good. We are going further. Now it may be just a problem of default route or
>> DNS config. Do you have these 2 DNS servers in /etc/resolv.conf ? What you
>> can do is edit /etc/resolv.conf and put something like :
>>
>> domain yourdomain.net
>> nameserver 194.168.4.100
>> nameserver 194.168.8.100
>>
>> Then you need to edit /etc/sysconfig/network/dhcp and set
>> DHCLIENT_MODIFY_RESOLV_CONF="no"
>> It will keep resolv.conf unmodified. Also check on your ISP website if these
>> 2 servers are the right one advised to use.
>>
>> Can you ping any of these 2 DNS servers ? Give us your routing table with :
>>
>> route -n
>>
>> The line with 0.0.0.0 should point to 192.168.1.1
>>
>>[/color]
>First, many thanks for your help![/color]
[color=blue]
>I do have the right entries in resolv.conf. These DNS servers are the
>right ones. If I set that entry in dhcp to "no", it still does not work
>and then my wired connection does not work either, so I put it back to
>"yes" (otherwise I would not be able to send this!).[/color]
[color=blue]
>Here is what you asked:
> # 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 eth0
>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 eth0
>127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
>0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0[/color]

This just wrong. You tell the system to send any packet with address
192.168.1.x to both eth0 and wlan0 It will not do so, but instead will send
it to the last one set up.
I do not know what you want and what machines you want to be contacted, but
this will not do it.


[color=blue]
>and I can ping the DNS servers.[/color]

George wrote:
[color=blue]
> First, many thanks for your help!
>
> I do have the right entries in resolv.conf. These DNS servers are the
> right ones. If I set that entry in dhcp to "no", it still does not work
> and then my wired connection does not work either, so I put it back to
> "yes" (otherwise I would not be able to send this!).
>
> Here is what you asked:
> # 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
> eth0
> 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
> eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
> eth0
>
> and I can ping the DNS servers.[/color]

No problem George. You will eventually succeed :-)

May I ask exatly what does not work ? At the moment the routing table shows
that your system is using mainly eth0 for the connection. If you want it to
go through the wifi you may have to drop this ethernet route. One way to do
this could simply be to run "ifdown eth0" before configuring the wifi with
ifup. You can also avoid setting up eth0 during the boot process by setting
STARTMODE=manual in /etc/sysconfig/network/ifcfg-eth0. Then reboot and
configure the wifi as before. No eth0 should now appear in your routing
table and the traffic should go through wlan0 instead. Personally I also
stop NetworkManager by changing NETWORKMANAGER=yes into no
in /etc/sysconfig/network/config. All this may look a bit complicated, but
deactivating eth0 to have the wifi working fine seems sometimes necessary.

I am sure that other guys will give you better explanations.

All these are manual modifications done by editing different files. Usually
most people can install their wifi adaptor just using YAST. But I guess you
have already tried this :-)

blackcat escribió:[color=blue]
> George wrote:
>[color=green]
>> First, many thanks for your help!
>>
>> I do have the right entries in resolv.conf. These DNS servers are the
>> right ones. If I set that entry in dhcp to "no", it still does not work
>> and then my wired connection does not work either, so I put it back to
>> "yes" (otherwise I would not be able to send this!).
>>
>> Here is what you asked:
>> # 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
>> eth0
>> 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
>> eth0
>> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
>> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
>> eth0
>>
>> and I can ping the DNS servers.[/color]
>
> No problem George. You will eventually succeed :-)
>
> May I ask exatly what does not work ? At the moment the routing table shows
> that your system is using mainly eth0 for the connection. If you want it to
> go through the wifi you may have to drop this ethernet route. One way to do
> this could simply be to run "ifdown eth0" before configuring the wifi with
> ifup. You can also avoid setting up eth0 during the boot process by setting
> STARTMODE=manual in /etc/sysconfig/network/ifcfg-eth0. Then reboot and
> configure the wifi as before. No eth0 should now appear in your routing
> table and the traffic should go through wlan0 instead. Personally I also
> stop NetworkManager by changing NETWORKMANAGER=yes into no
> in /etc/sysconfig/network/config. All this may look a bit complicated, but
> deactivating eth0 to have the wifi working fine seems sometimes necessary.
>
> I am sure that other guys will give you better explanations.
>
> All these are manual modifications done by editing different files. Usually
> most people can install their wifi adaptor just using YAST. But I guess you
> have already tried this :-)
>
>
>[/color]
Yes, the installation using YAST does not seem to work for me,
unfortunately. At one point, I managed to get WLAN0 started with ETH0
down and getting through the wireless connection (i.e., route -n was
showing all traffic going into wireless, no entry for eth0). But as soon
as I disconnected the wired connection I lost the Internet. I had enough
of this for today, but I think I made progress and learned in the
process. I will have another go during the week. Many thanks blackcat
for your help, it is appreciated.

George escribió:[color=blue]
> blackcat escribió:[color=green]
>> George wrote:
>>[color=darkred]
>>> First, many thanks for your help!
>>>
>>> I do have the right entries in resolv.conf. These DNS servers are the
>>> right ones. If I set that entry in dhcp to "no", it still does not work
>>> and then my wired connection does not work either, so I put it back to
>>> "yes" (otherwise I would not be able to send this!).
>>>
>>> Here is what you asked:
>>> # 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
>>> eth0
>>> 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
>>> eth0
>>> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
>>> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
>>> eth0
>>>
>>> and I can ping the DNS servers.[/color]
>> No problem George. You will eventually succeed :-)
>>
>> May I ask exatly what does not work ? At the moment the routing table shows
>> that your system is using mainly eth0 for the connection. If you want it to
>> go through the wifi you may have to drop this ethernet route. One way to do
>> this could simply be to run "ifdown eth0" before configuring the wifi with
>> ifup. You can also avoid setting up eth0 during the boot process by setting
>> STARTMODE=manual in /etc/sysconfig/network/ifcfg-eth0. Then reboot and
>> configure the wifi as before. No eth0 should now appear in your routing
>> table and the traffic should go through wlan0 instead. Personally I also
>> stop NetworkManager by changing NETWORKMANAGER=yes into no
>> in /etc/sysconfig/network/config. All this may look a bit complicated, but
>> deactivating eth0 to have the wifi working fine seems sometimes necessary.
>>
>> I am sure that other guys will give you better explanations.
>>
>> All these are manual modifications done by editing different files. Usually
>> most people can install their wifi adaptor just using YAST. But I guess you
>> have already tried this :-)
>>
>>
>>[/color]
> Yes, the installation using YAST does not seem to work for me,
> unfortunately. At one point, I managed to get WLAN0 started with ETH0
> down and getting through the wireless connection (i.e., route -n was
> showing all traffic going into wireless, no entry for eth0). But as soon
> as I disconnected the wired connection I lost the Internet. I had enough
> of this for today, but I think I made progress and learned in the
> process. I will have another go during the week. Many thanks blackcat
> for your help, it is appreciated.[/color]

I had another go at this, with no success. I have been experimenting a
bit, and I do not understand how it works. I have NetworkManager not
active, but if I do iwconfig several times, I can see that the data for
wlan0 changes (i.e., bit rate, key). Who is changing it? from where? I
set the right key using iwconfig, but sometimes simply does not seem to
pay attention to what I do, other times I can see that the key was taken
(it is displayed when issuing iwconfig) but later on it reverts again to
no key. It should work simply from Yast, I would expect. But if I use
Yast to put the right settings, I do not get any error message but if I
do iwconfig afterwards the changes don't seem to have been taken.

George wrote:[color=blue]
>
> I had another go at this, with no success. I have been experimenting a
> bit, and I do not understand how it works. I have NetworkManager not
> active, but if I do iwconfig several times, I can see that the data for
> wlan0 changes (i.e., bit rate, key). Who is changing it? from where? I
> set the right key using iwconfig, but sometimes simply does not seem to
> pay attention to what I do, other times I can see that the key was taken
> (it is displayed when issuing iwconfig) but later on it reverts again to
> no key. It should work simply from Yast, I would expect. But if I use
> Yast to put the right settings, I do not get any error message but if I
> do iwconfig afterwards the changes don't seem to have been taken.[/color]

Hi George.

Still unlucky ? I can try to help again but I am sure I am not the best one.
I don't use wifi myself but I believe that if you don't do the things in
the right order it can drive you quickly mad. One way of always configuring
your adaptor the same way is to write a small script that you run after
booting (without the ethernet interface on). Call it something like mywifi
and make it executable. Here is what you could do, but a man iwconfig will
show other parameters that can be set:

#!/bin/sh

# set up the ssid of pat
iwconfig wlan0 essid pat

# configuring the access point MAC address
iwconfig wlan0 ap any

# install the wep key and bit rate
iwconfig wlan0 key 2320-CDE4-B7
iwconfig wlan0 rate 54M

# checking the config
iwconfig wlan0

ifup wlan0

# checking again
iwlist wlan0 scanning essid pat

exit 0

Then just run it and check the routing table again. Btw you did not say
anything about the adaptor and the driver that you use.

Bertrand