[opensuse] Strange WiFi problem
Ok, this one has me stumped. I'm trying to figure out why the WiFi on a friend's netbook is not working right. Hardware/software: - Asus EeePC 1005HA-H - Atheros WiFi that is known to work well with the ath9k driver - openSUSE 11.2 and KDE.4.3.1 default install plus standard updates I have the exact same netbook model running openSUSE 11.2 and it works fine on my system. Now, what it's doing... we've enabled WiFi using the KNetworkManager, and entered the WEP key for his WiFi router. It finds his router fine, and requests/receives and IP address. But.. here's the weird part... he can't get past the router on the network. We can browse the local network, and even admin the router from the EeePC, but going past the router onto the internet just fails. We cannot ping etc anything outside the local LAP. If I connect my identical laptop into the same router, it's fine... receives an IP, and I have full access to the local LAN as well as the internet. If we connect his netbook to a CAT5 cable then everything works as expected. So.... WiFi is working on the netbook, we can access the LAN, but beyond that doesn't seem to exist. This is on a brand new default install of openSUSE. No extra apps added to the install. We've also reinstalled a couple of times just to see if something went odd in the install. Anyone have any ideas what is going on here? I don't know what to look for in the logs.... C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2010-01-16 at 13:42 +0100, Clayton wrote: ...
Anyone have any ideas what is going on here? I don't know what to look for in the logs....
Guess 1: DNS. --> check using IP, not name. Guess 2: routing. --> print routing table. Try traceroute. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktRvf4ACgkQtTMYHG2NR9XQAQCeNYRIM9KQk/8Y7DPIOMsEln3j YaYAn0x8MbKQkYK0etzKlNrVDW9dMhcJ =mGMc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Guess 1: DNS. --> check using IP, not name.
Checked that just a few mins ago... same results. Plus when we plug in the CAT5 cable, and net traffic is routed that way, everything works OK... so the DNS at the ISP is working as expected.
Guess 2: routing. --> print routing table. Try traceroute.
Hmmm haven't checked that yet. I'll poke around in that part and see what comes up. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 16 Jan 2010 14:56:36 +0100 Clayton <smaug42@gmail.com> wrote:
Guess 1: DNS. --> check using IP, not name.
Checked that just a few mins ago... same results. Plus when we plug in the CAT5 cable, and net traffic is routed that way, everything works OK... so the DNS at the ISP is working as expected.
Guess 2: routing. --> print routing table. Try traceroute.
Hmmm haven't checked that yet. I'll poke around in that part and see what comes up.
C. Hi Are you getting DNS entries in /etc/resolv.conf. If not delete the file and restart the network service.
-- Cheers Malcolm °¿° (Linux Counter #276890) SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.42-0.1-default up 1 day 0:29, 2 users, load average: 0.00, 0.05, 0.07 GPU GeForce 8600 GTS Silent - CUDA Driver Version: 190.18 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Jan 16, 2010 at 15:06, Malcolm <malcolm_lewis@bellsouth.net> wrote:
Are you getting DNS entries in /etc/resolv.conf. If not delete the file and restart the network service.
No, there is no line for nameserver in the resolv.conf. I've tried a few things - deleted the resolv.conf and did a network restart. No difference. Also tried a netconfig update -f with no change. So... narrowed it down to where the problem is. Question is... why is this a problem? and what can we do to fix it? (There's nothing on this netbook, so we can do any level or tinkering or even full reinstalls if necessary) C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 01/16/2010 04:50 PM, Clayton pecked at the keyboard and wrote:
On Sat, Jan 16, 2010 at 15:06, Malcolm <malcolm_lewis@bellsouth.net> wrote:
Are you getting DNS entries in /etc/resolv.conf. If not delete the file and restart the network service.
No, there is no line for nameserver in the resolv.conf.
Seems simple enough, add a couple and try again. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ken Schneider - openSUSE said the following on 01/16/2010 05:01 PM:
On 01/16/2010 04:50 PM, Clayton pecked at the keyboard and wrote:
On Sat, Jan 16, 2010 at 15:06, Malcolm <malcolm_lewis@bellsouth.net> wrote:
Are you getting DNS entries in /etc/resolv.conf. If not delete the file and restart the network service.
No, there is no line for nameserver in the resolv.conf.
Seems simple enough, add a couple and try again.
Unless you know what your service providers/points _should_ be handing out, the simplest is t use nameserver 8.8.8.8 -- How inappropriate to call this planet `Earth' when it is quite clearly `Ocean'. -- Arthur C Clarke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2010-01-16 at 22:50 +0100, Clayton wrote:
On Sat, Jan 16, 2010 at 15:06, Malcolm <malcolm_lewis@bellsouth.net> wrote:
Are you getting DNS entries in /etc/resolv.conf. If not delete the file and restart the network service.
No, there is no line for nameserver in the resolv.conf.
Then, it is obvious that you will not be able to connect to anywhere until you have them. Change your network configuration in yast or wherevever you are doing it. Make sure you select to get automatic dns from the network, if your router is configured to do so, or otherwise, write a DNS that works for you; usually your ISP provides them. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktTB44ACgkQtTMYHG2NR9VskgCgkQG1vtU1CJwsi5cZ7HAuLYOH zSAAnRSYnaUXmg17L9gBJEp9cl4/utTE =LcD4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Jan 17, 2010 at 13:50, Carlos E. R. <robin.listas@telefonica.net> wrote:
No, there is no line for nameserver in the resolv.conf.
Then, it is obvious that you will not be able to connect to anywhere until you have them.
Yup, agreed.
Change your network configuration in yast or wherevever you are doing it. Make sure you select to get automatic dns from the network, if your router is configured to do so, or otherwise, write a DNS that works for you; usually your ISP provides them.
In this case it probably should be nameserver 192.168.1.1 for the router (since all other machines in the house use that, and they all work fine). The really odd thing is...all the other openSUSE installs in the house are fine. My own laptop with 11.2 works as well (with the right namesever entry)... but this one machine with a default install is missing the resolv.conf settings and/or network config settings for automatic DNS? Plus it's only on WiFi that this happens... wired works fine and the nameserver entries are added correctly. How is that possible? How can one install go wrong on something simple like this with a 100% default install when other installs we did are fine? That doesn't make sense to me. I can't see anything in the install clicks that were done that would turn off autoDNS.... and if it works on one default install on a netbook, I would expect it to work exactly the same on a second install on an identical netbook. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 17 Jan 2010 13:59:29 Clayton wrote:
On Sun, Jan 17, 2010 at 13:50, Carlos E. R. <robin.listas@telefonica.net> wrote:
No, there is no line for nameserver in the resolv.conf.
Then, it is obvious that you will not be able to connect to anywhere until you have them.
Yup, agreed.
Change your network configuration in yast or wherevever you are doing it. Make sure you select to get automatic dns from the network, if your router is configured to do so, or otherwise, write a DNS that works for you; usually your ISP provides them.
In this case it probably should be nameserver 192.168.1.1 for the router (since all other machines in the house use that, and they all work fine).
The really odd thing is...all the other openSUSE installs in the house are fine. My own laptop with 11.2 works as well (with the right namesever entry)... but this one machine with a default install is missing the resolv.conf settings and/or network config settings for automatic DNS? Plus it's only on WiFi that this happens... wired works fine and the nameserver entries are added correctly.
How is that possible? How can one install go wrong on something simple like this with a 100% default install when other installs we did are fine? That doesn't make sense to me. I can't see anything in the install clicks that were done that would turn off autoDNS.... and if it works on one default install on a netbook, I would expect it to work exactly the same on a second install on an identical netbook.
Is it https://bugzilla.novell.com/show_bug.cgi?id=553908 ? This should be fixed already by online update. Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 01/17/2010 06:59 AM, Clayton wrote:
On Sun, Jan 17, 2010 at 13:50, Carlos E. R. <robin.listas@telefonica.net> wrote:
No, there is no line for nameserver in the resolv.conf.
Then, it is obvious that you will not be able to connect to anywhere until you have them.
Yup, agreed.
Change your network configuration in yast or wherevever you are doing it. Make sure you select to get automatic dns from the network, if your router is configured to do so, or otherwise, write a DNS that works for you; usually your ISP provides them.
In this case it probably should be nameserver 192.168.1.1 for the router (since all other machines in the house use that, and they all work fine).
The really odd thing is...all the other openSUSE installs in the house are fine. My own laptop with 11.2 works as well (with the right namesever entry)... but this one machine with a default install is missing the resolv.conf settings and/or network config settings for automatic DNS? Plus it's only on WiFi that this happens... wired works fine and the nameserver entries are added correctly.
How is that possible? How can one install go wrong on something simple like this with a 100% default install when other installs we did are fine? That doesn't make sense to me. I can't see anything in the install clicks that were done that would turn off autoDNS.... and if it works on one default install on a netbook, I would expect it to work exactly the same on a second install on an identical netbook.
C.
Clayton, Also check: https://bugzilla.novell.com/show_bug.cgi?id=567137 -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Feb 3, 2010 at 19:20, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Also check:
I forgot to follow up on this one... we got it working. It was the issue linked by Wil, and a full update cleared the problem. WiFi is working as it should. :-) C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 03 February 2010 19:47:26 Clayton wrote:
On Wed, Feb 3, 2010 at 19:20, David C. Rankin
<drankinatty@suddenlinkmail.com> wrote:
Also check:
I forgot to follow up on this one... we got it working. It was the issue linked by Wil, and a full update cleared the problem. WiFi is working as it should. :-)
Glad to hear it :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.00.1001161526440.4868@nimrodel.valinor> On Saturday, 2010-01-16 at 14:56 +0100, Clayton wrote:
Guess 1: DNS. --> check using IP, not name.
Checked that just a few mins ago... same results. Plus when we plug in the CAT5 cable, and net traffic is routed that way, everything works OK... so the DNS at the ISP is working as expected.
Suposedly. It might not answer to wireless connections. The wifi dhcp server might give incorrect dns info. Who knows...
Guess 2: routing. --> print routing table. Try traceroute.
Hmmm haven't checked that yet. I'll poke around in that part and see what comes up.
Ok. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAktRzLIACgkQtTMYHG2NR9X50QCdFn8dC6QypsWv37Rx5mLNa0vn Y+kAn1JolVstG6veZLLcixBLtRQAfIJQ =xLwG -----END PGP SIGNATURE-----
participants (7)
-
Anton Aylward -
Carlos E. R. -
Clayton -
David C. Rankin -
Ken Schneider - openSUSE -
Malcolm -
Will Stephenson