By Joshua "Tiberian"
Hello again, and welcome to Tubby Tibs Fine Dining. Today
on the menu, we have bronto-TCP/IP, pizza al la Console, and
Fried Daemon Chips for the kids. Sit down, pull up a chair,
sedate the kids, and watch some MST3K as we get into the Wonderful
World of Linux Networking!
Scott's Internet safety note: Also, you should make a minor
point that you should NEVER EVER do anything other than system
administration chores as root. Even running a Quake server
is best done as a normal user. There's just too much of a
risk of nuking something, or of getting something compromised
because one of your binaries was running as root. :)
Josh's Internet safety note: Don't IRC from root. It's bad.
Take my advice at face value, I don't want to start another
crop of script kiddies due to something I include here. :)
it is, take a good look!
probably already been screwing around in Linux and found the
handily little kppp, right? If not, open up your KDE menu
and click on "kppp" (probably somewhere under "internet").
For those not running KDE, type "kppp" on the console,
or, if your UI supports reading the KDE menus, you can click
on it from in there. If you've got a modem, this is your ticket
to muck and mayhem on the internet. You'll also want to get
a copy of Licq (ICQ is probably included in most distributions,
but Licq is my personal favorite). It can be found on The
Licq Homepage (and requires QT 2.0.x).
How do you know what kind of broadband connection you have?
Well, if you connect to your ISP and you get "flashy
computers" in your clock tray, then you most likely are
running WINPoET. See the ADSL section. If you turn your computer
on and have a DIFFERENT IP each time, then you are using DHCP.
Follow the DHCPCD instructions. And if you are a lucky bastard
and are always on and always have the same IP, you would just
use "ifconfig eth0 [assigned ipaddress]" and you
would be right as rain.
If you have @Home, or a comparable cable or ADSL that offers
static IPs, then you know that you have two or three IP addresses
to use for your service. It's not as simple as just plugging
those IPs in, you also need your DNS servers. DNS servers
are what your computer talks to in order to get the IPs for
servers that you request. You can either call up your ISP
or find out with a "whois" as to what your DNS servers
(I'm cheating, I am already online. You'll have to do this from someone else's computer. I am pretty sure that Windows has a whois command in the
later versions. If not, we can call them on the phone.)
BigIron:~# whois home.com
Whois Server Version 1.1
Domain names in the .com, .net, and .org domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
Domain Name: HOME.COM
Registrar: NETWORK SOLUTIONS, INC.
Whois Server: whois.networksolutions.com
Referral URL: www.networksolutions.com
Name Server: NS2.HOME.NET
Name Server: NS1.HOME.NET
Updated Date: 16-dec-1999
>>> Last update of whois database: Mon, 15 May 00 04:07:59 EDT <<<
The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and
Whoohoo! See the entry for "Name Server"? We want both of those. Write them down!
Ping that nameserver! cyrex200:~$ ping ns2.home.net PING ns2.home.net (184.108.40.206): 56 data bytes 64 bytes from 220.127.116.11: icmp_seq=0 ttl=240
time=73.3 ms 64 bytes from 18.104.22.168: icmp_seq=1 ttl=240 time=64.7 ms
--- ns2.home.net ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 64.7/69.0/73.3 ms
Hit ^c when you see the part about "64 bytes from.....". See that IP address? Write that down! Do it agian for the other server.
Next, pop open /etc/resolv.conf.
The proper format for resolv.conf is "nameserver <ipaddress>" and following that line, "secondary <ipaddress>" with
one blank line at the end of the file. Your resolv.conf should look like:
(Notice the blank line.) It doesn't really matter which order
you put the servers in. Linux will keep going down the list
if a server is down. If all the servers are down, then your
ISP is probably kaput, so you probably shouldn't worry about
getting online anyway.
The common problem a lot of people run into is that your
ISP won't give you a nameserver or finds out that you are
running Linux and curtly denies any further help. Call them
back, and tell them you are running a Macintosh. Macs need
nameservers to connect, so the user has to enter them manually.
Mac users aren't a threat! Be proud to be an apple. (Wear
the penguin under the tie). After you ask them for the nameservers
and tell them how nice it is to use the internet and compliment
their good service, then you can plug them into your resolv.conf.
If they STILL won't surrender the nameservers and/or don't
support Mac, you might want to find a new ISP. As usual, if
you are still hurting after this breakneck speed run through,
try looking things up on The
Linux Documentation Project under the mini-how-to section.