On Sunday 22 January 2006 19:24, Alex Bartonek wrote:
if you can ping other computers on "your" network using the wireless, then 
your wireless must be configured alright.  if this is so, i would look on my 
router, to see if it has the dhcp servers listed from my isp.  i know, i use 
a cable modem with a linksys router, and my isp's nameservers are actually 
stored in my router.  this is how the dhcp client obtains the dns entries for 
my /etc/resolv.conf file.  i would then make sure that the isp's listed in 
my /etc/resolve.conf match the ones stored in my router.

if all of this checks out fine, then perhpas there could be an issue with your 
router not allowing your traffice to pass to the internet?  could there be a 
security setting within your router thats blocking your ip traffic?

tom
> while I realize you're trying to help..but searching
> suse's support portal without knowing the keywords to
> find that article really doesnt help. :/
> thx
>
> --- jeffrey franc-law <[EMAIL PROTECTED]> wrote:
>
>
> ---------------------------------
>     I had this same problem.  For me, it had to do
> with the DHCP, which wasactivated for the wired
> network but not the wireless.  I can't rememberexactly
> what I did, but the explaination was really good on
> the susesupport 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
> recognizedbut didnt really mess with it enough to get
> itworking.  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
> amconnected, I get a IP address assigned..I can
> pingother machines on my network but I cant connect to
> theinternet.  Is there something I missed? It has
> workedbefore 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
> [EMAIL PROTECTED]://lists.pcxperience.com/cgi-bin/ma
>ilman/listinfo/linuxr3000Wiki at http://prinsig.se/weekee/
>
>
> -- Jeffrey Michael Franc-Law, MD, CCFP.EM, D Sport
> MedClinical Lecturer, Dept of Emergency Med,
> University of AlbertaChief Medical Officer, World
> Masters Games 2005Disaster Plan Coordinator, Dept of
> Emergency Med, University of
> [EMAIL PROTECTED]: 780-903-5635Fax:
> 780-437-9673
>
> > _______________________________________________
> > LinuxR3000 mailing list
> > [email protected]
>
> http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
>
> > Wiki at http://prinsig.se/weekee/
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> LinuxR3000 mailing list
> [email protected]
> http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
> Wiki at http://prinsig.se/weekee/
_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/

Reply via email to