Wifi Connected but Not Accessing Web

[rjwilcox]

Cheers,
I am running OpenSuse 11.1 on my Laptop. The wifi works on my home router but when I go to Chruch the PC reports that I am connected but I cannot access the web. The WEP password is a 10 character phase. When the connection screen opens I am given the choice of WPA & WPA2 Personal (which I cannot change), I enter the password, the display bars indicates that I am connected but I cannot access the web.
Does anyone have any thoughts on what I can do?

Thanks Bob

[lwfinger]

rjwilcox wrote:
> Cheers,
> I am running OpenSuse 11.1 on my Laptop. The wifi works on my home
> router but when I go to Chruch the PC reports that I am connected but I
> cannot access the web. The WEP password is a 10 character phase. When
> the connection screen opens I am given the choice of WPA & WPA2 Personal
> (which I cannot change), I enter the password, the display bars
> indicates that I am connected but I cannot access the web.
> Does anyone have any thoughts on what I can do?

There are two different schemes for converting from a WEP phrase to the hex key.
Your churche's AP uses one and Linux uses a different one. You need to obtain
the hexadecimal key and enter it.

Larry

[deano_ferrari]

Post output of

ifconfig
route -n
cat /etc/resolv.conf

[rjwilcox]

I want to thank everyone for their responding. The first suggestion to use a hexadecimal key: I went to Convert String To Hexadecimal Online to convert the church password to hexadecimal but this key did not work.

Output for
ifconfig
route -n
cat /etc/resolv.conf

ifconfig
Program 'ifconfig' is present in package 'net-tools', which is installed on your system.
Absolute path to 'ifconfig' is '/sbin/ifconfig', so it might be intended to be run only by user with superuser privileges (eg. root).


route -n
Absolute path to 'route' is '/sbin/route', so it might be intended to be run only by user with superuser privileges (eg. root).

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

[lwfinger]

rjwilcox wrote:
> I want to thank everyone for their responding. The first suggestion to
> use a hexadecimal key: I went to 'Convert String To Hexadecimal Online'
> (http://www.string-functions.com/string-hex.aspx) to convert the church
> password to hexadecimal but this key did not work.

You need to have the person that controls the church's AP read out the hex key
from the configuration page of the AP. An arbitrary conversion from string to
hex won't do any good, particularly one that just converts the characters to
their numeric equivalent (a = 61, b=62, etc.).

Until you get the encryption right, the rest of the stuff you posted is
irrelevant. You might try http://www.powerdog.com/wepkey.cgi to see if the
phrase generates the right key.

Larry