Aric C. Wilisch wrote:
I have this problem as well. I have a Toshiba Satallite with an Orinoco Gold pcmcia card. Thing is, the card works fine with my Windows XP partition, it's worked well with my distributions of Red Hat and Mandrake and EVEN worked on Suse 8.2. I know it works because when it didn't work with Suse 9, I blew away the linux partition and reloaded Suse 8.2. Wireless came up and worked like a champ. So I dropped my Suse 9 cd in and reloaded that, immediately stopped working. Built in Ethernet works great, rewrites the resolv.conf file and life is dandy. But the minute I put that wireless card in, the only thing I get in is an ip address, and the only thing in resolv.conf is my domain name.
So, if anyone from Suse is listening in, this isn't an isolated problem. You've downgraded the wireless performance. Really hope someone comes out with a fix that DOESN'T involve manually setting routes and manually configuring the resolv.conf file. We never had to do it before, shouldn't have to do it now.
Regards, Aric Wilisch knight@shadowrealms.cc
From: david stevenson
Date: Sat, 1 Nov 2003 20:22:26 +0000 Message-Id: <200311012022.26023.suse@avoncliff.com> Subject: Re: [SLE] wireless is able to browse the lan but not the internet On Saturday 01 November 2003 4:49 am, chadd wrote:
I've found a problem on my notebook (Compaq Armada M700, WL110 wireless) whereas the embedded nic will acquire the IP address & the nameserver
info
but the wireless will only obtain an IP address. This allows me to
browse
my home LAN (everything behind the router) but I cannot get out when
only
using my wireless nic.
Initially I thought I would have to set my gateway to my router's address (192.168.1.1) but I've found that doesn't make a difference. I've tried this at home (w/ a Linksys router). Even if I activate eht0
(embedded wired nic) first & get the nameserver info entered into resolv.conf then turn off eth0 I cannot get past a my router.
Furthermore
when I plug the ethernet back in and remove the wireless nic & restart
the
network service (/etc/rc.d/network restart) I still cannot get out.
From
that point I'm stuck with a reboot and letting the system come up
without
the wireless nic installed.
I guess the first question would be: Does anyone know why my wireless will not acquire the nameserver info whereas the embedded nic will?
Secondly, even once I enter the nameserver info manually, why will the wireless not hit the Internet?
I have my SSID & encryption set correctly or I wouldn't be getting even an ip address & the ability to browse the internal network. I've also
tried
turning the encryption off to rule that out but with no luck. Also as
FYI
I've not touched the firewall this time. I've went with the default install settings. Last time I did the install though I did go through
and
set everything at the easiest level.
If anyone can give me a direction to go (other than rtfm) I would really appreciate it. I've been a red hat user for about 3 years now and I've
really started to like how Suse is looking now. If I cannot solve this
problem them I'll be stuck going back to red hat. From what I've seen
with
I had the same type problem when running the SuSEfirewall. If I turned off the firewall, it waked fine. Art
Suse 9, I would like to stick with it instead.
Any ideas?
You have not told us about your setup. I am guessing some form of broadband router connected by ethernet to a wireless access point, or directly to the PC. So when you ask the access point, via dhcp, for an IP you also get routing infomation. But when you ask the access point you get only an IP. If this is the problem then try reconfiguring the access point to pass DHCP though to the router. David