|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Wireless Questions about wireless networking setup, use, and wireless specific applications |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
||||
|
I forgot to mention - ipv6 IS disabled on this laptop. Its been disabled as part of the initial install.
|
|
||||
|
My wife just reminded me our ISP went down earlier this week for a few hours, and we did have to reboot our router to get our LAN internet access back.
I also note the Laptop's wireless (a month ago) successfully could access the Internet via a live CD on our home LAN. So I think I will give that a try (ie boot to a liveCD and see if I can configure the wireless to access the Internet with that liveCD in place). IF I can still access the Internet via the liveCD on the laptop, that will take our router out of "consideration" as the cause. |
|
||||
|
Quote:
I think that proves its not an ISP nor our LAN router at issue here. Rather there is a configuration problem with the 64-bit openSUSE-11.1 KDE-4.3.2 on the laptop, such that it can access our WLAN but not access the Internet. Its very puzzling. One thing I note is after the last time I had Internet access on that laptop (with openSUSE-11.1) I changed the graphic driver to the latest ATI proprietary driver for a Radeon 3450 (which is the hardware on that laptop). But I can't see that being related to an Internet specific wireless problem. I'm out of my depth here for investigating. Now that it is narrowed down to a 64-bit openSUSE-11.1 (w/KDE-4.3.2) specific problem (which may not be relevant to KDE-4.3.2) are there any suggestions where I should investigate? Again note wireless to our LAN works, it is just wireless to the Internet that fails with the installed openSUSE-11.1. (but works from a liveCD) |
|
|||
|
On 11/07/2009 06:46 AM, oldcpu wrote:
> > oldcpu;2061436 Wrote: >> My wife just reminded me our ISP went down earlier this week for a few >> hours, and we did have to reboot our router to get our LAN internet >> access back. >> >> I also note the Laptop's wireless (a month ago) successfully could >> access the Internet via a live CD on our home LAN. So I think I will >> give that a try (ie boot to a liveCD and see if I can configure the >> wireless to access the Internet with that liveCD in place). IF I can >> still access the Internet via the liveCD on the laptop, that will take >> our router out of "consideration" as the cause. > > I just finished booting to the openSUSE-11.2 RC2 KDE live CD. I went to > YaST, configured for the traditional ifup, entered our LAN ssid, > passphrase, and the laptop can now see the LAN and surf the Internet > when booting to the liveCD. > > I think that proves its not an ISP nor our LAN router at issue here. > Rather there is a configuration problem with the 64-bit openSUSE-11.1 > KDE-4.3.2 on the laptop, such that it can access our WLAN but not access > the Internet. Its very puzzling. One thing I note is after the last > time I had Internet access on that laptop (with openSUSE-11.1) I changed > the graphic driver to the latest ATI proprietary driver for a Radeon > 3450 (which is the hardware on that laptop). But I can't see that being > related to an Internet specific wireless problem. > > I'm out of my depth here for investigating. Now that it is narrowed > down to a 64-bit openSUSE-11.1 (w/KDE-4.3.2) specific problem (which may > not be relevant to KDE-4.3.2) are there any suggestions where I should > investigate? Again note wireless to our LAN works, it is just wireless > to the Internet that fails with the installed openSUSE-11.1. (but works > from a liveCD) I always suspect DNS when you can access local networks, but not the Internet. You have a valid connection, and routing is likely OK. (1) When you access some machine on the local network, is this by IP, by entries in /etc/hosts, or are you running a local name server? (2) Does 'ping 74.125.19.103' work? If it does, does 'ping www.google.com' work? (3) If you ifdown the connection, delete /etc/resolv.conf, and ifup the connection, does that change anything in step 2? |
|
||||
|
Thankyou for your reply.
Quote:
Quote:
Quote:
It does not change anything. I still get destination Host is still Unreachable. |
|
|||
|
Hmm. This problem seems tougher than most.
Let's concentrate on differences between wired that works, and wireless that doesn't. Please look at the output of '/sbin/route -n' for both cases. Are there any differences other than the "ethX" vs "wlanY" in the Iface column? I expect X to be 0 and Y to be 0 or 1. Please 'cat /etc/resolv.conf' for the two cases. Any differences? Check the BOOTPROTO line in /etc/sysconfig/network/ifcfg-ethX and /etc/sysconfig/network/ifcfg-wlanY. Do both say BOOTPROTO='dhcp4'? Does the ethX file have STARTMODE='ifplugd' and the wlanY one have STARTMODE='auto'? |
|
||||
|
Did something get changed in the firewall, to cause it to lock down the wireless?
|
|
|||
|
On 11/07/2009 12:06 PM, Wilson Phillips wrote:
> > Did something get changed in the firewall, to cause it to lock down the > wireless? Unlikely, but it could be worth testing with firewall off. |
|
||||
|
This is puzzling. I keep asking if I am doing something silly , but I can't find anything suggestive of a silly mistake.
Quote:
oldcpu@dell:~> /sbin/route -n Code:
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 192.168.123.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.123.254 0.0.0.0 UG 0 0 0 eth0
Quote:
Code:
### Please remove (at least) this line when you modify the file! nameserver 192.168.2.1 nameserver 192.168.123.254 Quote:
STARTMODE in both cases equals "auto". |
![]() |
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|