I had this same problem. For me, it had to do with the DHCP, which was
activated for the wired network but not the wireless. I can't remember
exactly what I did, but the explaination was really good on the suse
support portal.
ciao,
jfl
Frank Edwards wrote:
On Sunday 22 January 2006 1:00 pm, Alex Bartonek
<[EMAIL PROTECTED]> wrote:
well I somewhat got the built-in wireless recognized
but didnt really mess with it enough to get it
working. I bought a gigabyte technology usb stick.
Its setup through yast (SuSE 10), with the wep key,
channel, essid etc. With kwifimanager it shows I am
connected, I get a IP address assigned..I can ping
other machines on my network but I cant connect to the
internet. Is there something I missed? It has worked
before but never automatically on bootup.
Alex
Basic networking:
1. Do you have a link light -- check by looking at the plug where the cable
is connected or where the wifi card is? (An LED on the NIC that shows
you're connected to a switch, hub, or another computer.)
2. Do you have an IP address -- check with {/sbin/}ifconfig? (If you
configured a static address, then you should have one. Otherwise, there
might not be a DHCP server within broadcast range; DHCP is a broadcast
protocol and isn't automatically forwarded through routers unless the
router is told to do so.)
3. Do you have connectivity -- check with {/bin/}ping? (With a static IP
address, there's no way to know what other addresses might be on the
network that you can check for. You can try running {/usr/sbin/}tcpdump
and scanning the output to see what other IP addresses are out there.
You'll need to hit Ctrl-C to stop the command. With DHCP, your machine has
at least the IP address of the DHCP server, so that's a good one to try.
You can find that information from /var/run/dhcpcd if you're using the ISC
DHCP client. I'm using ifplugd and I can't find that information anywhere!?
Problems here include the general configuration of the IP stack, but a
common problem is a routing table entry that's wrong. Key point: just
because a packet can get from machine A to machine B, doesn't mean it can
get from machine B to machine A! It depends on the routing tables of both
machines and all intermediate points.)
4. Does your DNS configuration resolve hostnames correctly -- check with
{/usr/bin/}host? (Running the host command and providing a hostname will
tell if you your DNS is configured correctly. Do not use ping (or similar)
for this, because they will check the local /etc/hosts file first (by
default; see /etc/nsswitch.conf) which means some names may resolve from
the /etc/hosts file while others won't.)
5. Check end-to-end connectivity -- can you connect to a web server or ftp
server? (Using telnet to check connectivity to a particular web server
takes the browser out of the loop. Try running "telnet web.server.name 80"
to get to port 80 on the server. You should see a "connected" message.
Type some garbage, such as "x", and hit Enter. You should get an error
message from the server. For computers behind an proxy (active or
passive), telnet may not work because you may need to direct your
connection to the proxy server instead. If connecting to the proxy works,
go back to testing with the browser, since the proxy protocols are
complicated enough that I'm not going to detail them here.)
If all steps through step 5 are working, but your web browser or email still
don't work, run a network packet sniffer and monitor the traffic. At this
point, the problem is usually the configuration of the client (browser,
ftp, whatever), but in a Windoze network it could also be connection or
authentication issues with a Windoze domain controller (PDC or AD server).
That's beyond the scope of this message. :-)
Good luck!
_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/
--
Jeffrey Michael Franc-Law, MD, CCFP.EM, D Sport Med
Clinical Lecturer, Dept of Emergency Med, University of Alberta
Chief Medical Officer, World Masters Games 2005
Disaster Plan Coordinator, Dept of Emergency Med, University of Alberta
[EMAIL PROTECTED]
Phone: 780-903-5635
Fax: 780-437-9673
|
