[SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

Caliburn · 2008-02-21 02:39:48

I took note to print out the 40+ page Wiki manual in regards to installing Arch, and while the majority of it looks like the same old, same old, sadly there's no real mention of going about handling a PPP connection. Yes, it's very doable on this particular system - I've a base phone line dedicated to data transmission as I'm living in an area without cable or DSL. The amount of time it takes to download X and it's children doesn't mean much to me.

On looking through the forums, I've found several posts in which possibly -could- help, but none of which have actually followed through. There's been a post in regards to installing PPP with an already existing connection (cable connection), and as a result that knocks me out of said water. There's also a posting a few people mention with a dialup walkthrough available on the Wiki, however said document no longer exists anytime anyone offers a link to it.

I've tried grabbing wvdial and wvstreams, and have successfully copied them to disc per extracting the data first (see http://bbs.archlinux.org/viewtopic.php?id=44287 ), but on trying to install these through what I expect to be the usual methods (GCC: /configure, make, make install), naturally there is no compiler component available in the install and ./configure just laughs.

I can't utilize any pacman resources, as I have no connection to download anything in Arch currently. I want to learn Arch, but I feel a bit left out in the cold here on 56k island.

Any resources I could use to help me with setup of a 56k on Arch? I feel I'd have it comfortably with the Wiki article from that point forward, I'm just stuck at the after-install with this.

Last edited by Caliburn (2008-03-09 01:54:19)

rossm · 2008-02-21 05:06:23

Hi Caliburn,
Don't despair. Have a look at this page.
http://axion.physics.ubc.ca/ppp-linux.html
It shows you how to do it just using ppp and included programs.

matahari · 2008-02-21 05:32:18

what about this wiki page http://wiki.archlinux.org/index.php/Dia … aler_HOWTO, it use ppp (and its in core cd). im on dialup too, but via gprs.

Caliburn · 2008-03-02 05:51:22

Hey guys.

Thanks for the replies. With a combination of both your suggestions and a couple of hours with tinkering, pppd is running well. The two suggested documents both of you have given are a must for anyone needing help with the process. Simply speaking - where one document didn't help, the other document did.

Thanks again.

Now I'm off to continue the process. I'm rather impressed with Arch thus far, following the wiki's documentation for Arch newbies and all.

Pudge · 2008-03-02 15:31:14

I realize that time is a valuable resource, but if you have the time could you possibly write up a quick tutorial on how you accomplished this?

Is your modem an Intel WinModem? I've heard that it is almost impossible to get WinModems to work with any Kernel past 2.24.X.

I tried getting Arch and 56K to work on a friend's computer with an Intel 537e WinModem and finally gave up.

Pudge

Caliburn · 2008-03-04 01:16:12

Pudge:

I've three modems on this particular box, all for various reasons and one of those reasons being testing purposes while under various Linux distros.

The modem I'm currently using is a serial Zoom modem, hardware-based.

I also have a Zoom USB modem which is a software-based modem, but, as it said on the box, the modem does come with Linux drivers. I have successfully used the Zoom USB modem in Ubuntu and Sabayon, but I have not tried the modem under Arch.

I also have an Intel 536EP Winmodem, which does have drivers available for it under Linux. I know this driver functioned with the preloaded driver under Mepis and my manually loaded driver under Sabayon Linux, however I have not tested this modem with Arch.

I believe there is a 536 (and if my memory serves me correctly, a 537) compressed driver package available somewhere online. While I'd try to install the modems and give them a shot, and I may sooner or later if the interest hits me, right now I can't say I'm too interested in messing with a good thing. I haven't heard of the modems not working with the newer kernels, though.. that's interesting.

In regards to the tutorial, I really can't say much more than the two links provided above by others already give. As a default, pppd is installed from the Arch CD with an editable file regarding it's configuration (/etc/ppp/options):

lock
modem
/dev/ttyS1
57600
debug
noauth
defaultroute
noipdefault
user username
password password
connect "chat -v \'\' ATZ OK ATDTnumberofisp CONNECT"

.. /dev/ttyS1 being the modem's port (COM2), the user listing the username, the password listing the password, and the numberofisp being the number of the ISP you're dialing..

As well as adding the following in /etc/ppp/chap-secrets:

\"username\" * \"password\"

.. essentially allowed me to connect with no errors. No idea whether or not chap-secrets was necessary considering the username and password are already stated in /etc/ppp/options, but it's suitable for my connection currently until I find out differently.

Again, I may try to install the modems, but I won't guarantee it. I hope I've helped somehow though.

Caliburn · 2008-03-04 07:32:12

After the storms we'd received, I was able to look around on Google for a link regarding the Intel 536EP and Intel 537 that pointed back to Arch's Wiki.

http://wiki.archlinux.org/index.php/Int … dem_Driver

The work that went into the Wiki is really beginning to surprise me as a newbie to Arch. Still, as I haven't tried the modem yet, I've no idea whether or not this driver actually works - just a forewarning. I may do that a little later.

Whenever I tried to compile a version of the Intel 536EP driver on the system manually (with using an old .tar.gz source file I had lying around for another distro), make 536 worked, but the next make of the process did not unfortunately.

Thought I'd report back as a just in case.

EDIT: The Intel 536EP does work under the Arch-provided drivers as listed in the Wiki entry above (I'm using it currently). You'll have to load said drivers as above from an already-existing Internet connection short of, I'm assuming, grabbing them manually for installation. As we're already off-topic for this particular thread with the Winmodem additions, more comments need to go in a thread suited for it.

Last edited by Caliburn (2008-03-04 16:26:04)

Pudge · 2008-03-09 03:28:33

Using an external serial modem and wvdial I can now dial up the ISP and it looks like it connects. But nothing happens with the browser or anything. In /etc/rc.conf the default network interface is eth0:

lo="lo 127.0.0.1"
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(lo eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

What do I need to add/change to set up /dev/ttyS0 as a network interface? ifconfig -a lists eth0 and lo but doesn't show anything related to the serial port. Do I need to do anything with /etc/resolv.conf ? I can't find anything on this in the Wiki or anything.

Thanks for any help.

Pudge

Caliburn · 2008-03-09 04:16:43

Being that /dev/ttyS0, S1, S2, S3 are all COMport configurations (ie. /dev/ttyS0 = COM1, /dev/ttyS1 = COM2, so on and so forth), and given that your machine has detected the connected modem on Arch's boot, there's no need to set the modem up as it's an automatic entity short of being a Winmodem. If the modem is a Winmodem, you'll need to install the Linux drivers (if there are any). Winmodems usually resort to /dev/modem/ as being the requested interface and not /dev/ttyS#. However, my intel 536EP resorted to /dev/536ep0 on installing the Arch-provided driver with a serial modem connected. Such information would need to be added to the /etc/ppp/options file to correctly point the dialer as to where the dialing device is.

Getting back on track..

In regards to /etc/resolv.conf, my file is similar to:

#
# /etc/resolv.conf
#
#search <yourdomain.tld>
#nameserver <ip>
nameserver XX.XX.XX.XX
nameserver XX.XX.XX.XX
# End of file

.. where XX.XX.XX.XX is the listing of both the primary and secondary nameserver IPs provided from your ISP. Usually these can be found in a FAQ or by requesting the information from the ISP itself, but I've typically found them in an ISP-provided FAQ.

I hope I've helped.

EDIT: And just to add, I didn't have to do anything to /etc/rc.conf.

EDIT #2: Visit http://lonestar.texas.net/helpdesk/linux.html for more information in regards to this. I've noted they keep password out of the /etc/ppp/options file, and it's best if you follow their instructions in regards to doing so. I'm sure they've more experience with ppp than I judging from their scripts.

ie: /etc/ppp/chap-secrets:

* * passwordforlogin

ie: /etc/ppp/pap-secrets:

* * passwordforlogin

and within /etc/ppp/options, remove the password line. Should work.

Last edited by Caliburn (2008-03-09 04:40:31)

Arch Linux

#1 2008-02-21 02:39:48

[SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

#2 2008-02-21 05:06:23

Re: [SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

#3 2008-02-21 05:32:18

Re: [SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

#4 2008-03-02 05:51:22

Re: [SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

#5 2008-03-02 15:31:14

Re: [SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

#6 2008-03-04 01:16:12

Re: [SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

#7 2008-03-04 07:32:12

Re: [SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

#8 2008-03-09 03:28:33

Re: [SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

#9 2008-03-09 04:16:43

Re: [SOLVED] 56k, pppd (what worked for me w/ HOWTOs via links).

Board footer