[K.-H.]    That    question    is    completely    confused.   Read
     [68]http://www.linuxgazette.com/tag/ask-the-gang.html to get an idea how
     to ask a good question. It would help to tell what netscape is doing/not
     doing. proxy setting in netscape. output of /sbin/route -n (one of the
     tools you ask for) would also help in finding out whats the problem.

     Generally:

     Your computer has an IP-adress attached to each of its interfaces. It is
     127.0.0.1 on interface lo (loop back), it might have ethernet connections
     like eth0 with local IP-adresses (e.g. 10.10.10.1) and once you've dialed
     out via modem/ISDN you've a [i]ppp0 interface which got a dynamic IP
     adress assigned. That might be any IP-adress.

     The IP-traffic is directed by routing, thats's the roadmap which tells the
     kernel where to send each IP packet depending on the IP. A packet to
     127.0.0.1  will  be  passed to interface lo, while with appropriate
     netmask/broadcast setting any packet to 10.x.x.x will be passed to eth0.
     To direct all unknown (outside) IP-adresses to [i]ppp0 you would set a
     default route (shows up as 0.0.0.0 in route outpute) specifying where to
     send all the traffic.

     If your netscape doesn't see the outside, it's because the packets go
     wrong (or the interface is not up and running).

     interfaces are checked with ifconfig, routes with route [-n].

     WLAN is no different, looks like an ethernet but has some special tools
     for the interface and status: iwconfig, iwspy, iwlist, iwpriv,... route is
     the same.

     [69]http://www.oreillynet.com/pub/a/wireless/2001/03/06/recipe.htmlhasa
     Linux-setup for 802.11b cards. There are links to the wireless-tools which
     will help diagnose and set WLAN specific things.

     K.-H.
     _________________________________________________________________

      This page edited and maintained by the Editors of Linux Gazette
HTML script maintained by [70]Heather Stern of Starshine Technical Services,
                       [71]http://www.starshine.org/ 
     _________________________________________________________________

   Published in Issue 102 of Linux Gazette, May 2004

The Answer Gang

   [72]LINUX GAZETTE 
   ...making Linux just a little more fun!

                          (?) The Answer Gang (!)
By Jim Dennis, Karl-Heinz Herrmann, Breen, Chris, and... ([73]meet the Gang)
                ... the Editors of Linux Gazette... and [74]You! 

    We have guidelines for [75]asking and [76]answering questions. Linux
                          questions only, please.
  We make no guarantees about answers, but you can be anonymous on request.
 See also: The Answer Gang's [77]Knowledge Base and the LG [78]Search Engine
     _________________________________________________________________

  Contents:

   [79]¶: Greetings From Heather Stern

   [80](?) Redhat + scsi RAID = Excedrin headache #459
   [81](?) howto
   [82](?) Wireless networking
            ____________________________________________________

(¶) Greetings from Heather Stern

   Greetings dear readers, and welcome once more to the wild and whacky world
   of The Answer Gang. Sorry the workshop's a mess. Even sorrier we took so
   long to clear out the sawdust and get these bits to you. However, I hope
   you find the threads a little more readable; my apologies to everyone who
   got  nipped  by my confused battle with the stylesheet last month. The
   bandaids are off now and the scratches are healing nicely... 

   Which brings me to thoughts of the next battle ahead. Upgradability has
   always been something I care about; thence my careful management of my
   distros, whichever they are, and a particular fondness for [83]Debian's
   apt-get feature. (I look forward to trying [84]yum when I have Copious Free
   Time^tm to try Fedore, and recommend [85]urpmi to Mandrake fans.) Still, the
   main thing that gives any distro is the policies its maintainers apply. RPM
   based distros are unique because of how the dependencies are laid out - if
   they're good, installs of new software - even source based softare, are
   easy, and if not, then upgrades are just hellish. In other words, these
   maintainers... they are your sysadmin, until you take the reins in your
   hands to do it yourself - and even then, the tools they make handiest to
   help you with that also apply policy, at least about where the control
   files go. 

   As  Linux is increasingly being taken up by people who care about what
   they're going to do with it, rather than folks who really care what their
   OS is at all under the hood - this is getting more important. The paper
   zines have been muttering under their breath for years "not ready for the
   enterprise" - what they mean is we dunno, as in Ghostbusters, "who ya gonna
   call?" 

   Nobody claims that's the problem anymore, all the big names are well known