Hi Everyone,
I am using SUSE 10.0, the problem is when I try to connect from wireless, it finds the appropriate networks, even it shows that I connected to that network but unfortunately I can't open any web page I mean I can't access to internet, I am using an Access Point and only page I can access is that address of the router(acts like an access point), when I try to connect from ethernet I can, but I can't use internet by wireless connection, what could be the solution, thanks for help. (And the webpages are displayed in very small fonts what could be the problem about that too) .

Try this thread that was solved about 5 secs ago, Suse should be very similar.
http://www.linuxquestions.org/questi...d.php?t=415087

About the webpage text being very small, is this a settings problem, a resolution problem, a problem in Konqueror or Firefox?

If you can ctrl-+ to increase the font size and everything looks cool, then it is probably a setting to change.

Well I think it's a resolution problem, I mean some pages are fine, but other have problems, ev en I increase the font by ctrl + font increases but it is seen very messy.

Well can someone help, I am new to Linux and I couldn't understand what should I do after reading the post you sent "accessrichard", thanks anyway, but can someone help me with giving more details about what should I do. Iwrite netstat -r to terminal but it just gives me ip routing table, thanks

First of all, there is a button that is added to the bottom left of your post called edit so that you dont have to post 2 times in a row.

What you are looking for in the netstat -r command is the default gateway, mine is that of my router's ip address. This tells your computer that to get out into the internet, go through this address. This address will also allow you to access your ISP's dns servers which we can check with

cat /etc/resolv.conf

In the output of resolv.conf you should see a couple nameservers. You could check to make sure they are dns servers by say doing a whois lookup or something. whois <ipaddress> and they should get outputs indicated that they are dns servers.

If the outputs of these commands do not look good, you could try doing a

route add default gw 192.168.0.1 dev wlan0

or something similar, you have to "man route" or use the suse GUI in order to configure your network settings.
If your dns servers and your gw is correct, then make sure you are turning off you eth0 interface before you start your wlan0 interface as some people on Suse report problems with this, and then maybe powercycle you AP.

On you web problem, is the problem persistent when you open a different browser such as Opera or Konqueror.

For Web Browsers yes all of them have the same problem.
When I use "cat /etc/resolv.conf"
command, the output is This is a temporary resolv.conf created by service dhcpcd... (In the end) search company.com nameserver 192.168.1.1 and when I use whois 192.168.1.1 it just waits, and when I use man route I see the help page but when I try the command route it says command not found, and I am not using a dns server I am connrctin through a dhps server, do youhave any idea or am I hopeless about the wireless connection =(
(by the way is there a way to disable eth0 interface by a command from terminal, I made that wireless network connection connects while booting whereas ethernet manually, so when Suse starts KInternet shows that eth0 is active and KWifiManager shows the connection is made through eth1 I don't understand maybe that's the problem I don't see anything about wlan0 interface )

Open your resolv.conf as root and try commenting out "search company.com"(add an # as the first character of the line) so that your resolve config looks like this:

EDIT: you must be root or have su privs to edit this AND/OR have access for the route command

To disable your eth0 connection via console type

Again, you must be root for these commands, to bring it back up then the command is

Ok, web addresses that start with 192.168.x.x are local IP address's. If the nameserver lines in reslov.conf are 192.168.1.1 then this is a sign that your gateway is not set up correctly as they should read your ISP's dns servers.

If you can get a wireless IP address on eth1, e.g. can ping router without ethernet cable plugged in, then your wireless device is called eth1 and not wlan0. It makes no difference.

If you can man route, I would like to assume that route is installed. do a

whereis route

and then you should see an output like /usr/sbin/route or something like that. Use the path from the whereis route command and run

/path/from/whereis/route add default gw 192.168.1.1 dev eth1

If the route command does not work, then use the Suse network gui and add the default gateway through the GUI, it should be a setting there in either the 'K' or 'Gnome' menu's

Then ifdown eth0, or ifconfig eth0 down whichever one works on suse,
and
run the above commands as sudo or root.

Thanks justanohersteve but it doesn't work, and when I type the command route add default gw 192.168.1.1 dev wlan0 it says SIOCADDRT: No such device.
"accessRichard" I tried route add default gw 192.168.1.1 dev eth0 it says File exists, then I say ifconfig eth0 it close eth0,
then iwconfig eth1 essid any && dhcpd eth1, and it opens a page and in summary it says that No subnet declaration for eth1 (0.0.0.0), write a subnet declaration in your dhcpd.conf file if you want to change this. "Not configured to listen on any interfaces" =(
even though thanks again "accessRichard" I think I am stuck with cable connection again =(

in

route add default gw 192.168.1.1 dev eth0

change eth0 to eth1

eth0 = wired ethernet
eth1 = wireless ethernet

I tried that(route add default gw 192.168.1.1 dev eth1) and it says Network is unreachable, I even say ifconfig eth1 up and try again the result is same, oo thanks Richard I think we tried everything =), well at least ı felt like I learned something about these stuffs =)

Never give up hope.

This just means that we are specifying the wrong subnet, gateway or network or eth1 was not activated.

Try going back to your first post, can ping router but nothing else from eth1 with ethernet cable unplugged. Do whatever you did to be able to ping your router with your ethernet cable unplugged. Then ifconfig eth0 down and

route add default gw 192.168.1.1 netmask 255.255.255.0 dev eth1

This is just to make sure you can ping your router but can not add a route to it.

=(, first it connects then I restart the computer now it doesn't connect from anywhere I try same things but this time when I say ipup eth1 it says ".... no IP address yet ....", and when I try route add default gw 192.168.1.1 dev eth1 it gives error "Network
is unreachable", why could it be so difficult, my friend also using this and she connects wthout doing anything, what should I do?

"accessrichard" sorry for extra reply but what do you think I should do?

When you say it doesnt connect from anywhere do you mean eth0(wired) and eth1(wireless) dont connect or do you mean that just eth1 does not connect.

If you added the route before I do not think you need to do it again, but check again to see if in /etc/resolv.conf that the nameservers are that of your ISP (not 192.168.x.x) addresses, and netstat -r to be sure that your default gw is 192.168.1.1.

What did you do to try to connect.
iwconfig eth1 essid any
ifconfig eth1 up
dhcpcd eth1
ifup eth1

Are you getting an IP address at all?
Can you ping the router wirelessly?
Is everything ok in reslov.conf and netstat -r?

I use Fedora and after I get things working with in the command line, I use the Fedora GUI to configure how to connect via ifup, otherwise ifup doesnt do what I need to do to connect, e.g. WPA, essid, etc.