John Gabriele wrote:

> John Gabriele wrote:
>
>>
>> Thanks for the replies Otako.
>>
>
> Whoops. Sorry, repiled to the wrong branch in this discussion.
>
>

Double whoops. Please ignore previous message (an older version
of OS X Thunderbird is messin' with my head

Also, I posted for help in comp.os.linux.networking, got a helpful
reply, then replied back to both that group and this one -- see
new thread below if interested.

I'm figuring, either:
A. This thread will be of broad interest to home- dialup-users of
Slackware 9.1 (the outcome of which will be very useful), or else
B. I'm making some terribly simple and embarassing configuration
mistake.

--- if contacting via email, remove zees ---

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, John Gabriele dared to utter,
> or else
> B. I'm making some terribly simple and embarassing configuration
> mistake.

That's usually the way it is. :-) Just the other day I goofed while
manually editing a master.passwd file on a FreeBSD machine and put two
colons before the encrypted password, which effectively meant that user
had no password. Glad s/he didn't have sudo! :-)

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAh0VXL3KiNGOqr6ERApl0AJ0Zc8oXcgltOwksEUlk1/TH2ZPbeACeNAFF
bpeZIds/wjANOB8y3R4oEoU=
=5u9N
-----END PGP SIGNATURE-----

John Gabriele <john3gz@bestwebz.net> wrote in message news:<108du029u56qfd0@corp.supernews.com>...
> zentara wrote:
>
> > On Tue, 20 Apr 2004 16:24:45 -0400, John Gabriele <john3gz@bestwebz.net>
> > wrote:
> >
> >
> >>I'm just trying to get a simple desktop dialup setup working. I haven't set
> >>up any LAN. I'd like to be able to use ppp-on/off as a regular user, but for
> >>now I just want to get it working for root. I'm running a stock Slack 9.1
> >>install with bare.i.
> >>
> >> [snip]
> >
> > I had a similar problem getting my dialup ppp going. It was my firewall.
> > When the ppp0 gets established, the firewall needs to be restarted to
> > allow the ppp0 interface. The whole thing is usually done in the
> > /etc/ppp/ip-up script.
> >
> >
> > Do you have a firewall going? If so, stop it and see if you can connect
> > with ppp0.
> >
>
> Thanks for the reply zentara.
>
> No. I've got no /etc/rc.d/rc.firewall script, and rc.ip_forward isn't
> even executable.


**
I also had a hard time getting the modem to make a connection and
communicate. her are copies of my working ppp scripts.


# The following four files are configured to dial
# a modem in Slackware9.1. I use an external modem
# /dev/modem is a symbolic link to the actual device.
#
#-rw------- 1 root root 556 Jan 14 23:01 options
#-rw------- 1 root root 656 Jan 14 17:31 options.demand
#-rw------- 1 root root 212 Jan 14 17:31 pap-secrets
#-rw------- 1 root root 123 Jan 14 20:12 pppscript
#
#
# lrwxrwxrwx 1 root root 5 Jan 13 02:39 /dev/modem -> ttyS0
#
# execute as root to dial /usr/sbin/ppp-on
# execute as root to hangup /usr/sbin/ppp-off
#
#
#**************************

# /etc/ppp/options

# General configuration options for PPPD:
lock
defaultroute
noipdefault
modem
/dev/modem
115200
crtscts
# Uncomment the line below for more verbose error reporting:
#
# debug
#
# If you have a default route already, pppd may require the other side
# to authenticate itself, which most ISPs will not do. To work around this,
# uncomment the line below. Note that this may have negative side effects
# on system security if you allow PPP dialins. See the docs in /usr/doc/ppp*
# for more information.
#
# noauth
passive
asyncmap 0
name "wmreinemer" # your ISP username

#*******************************************
# /etc/ppp/options.demand lines 1-23/24 92%

# General configuration options for PPPD:
lock
defaultroute
noipdefault
modem
/dev/modem
115200
crtscts
# Uncomment the line below for more verbose error reporting:
#debug
# If you have a default route already, pppd may require the other side
# to authenticate itself, which most ISPs will not do. To work around this,
# uncomment the line below. Note that this may have negative side effects
# on system security if you allow PPP dialins. See the docs in /usr/doc/ppp*
# for more information.
#noauth
passive
asyncmap 0
name "wmreinemer" # your ISP username
ipcp-accept-local
ipcp-accept-remote
0.0.0.0:10.10.10.10
demand
connect "/usr/sbin/chat -v -f /etc/ppp/pppscript"

#***********************************

# /etc/ppp/pap-secrets

# PAP authentication file: /etc/ppp/pap-secrets
# This file should have a permission of 600.
# ~# chmod 600 /etc/ppp/pap-secrets
# Username Server Password IP addresses
"wmreinemer" * "actual password"

#************************************

# /etc/ppp/pppscript

TIMEOUT 60
ABORT ERROR
ABORT BUSY
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
"" "AT&FH0"
OK "atdt8631945" # ISP's phone number
TIMEOUT 75
CONNECT

Walt R.

Walt R wrote:
>
> **
> I also had a hard time getting the modem to make a connection and
> communicate.

Hmm... For such a common thing, I'm really surprised that
this doesn't work right out of the box (that is; run netconfig,
run pppsetup, and boom -- you're on the net). Thanks for sharing
Walt.

> her are copies of my working ppp scripts.
>
>
> # The following four files are configured to dial
> # a modem in Slackware9.1. I use an external modem
> # /dev/modem is a symbolic link to the actual device.
> #
> #-rw------- 1 root root 556 Jan 14 23:01 options
> #-rw------- 1 root root 656 Jan 14 17:31 options.demand
> #-rw------- 1 root root 212 Jan 14 17:31 pap-secrets
> #-rw------- 1 root root 123 Jan 14 20:12 pppscript
> #

Check -- permissions are correct.

> #
> # lrwxrwxrwx 1 root root 5 Jan 13 02:39 /dev/modem -> ttyS0
> #

Check. Though, as for ttyS0
crw-rw---- 1 root uucp 4, 64 Apr 21 23:38 /dev/ttyS0


> # execute as root to dial /usr/sbin/ppp-on
> # execute as root to hangup /usr/sbin/ppp-off
> #
> #
> #**************************
>
> # /etc/ppp/options
>
> # General configuration options for PPPD:
> lock
> defaultroute
> noipdefault
> modem
> /dev/modem
> 115200
> crtscts
> # Uncomment the line below for more verbose error reporting:
> #
> # debug
> #
> # If you have a default route already, pppd may require the other side
> # to authenticate itself, which most ISPs will not do. To work around this,
> # uncomment the line below. Note that this may have negative side effects
> # on system security if you allow PPP dialins. See the docs in /usr/doc/ppp*
> # for more information.
> #
> # noauth
> passive
> asyncmap 0
> name "wmreinemer" # your ISP username

Check. Though, my ISP requires me to use "foo@isp.net" rather than
just "foo".

>
> #*******************************************
> # /etc/ppp/options.demand lines 1-23/24 92%
>

Wait. Which one of these gets used when I run ppp-go? options or
options.default?

> # General configuration options for PPPD:
> lock
> defaultroute
> noipdefault
> modem
> /dev/modem
> 115200
> crtscts
> # Uncomment the line below for more verbose error reporting:
> #debug
> # If you have a default route already, pppd may require the other side
> # to authenticate itself, which most ISPs will not do. To work around this,
> # uncomment the line below. Note that this may have negative side effects
> # on system security if you allow PPP dialins. See the docs in /usr/doc/ppp*
> # for more information.
> #noauth
> passive
> asyncmap 0
> name "wmreinemer" # your ISP username
> ipcp-accept-local
> ipcp-accept-remote
> 0.0.0.0:10.10.10.10
> demand
> connect "/usr/sbin/chat -v -f /etc/ppp/pppscript"
>

Check.

> #***********************************
>
> # /etc/ppp/pap-secrets
>
> # PAP authentication file: /etc/ppp/pap-secrets
> # This file should have a permission of 600.
> # ~# chmod 600 /etc/ppp/pap-secrets
> # Username Server Password IP addresses
> "wmreinemer" * "actual password"
>

Check. Though, again, I've got the foo@isp.net instead of just foo.
I think the reason for this is, my isp uses some 3rd-party services
(Aleron and Megapop) to handle the actual dialup server, but then
once you're authenticated, you get connected to the isp's network.

> #************************************
>
> # /etc/ppp/pppscript
>
> TIMEOUT 60
> ABORT ERROR
> ABORT BUSY
> ABORT "NO CARRIER"
> ABORT "NO DIALTONE"
> "" "AT&FH0"
> OK "atdt8631945" # ISP's phone number
> TIMEOUT 75
> CONNECT

Yup. The same.

>
> Walt R.

Walt, when you're connected, could you please run 'lsmod | grep ppp'
and show me the output? If you're using the default Slack 9.1 setup
(like me), you're using hotplug too. Once connected, lsmod tells me:

ppp_async xxx 1 (autoclean)
ppp_generic xxx 3 (autoclean) [ppp_async]
slhc xxx 0 (autoclean) [ppp_generic]

Thanks,
---J

John Gabriele <john3gz@bestwebz.net> wrote in message news:<108fm2c2kv64mde@corp.supernews.com>...
> Walt R wrote:
> >
> > **
> > I also had a hard time getting the modem to make a connection and
> > communicate.
>
> Hmm... For such a common thing, I'm really surprised that
> this doesn't work right out of the box (that is; run netconfig,
> run pppsetup, and boom -- you're on the net). Thanks for sharing
> Walt.
>
> > her are copies of my working ppp scripts.
> >
> >
> > # The following four files are configured to dial
> > # a modem in Slackware9.1. I use an external modem
> > # /dev/modem is a symbolic link to the actual device.
> > #
> > #-rw------- 1 root root 556 Jan 14 23:01 options
> > #-rw------- 1 root root 656 Jan 14 17:31 options.demand
> > #-rw------- 1 root root 212 Jan 14 17:31 pap-secrets
> > #-rw------- 1 root root 123 Jan 14 20:12 pppscript
> > #
>
> Check -- permissions are correct.
>
> > #
> > # lrwxrwxrwx 1 root root 5 Jan 13 02:39 /dev/modem -> ttyS0
> > #
>
> Check. Though, as for ttyS0
> crw-rw---- 1 root uucp 4, 64 Apr 21 23:38 /dev/ttyS0
>
>
> > # execute as root to dial /usr/sbin/ppp-on
> > # execute as root to hangup /usr/sbin/ppp-off
> > #
> > #
> > #**************************
> >
> > # /etc/ppp/options
> >
> > # General configuration options for PPPD:
> > lock
> > defaultroute
> > noipdefault
> > modem
> > /dev/modem
> > 115200
> > crtscts
> > # Uncomment the line below for more verbose error reporting:
> > #
> > # debug
> > #
> > # If you have a default route already, pppd may require the other side
> > # to authenticate itself, which most ISPs will not do. To work around this,
> > # uncomment the line below. Note that this may have negative side effects
> > # on system security if you allow PPP dialins. See the docs in /usr/doc/ppp*
> > # for more information.
> > #
> > # noauth
> > passive
> > asyncmap 0
> > name "wmreinemer" # your ISP username
>
> Check. Though, my ISP requires me to use "foo@isp.net" rather than
> just "foo".
>
> >
> > #*******************************************
> > # /etc/ppp/options.demand lines 1-23/24 92%
> >
>
> Wait. Which one of these gets used when I run ppp-go? options or
> options.default?
>
> > # General configuration options for PPPD:
> > lock
> > defaultroute
> > noipdefault
> > modem
> > /dev/modem
> > 115200
> > crtscts
> > # Uncomment the line below for more verbose error reporting:
> > #debug
> > # If you have a default route already, pppd may require the other side
> > # to authenticate itself, which most ISPs will not do. To work around this,
> > # uncomment the line below. Note that this may have negative side effects
> > # on system security if you allow PPP dialins. See the docs in /usr/doc/ppp*
> > # for more information.
> > #noauth
> > passive
> > asyncmap 0
> > name "wmreinemer" # your ISP username
> > ipcp-accept-local
> > ipcp-accept-remote
> > 0.0.0.0:10.10.10.10
> > demand
> > connect "/usr/sbin/chat -v -f /etc/ppp/pppscript"
> >
>
> Check.
>
> > #***********************************
> >
> > # /etc/ppp/pap-secrets
> >
> > # PAP authentication file: /etc/ppp/pap-secrets
> > # This file should have a permission of 600.
> > # ~# chmod 600 /etc/ppp/pap-secrets
> > # Username Server Password IP addresses
> > "wmreinemer" * "actual password"
> >
>
> Check. Though, again, I've got the foo@isp.net instead of just foo.
> I think the reason for this is, my isp uses some 3rd-party services
> (Aleron and Megapop) to handle the actual dialup server, but then
> once you're authenticated, you get connected to the isp's network.
>
> > #************************************
> >
> > # /etc/ppp/pppscript
> >
> > TIMEOUT 60
> > ABORT ERROR
> > ABORT BUSY
> > ABORT "NO CARRIER"
> > ABORT "NO DIALTONE"
> > "" "AT&FH0"
> > OK "atdt8631945" # ISP's phone number
> > TIMEOUT 75
> > CONNECT
>
> Yup. The same.
>
> >
> > Walt R.
>
> Walt, when you're connected, could you please run 'lsmod | grep ppp'
> and show me the output? If you're using the default Slack 9.1 setup
> (like me), you're using hotplug too. Once connected, lsmod tells me:
>
> ppp_async xxx 1 (autoclean)
> ppp_generic xxx 3 (autoclean) [ppp_async]
> slhc xxx 0 (autoclean) [ppp_generic]
>
> Thanks,
> ---J

Here it is. I have not looked at the difference between options and
options.demand. I am running the stock adaptec 2.4.22 kernel.


wmr@wmr_srv01:~ $ lsmod|grep ppp
ppp_deflate 3288 0 (autoclean)
zlib_deflate 18200 0 (autoclean) [ppp_deflate]
ppp_async 7552 1 (autoclean)
ppp_generic 15452 3 (autoclean) [ppp_deflate bsd_comp
ppp_async]
slhc 5040 1 (autoclean) [ppp_generic]

I compiled these files for support@tns.net. All they had
was config for kde on DedRat.

Walt R.

Walt R wrote:
> John Gabriele <john3gz@bestwebz.net> wrote
>> [snip]
>>Walt, when you're connected, could you please run 'lsmod | grep ppp'
>>and show me the output? If you're using the default Slack 9.1 setup
>>(like me), you're using hotplug too. Once connected, lsmod tells me:
>>
>> ppp_async xxx 1 (autoclean)
>> ppp_generic xxx 3 (autoclean) [ppp_async]
>> slhc xxx 0 (autoclean) [ppp_generic]
>>
>>Thanks,
>>---J
>
>
> Here it is. I have not looked at the difference between options and
> options.demand. I am running the stock adaptec 2.4.22 kernel.
>
>
> wmr@wmr_srv01:~ $ lsmod|grep ppp
> ppp_deflate 3288 0 (autoclean)
> zlib_deflate 18200 0 (autoclean) [ppp_deflate]
> ppp_async 7552 1 (autoclean)
> ppp_generic 15452 3 (autoclean) [ppp_deflate bsd_comp ppp_async]
> slhc 5040 1 (autoclean) [ppp_generic]
>
> I compiled these files for support@tns.net. All they had
> was config for kde on DedRat.
>
> Walt R.

Thanks Walt. Looks pretty much the same. ppp_deflate possibly
gets loaded after successful connection (though I'll look into
it anyway).

---J