Ok, no x session, so we do it the slackware way on the command line with the help of dialog.
By the look of your questions in the last post it might be best if I start at the very beginning and go step by step. If you know some of this already bear with me, I'm not trying to patronise you. Other newbies who know less might benifit as well.
I'll explain each step as I would do it on my machine if your not completely familiar with something google it once your online. Once you gotten a basic connection set up you can move onto the other things.
##########################################################################
Setting up a dialup connection in slackware for a stand alone machine, eg not
connected to a LAN:
Unless you want to edit the relevant files by hand, you will need to use two
command line tools, ( 1 ) netconfig ( 2 ) pppsetup. Brief descriptions of
what to do withe netconfig and pppsetup follows below, but read the complete
text/instructions in each step of the commands. You may learn
something along the way.
In a terminal type "netconfig" and hit enter. The steps
in order are:
(1) Enter name for host: that is the name of the machine, the default is
darkstar if you don't enter anything, I'll use my name "rick"
(2) Enter domain name: this would be used to enter the domain name of your
machine (not your ISP's) you can enter anything you like, I'll use "miles.home.
If the box was on a local area network ( LAN ) its address would be
rick@miles.home. In actual fact this box is also the server for a
small LAN. The setup is the same for the server as for the standalone in my case.
(3) How does the machine connect to the network: since this is presumably a standalone work
station I want "loopback", to select it I downarrow to loopback and hit enter.
(4) I am then presented with my machine's IP address (internal to my box) and
netmask. These are 127.0.0.1 and 255.255.255.0 respectively and would be the
same on any box.
I am now finished setting up a loopback network in my box. I have an internal
winmodem ith a Lucent chipset and have already compiled and installed my
drivers (modules) using the ltmodem package. The command "lsmod" shows me that
they are loaded so I can expect the modem to work. If I was using an external
modem I would not have to worry about this.
In a consol I type "pppsetup" and hit enter. The steps
involved are:
(1) I first have to enter the phone number of my ISP. I must prefix it with the
letters " atd ", so I enter " atd01985557777 "
(2) Next I select the location of my modem, I'll use /dev/modem which points to
/dev/tty0 (which would be com port 1 in an MS system) where I know it is.
(3) Next I am asked to select the baud rate for my modem. I select 115200
because I'm still living in the stone age.
(4) When asked if my ISP uses call back I answer "no" because very few do these
days.
(5) My modem works fine using the default modem string. In general, most
recentlymade modems produced for the mass market will.
(6) I will then be prompted to enter the name of my ISP. I will leave out the
leading " w.w.w. " and enter " optusnet.com.au ".
(7) I will then be prompted to enter my ISP's IP address. If I was logged onto
the net I could get this easily enough while connected. Since I'm not, I call my
ISP's service desk and ask for the primary and secondary dns numbers.
I will be told that I don't need them to set up my connection because the cd
they sent me does it all for me. When I say that I'm running linux the
customer service rep will tell me that optusnet doesn't support linux and I will
tell her that linux can stand up by itself and don't need any support. After
that I'll get my dns numbers real quick because she wants me to go away.
I only need one number for pppsetup so I type in 203.2.75.132.
(8) I am next asked to nominate which authentication protocol to use. I select
"PAP" because I've done this before, but it's a safe bet and in any case if
it don't work I can always come backand run pppsetup again and change it to
CHAP.
(9) I am asked to enter my login name, This is the name my ISP will be looking
for when it authenticates my attempted connection. It may not necessarily be the
same as the name in my email address. I know what it is and enter it.
(10) Finally I will be asked to provide my account password which again may or
may not be the same one I use to access my emails once logged in.
That will complete the ppsetup routine after which I should be able to make a
connection using the command " /usr/sbin/ppp-go ". I can disconnect using the
command " /usr/sbin/ppp-off "
The output on my machine when I run ppp-go is provided below. The connection was
made as a normal user with the settings in netconfig and pppsetup that I
detailed above.
rick@rick:/mnt/hda8/rick$ /usr/sbin/ppp-go
rick@rick:/mnt/hda8/rick$ Serial connection established.
Using interface ppp0
Connect: ppp0 <--> /dev/modem
local IP address 211.29.114.135
remote IP address 211.29.114.254
########################################################################
Note that you will have to run netconfig and pppsetup as root. You will probably
have to test you first connection as root However. as soon as you see that you
have made a connection, disconnect!!!!!
Don't go online as root even if it is only a dialup account for a couple hours. I have had people try to get in while logged onto the net, they may visit you too someday. Also, once you've got yourself in order set up a firewall.
It's been awhile since I thought about it and the above was done from notes
(get in the habit of taking notes), you will most likely have to:
suid /usr/sbin/ppp-go
suid /usr/sbin/ppp-off
suid /usr/sbin/pppd
suid /usf/sbin/pppoe
in order to allow a normal user to make a connection. I'm not too sure about the
permissions of (and in) /etc/ppp, but if you were able to make a connection as
root you know it works and you may just have to play around a bit to set it up
for a normal user.
slackware isp setup.
much love justwantin
and yes, thanks for the how-to! I guess the only difference in a standard DSL setup would be the driver? Or do you still have to define an authentication method? <edit> answer: yes.
