I’ve been happily using WiFi with my Samsung NC10 netbook, running 11.3. Today, I did zypper dup and a whole lot of stuff was installed, including a kernel update to 2.6.34.8-0.2 default (i686).
Immediately after a reboot, I couldn’t see the internet but i am able to get into the router (with the usual 192.168.0.1) so it would seem that the WiFi link is working but Firefox and Thunderbird can’t see any servers. Very strange. I re-installed the WiFi card (Atheros AR5001) but no change. I think the relevant module is ath5k. Any ideas gratefully received!
On 05/01/2011 09:36 AM, petermcph wrote:
>
> I’ve been happily using WiFi with my Samsung NC10 netbook, running 11.3.
> Today, I did zypper dup and a whole lot of stuff was installed,
> including a kernel update to 2.6.34.8-0.2 default (i686).
>
> Immediately after a reboot, I couldn’t see the internet but i am able
> to get into the router (with the usual 192.168.0.1) so it would seem
> that the WiFi link is working but Firefox and Thunderbird can’t see any
> servers. Very strange. I re-installed the WiFi card (Atheros AR5001) but
> no change. I think the relevant module is ath5k. Any ideas gratefully
> received!
If “getting into the router” means that ‘ping 192.168.0.1’ works, then your
routing may be messed up, or you have a DNS problem. Please post the output of
the following:
Hi lwfinger, thanks for your message. Here’s the output.
I notice when I compare the routing table (below) with the one from an ethernet-connected PC that there may be a line missing.
If so, how do I modify the file please?
peter@linux-mufg:~> ping -c 3 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=3.49 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=1.29 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=1.41 ms
— 192.168.0.1 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.296/2.069/3.499/1.012 ms
peter@linux-mufg:~> ping -c 3 8.8.8.8
connect: Network is unreachable
peter@linux-mufg:~> /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.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 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
peter@linux-mufg:~> 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.0.1
peter@linux-mufg:~> ping -c 3 Google
connect: Network is unreachable
peter@linux-mufg:~>
On 05/02/2011 04:06 AM, petermcph wrote:
>
> Hi lwfinger, thanks for your message. Here’s the output.
> I notice when I compare the routing table (below) with the one from an
> ethernet-connected PC that there may be a line missing.
> If so, how do I modify the file please?
>
> peter@linux-mufg:~> ping -c 3 192.168.0.1
> PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
> 64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=3.49 ms
> 64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=1.29 ms
> 64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=1.41 ms
>
> — 192.168.0.1 ping statistics —
> 3 packets transmitted, 3 received, 0% packet loss, time 2003ms
> rtt min/avg/max/mdev = 1.296/2.069/3.499/1.012 ms
>
> peter@linux-mufg:~> ping -c 3 8.8.8.8
> connect: Network is unreachable
>
> peter@linux-mufg:~> /sbin/route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.0.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
> wlan0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
> lo
>
> peter@linux-mufg:~> 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.0.1
>
> peter@linux-mufg:~> ping -c 3 ‘Google’ (http://www.google.com)
> connect: Network is unreachable
> peter@linux-mufg:~>
You are indeed missing the default gateway line. Once you run the command below,
it should work
sudo /sbin/route add default gw 192.168.0.1
The table that you showed above has information on how to reach 192.168.0.X
(Rule 1), but nothing else.
Ah, magic - that’s done the trick. And just in time, I’m going camping tomorrow for a few weeks - would have been lost without my trusty netbook.
Many thanks, I’ll make a note of the command for future use! I did poke around looking for information on commands but without knowing where to look, it could take a while.
On 05/02/2011 12:06 PM, petermcph wrote:
>
> Ah, magic - that’s done the trick. And just in time, I’m going camping
> tomorrow for a few weeks - would have been lost without my trusty
> netbook.
> Many thanks, I’ll make a note of the command for future use! I did poke
> around looking for information on commands but without knowing where to
> look, it could take a while.
“man” is your friend. If you are not sure where to look, “man -k <search_term>”
will look through all the man files for your <search_term>". The command
“apropos” is a synonym for “man -k”.
When I get back I’ll look into all that - it’s about time I did. I just realised I can use “man man” to start me off.
I think I’ve come across this gateway problem before. When 11.4 was released, I installed it on the netbook but came up with the same WiFi problem and after trying to fix it, went back to 11.3 (which worked ok until the recent update). I wouldn’t be surprised if it’s the same problem. I’ll have another go at 11.4 when I return.
