openSUSE v11.2 32-bit
desktop: KDE 4.x (.3 I think)
Background info: Installed openSUSE 11.2 on an old HP laptop this morning. I’ve been trying to set up my wireless connection since. After 2-ish hours of searchingupport forums, I managed to use network manager to connect to my home wireless network via WEP, I will say now that I’ve had lots of trouble.
I’ve finally been able to connect to my network, to a point. The NetworkManager in openSUSE says that the wireless connection is active. I can verify this by saying that on the other conputers in my house (winXP, win7, and Ubuntu v9) I have been able to ping this openSUSE computer and my router recognizes it as part of the network.
Here is where the problem arises:
I cannot access the internet from the openSUSE machine, with a domain name or by trying to type in an ip address, and I cannot ping other computers on my network with it. if you need more information I can give it, please give me a hand.
I have been able to ping other computer on my network, I had to resolve some settings on my router. However, I still cannot so much as ping an external site. Whenever I try to connect to something not on my network I receive the error: “connect: Network is unreachable”
Yes, I’ve been through that. I was able to make it all the way to verifying that my network connection was valid in step VII, and then I could not ping an external site. I believe that sticky said that “If that works, then Firefox or any other application should work. If this step fails, your name server entries are wrong and you should seek help.” However, I wasn’t able to ping any nameservers either. I’ve been through all of the mini-tutorials on the stickies, they haven’t fixed it.
Just to keep things updated, I am encountering the same problem as before with a wired ethernet connection that I tried this morning. I have full home network access, but I have zero external access.
On 06/18/2010 11:26 AM, axel417 wrote:
>
> Just to keep things updated, I am encountering the same problem as
> before with a wired ethernet connection that I tried this morning. I
> have full home network access, but I have zero external access.
That certainly sounds like a nameserver problem.
For completeness, post the output of ‘sudo /sbin/route -n’. That should
be OK if you can access the local network, but there may still be a problem.
On 06/18/2010 12:16 PM, axel417 wrote:
>
> lwfinger;2177892 Wrote:
>> On 06/18/2010 11:26 AM, axel417 wrote:
>>>
>>> Just to keep things updated, I am encountering the same problem as
>>> before with a wired ethernet connection that I tried this morning. I
>>> have full home network access, but I have zero external access.
>>
>> That certainly sounds like a nameserver problem.
>>
>> For completeness, post the output of ‘sudo /sbin/route -n’. That should
>> be OK if you can access the local network, but there may still be a
>> problem.
>>
>> Next post the output of ‘cat /etc/resolv.conf’.
> output from /sbin/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 2 0 0
> wlan0
>
>
> output from 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.
> #
Your routing table and your resolv.conf are both wrong. This looks like
an 11.2 system that has not been updated to fix the bugs in the
distribution, or the connection is left over from the code that had the
routing bug.
To fix routing, you need to issue the following command:
sudo /sbin/route add default gw 192.168.1.1
In the above, I guessed that your router is at 192.168.1.1. If not, use
its IP address.
To fix name serving, use the following:
kdesu kwrite /etc/resolv.conf
and add a line that says
nameserver 8.8.8.8
at the bottom of the file.
These two should get you Internet access. At that point do
sudo /sbin/zypper up
to get the latest stuff. After a reboot, delete the wireless connection
in the NetworkManager applet and remake it. You should be OK after that.