Slackware Dialup Issues - Slackware

This is a discussion on Slackware Dialup Issues - Slackware ; The modem and config files that dialup and authenticate PAP on Slackware 10.2 w/ 2.4.31 can dialup but not authenticate PAP on Slackware 12.2 w/ 2.6.21.5 kernel. This has been driving me nutz for a while. Am I missing something ...

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 20 of 21

Thread: Slackware Dialup Issues

  1. Slackware Dialup Issues


    The modem and config files that dialup and authenticate PAP on
    Slackware 10.2 w/ 2.4.31 can dialup but not authenticate PAP on
    Slackware 12.2 w/ 2.6.21.5 kernel. This has been driving me nutz for
    a while. Am I missing something in this 2.6 kernel? Any ideas
    outside of getting DSL or cable?

    Thanks, Walt R.


  2. Re: Slackware Dialup Issues

    wmreinemer@tns.net wrote:
    > The modem and config files that dialup and authenticate PAP on
    > Slackware 10.2 w/ 2.4.31 can dialup but not authenticate PAP on
    > Slackware 12.2 w/ 2.6.21.5 kernel. This has been driving me nutz for
    > a while. Am I missing something in this 2.6 kernel? Any ideas
    > outside of getting DSL or cable?
    >
    >


    Are you sure it's an authentication problem? What (exactly!) do the log
    files say?

    Oh, and is the ppp module loaded?

  3. Re: Slackware Dialup Issues

    On Oct 11, 10:16 pm, Chris Sorenson wrote:
    > wmreine...@tns.net wrote:
    > > The modem and config files that dialup and authenticate PAP on
    > > Slackware 10.2 w/ 2.4.31 can dialup but not authenticate PAP on
    > > Slackware 12.2 w/ 2.6.21.5 kernel. This has been driving me nutz for
    > > a while. Am I missing something in this 2.6 kernel? Any ideas
    > > outside of getting DSL or cable?

    >
    > Are you sure it's an authentication problem? What (exactly!) do the log
    > files say?
    >
    > Oh, and is the ppp module loaded?


    I would say that authentication failed The loaded ppp modules are
    listed below.
    root@wmr02:~
    # ppp-go
    root@wmr02:~
    # Serial connection established.
    using channel 1
    Using interface ppp0
    Connect: ppp0 <--> /dev/ttyS0
    sent [LCP ConfReq id=0x1
    ]
    rcvd [LCP ConfReq id=0x1 < 00 04 00 00>

    ]
    sent [LCP ConfRej id=0x1 < 00 04 00 00> ]
    rcvd [LCP ConfAck id=0x1
    ]
    rcvd [LCP ConfReq id=0x2
    p> ]
    sent [LCP ConfAck id=0x2
    p> ]
    sent [PAP AuthReq id=0x1 user="wmreinemer" password=]
    rcvd [PAP AuthNak id=0x1 ""]
    PAP authentication failed
    sent [LCP TermReq id=0x2 "Failed to authenticate ourselves to peer"]
    rcvd [LCP TermAck id=0x2]
    Connection terminated.

    Loaded ppp modules
    ppp_async 13056 0
    crc_ccitt 5888 1 ppp_async
    ppp_generic 26772 1 ppp_async

    Had to find a floppy the usb harddrive is no longer recognized on
    10.2.

    Thanks for any help you can give me. Walt R.


  4. Re: Slackware Dialup Issues

    wmreinemer@tns.net wrote:
    > sent [PAP AuthReq id=0x1 user="wmreinemer" password=]
    > rcvd [PAP AuthNak id=0x1 ""]
    > PAP authentication failed


    Everything looks good up to there, but that's terrible because
    ConfNak is supposed to tell you which option was bad, but there's
    nothing inside the quotes! Hmmm... Maybe that means your password is
    wrong in the pap-secrets file...

    What I would try is to run Slackware's pppsetup again, what's there to
    lose, your current setup is horked...

    >
    > Had to find a floppy the usb harddrive is no longer recognized on
    > 10.2.
    >


    Probably just need to load up a few more USB modules. That's the beauty
    of using the distribution kernel. Module module who's got the module...

  5. Re: Slackware Dialup Issues

    On Oct 12, 11:12 pm, Chris Sorenson wrote:
    > wmreine...@tns.net wrote:
    > > sent [PAP AuthReq id=0x1 user="wmreinemer" password=]
    > > rcvd [PAP AuthNak id=0x1 ""]
    > > PAP authentication failed

    >
    > Everything looks good up to there, but that's terrible because
    > ConfNak is supposed to tell you which option was bad, but there's
    > nothing inside the quotes! Hmmm... Maybe that means your password is
    > wrong in the pap-secrets file...
    >
    > What I would try is to run Slackware's pppsetup again, what's there to
    > lose, your current setup is horked...
    >
    >
    >
    > > Had to find a floppy the usb harddrive is no longer recognized on
    > > 10.2.

    >
    > Probably just need to load up a few more USB modules. That's the beauty
    > of using the distribution kernel. Module module who's got the module...

    #
    Username and password are correct.. There is nothing between the
    quotes when 10.2 authenticates PAP.
    [LCP ConfAck id=0x2
    ]
    sent [PAP AuthReq id=0x1 user="wmreinemer" password=]
    rcvd [PAP AuthAck id=0x1 ""]
    PAP authentication succeeded

    The same config files and modem connect and authenticate on 10.2, but
    NOT on 12.0
    Is this 2.6.*.* kernel missing something, or is this pppd hosed?

    Restarted the rc.hotplug script, to recognize the USB-HD.

    I have no idea how many times I have run pppsetup on this box.
    pppsetup comes up with the same config files that are on the 10.2 box.

    pppsetup, one more time :-)

    Thanks anyway - Walt R.


  6. Re: Slackware Dialup Issues

    wmreinemer@tns.net wrote:

    >
    > pppsetup, one more time :-)
    >
    >


    Another thing you could try is installing the 10.2 ppp package on your
    12.0 box, that might work (provided there are no library conflicts)...

  7. Re: Slackware Dialup Issues

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

    On Sun, 14 Oct 2007, wmreinemer@tns.net wrote:

    > The same config files and modem connect and authenticate on 10.2, but
    > NOT on 12.0
    > Is this 2.6.*.* kernel missing something, or is this pppd hosed?
    >
    > Restarted the rc.hotplug script, to recognize the USB-HD.


    not using udev ?


    - --
    Cheers
    Res

    PGP - Just another way to assist preventing Roger Maynards impersonations,
    even though at times he is funny as with his denials.

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.7 (GNU/Linux)

    iD8DBQFHEvd6sWhAmSIQh7MRAuRLAKCdGDDH8IjpEjLvkTtcIW rPAucdagCeP6OJ
    0uCu7a/YdNb2hV685viwzwk=
    =TXNj
    -----END PGP SIGNATURE-----

  8. Re: Slackware Dialup Issues

    On Oct 14, 10:15 pm, Res wrote:
    > -----BEGIN PGP SIGNED MESSAGE-----
    > Hash: SHA1
    >
    > On Sun, 14 Oct 2007, wmreine...@tns.net wrote:
    > > The same config files and modem connect and authenticate on 10.2, but
    > > NOT on 12.0
    > > Is this 2.6.*.* kernel missing something, or is this pppd hosed?

    >
    > > Restarted the rc.hotplug script, to recognize the USB-HD.

    >
    > not using udev ?
    >
    > - --
    > Cheers
    > Res
    >
    > PGP - Just another way to assist preventing Roger Maynards impersonations,
    > even though at times he is funny as with his denials.
    >
    > -----BEGIN PGP SIGNATURE-----
    > Version: GnuPG v1.4.7 (GNU/Linux)
    >
    > iD8DBQFHEvd6sWhAmSIQh7MRAuRLAKCdGDDH8IjpEjLvkTtcIW rPAucdagCeP6OJ
    > 0uCu7a/YdNb2hV685viwzwk=
    > =TXNj
    > -----END PGP SIGNATURE-----


    Ran pppsetup again with the same results, System can dialup, yet ppp
    will not authenticate PAP on 12.0.

    I have not messed with udev.

    I guess Slackware 12.0 is broke.

    Thanks anyway - Walt R.


  9. Re: Slackware Dialup Issues

    wmreinemer@tns.net says:
    >On Oct 14, 10:15 pm, Res wrote:


    [deletia]

    >Ran pppsetup again with the same results, System can dialup, yet ppp
    >will not authenticate PAP on 12.0.


    >I have not messed with udev. I guess Slackware 12.0 is broke.


    >Thanks anyway - Walt R.


    You realize that you are talking to the Res forger? Put him in your
    killfile and move on.

    cordially, as always,

    rm
    --
    http://sports.jrank.org/pages/4065/R...lishments.html

  10. Re: Slackware Dialup Issues

    (wmreinemer@tns.net) writes:
    > On Oct 14, 10:15 pm, Res wrote:
    >> -----BEGIN PGP SIGNED MESSAGE-----
    >> Hash: SHA1
    >>
    >> On Sun, 14 Oct 2007, wmreine...@tns.net wrote:
    >> > The same config files and modem connect and authenticate on 10.2, but
    >> > NOT on 12.0
    >> > Is this 2.6.*.* kernel missing something, or is this pppd hosed?

    >>
    >> > Restarted the rc.hotplug script, to recognize the USB-HD.

    >>
    >> not using udev ?
    >>
    >> - --
    >> Cheers
    >> Res
    >>
    >> PGP - Just another way to assist preventing Roger Maynards impersonations,
    >> even though at times he is funny as with his denials.
    >>
    >> -----BEGIN PGP SIGNATURE-----
    >> Version: GnuPG v1.4.7 (GNU/Linux)
    >>
    >> iD8DBQFHEvd6sWhAmSIQh7MRAuRLAKCdGDDH8IjpEjLvkTtcIW rPAucdagCeP6OJ
    >> 0uCu7a/YdNb2hV685viwzwk=
    >> =TXNj
    >> -----END PGP SIGNATURE-----

    >
    > Ran pppsetup again with the same results, System can dialup, yet ppp
    > will not authenticate PAP on 12.0.
    >
    > I have not messed with udev.
    >
    > I guess Slackware 12.0 is broke.
    >

    If you still have the old install, compare the files that get constructed
    from pppsetup.

    For the six years I've been running Linux (and that would specifically
    be Slackware), I used information and a script from my previous ISP.
    I just kept moving it, and when I changed ISPs a few years ago, just
    changed the pertinent information by hand edit.

    Last week, I decided to go "legit" and try pppsetup. The file
    it issued for pppscript did not work. It would dial okay, but fail
    when trying to authenticate.

    I still haven't figured out exactly what went wrong, but when I
    changed the "AT" command to the modem before the dialing, it started
    working.

    I suspect you won't be so lucky, but I felt this was odd enough
    that it seems a potential help given the way things seem to
    be going.

    This is Slack 10. Having done that with success, I booted
    to Slack 12 (that I haven't yet swithced over to) and ran pppsetup.
    I didn't write down if I had to hand edit something or not, but
    I was able to use the proper script to dial with.

    Michael


  11. Re: Slackware Dialup Issues

    Michael Black says:

    >This is Slack 10. Having done that with success, I booted
    >to Slack 12 (that I haven't yet swithced over to) and ran pppsetup.
    >I didn't write down if I had to hand edit something or not, but
    >I was able to use the proper script to dial with.


    When we used dialup, about 20 years ago, it seems, we found the kde
    dialer to be pretty robust and it worked where pppsetup failed.

    cordially, as always,

    rm

  12. Re: Slackware Dialup Issues

    On Oct 17, 9:09 pm, et...@FreeNet.Carleton.CA (Michael Black) wrote:
    > (wmreine...@tns.net) writes:
    > > On Oct 14, 10:15 pm, Res wrote:
    > >> -----BEGIN PGP SIGNED MESSAGE-----
    > >> Hash: SHA1

    >
    > >> On Sun, 14 Oct 2007, wmreine...@tns.net wrote:
    > >> > The same config files and modem connect and authenticate on 10.2, but
    > >> > NOT on 12.0
    > >> > Is this 2.6.*.* kernel missing something, or is this pppd hosed?

    >
    > >> > Restarted the rc.hotplug script, to recognize the USB-HD.

    >
    > >> not using udev ?

    >
    > >> - --
    > >> Cheers
    > >> Res

    >
    > >> PGP - Just another way to assist preventing Roger Maynards impersonations,
    > >> even though at times he is funny as with his denials.

    >
    > >> -----BEGIN PGP SIGNATURE-----
    > >> Version: GnuPG v1.4.7 (GNU/Linux)

    >
    > >> iD8DBQFHEvd6sWhAmSIQh7MRAuRLAKCdGDDH8IjpEjLvkTtcIW rPAucdagCeP6OJ
    > >> 0uCu7a/YdNb2hV685viwzwk=
    > >> =TXNj
    > >> -----END PGP SIGNATURE-----

    >
    > > Ran pppsetup again with the same results, System can dialup, yet ppp
    > > will not authenticate PAP on 12.0.

    >
    > > I have not messed with udev.

    >
    > > I guess Slackware 12.0 is broke.

    >
    > If you still have the old install, compare the files that get constructed
    > from pppsetup.
    >
    > For the six years I've been running Linux (and that would specifically
    > be Slackware), I used information and a script from my previous ISP.
    > I just kept moving it, and when I changed ISPs a few years ago, just
    > changed the pertinent information by hand edit.
    >
    > Last week, I decided to go "legit" and try pppsetup. The file
    > it issued for pppscript did not work. It would dial okay, but fail
    > when trying to authenticate.
    >
    > I still haven't figured out exactly what went wrong, but when I
    > changed the "AT" command to the modem before the dialing, it started
    > working.
    >
    > I suspect you won't be so lucky, but I felt this was odd enough
    > that it seems a potential help given the way things seem to
    > be going.
    >
    > This is Slack 10. Having done that with success, I booted
    > to Slack 12 (that I haven't yet swithced over to) and ran pppsetup.
    > I didn't write down if I had to hand edit something or not, but
    > I was able to use the proper script to dial with.
    >
    > Michael

    #
    What killfile??
    there were some dialup issues upgrading from dedrat7.2 to Slackware
    9.0,
    but upgrading to 10.2 was not a problem. The upgrade to 12.0 broke,
    so I did a complete reinstall. I am not going to upgrade the 10.2 box
    until
    I can dialup and authenticate on the 12.0 box.

    The external modem and config files that dialup and authenticate PAP
    on 10.2 can dial up, yet it refuses to authenticate on the 12.0 box.

    I am sick and tired of fighting this. What am I missing, or is 12.0
    missing
    something?

    I still think 12.0 is broke!!!!!!

    Thanks - Walt R.
    #


  13. Re: Slackware Dialup Issues

    wmreinemer@tns.net wrote:
    >
    > there were some dialup issues upgrading from dedrat7.2 to Slackware
    > 9.0,
    > but upgrading to 10.2 was not a problem. The upgrade to 12.0 broke,
    > so I did a complete reinstall. I am not going to upgrade the 10.2 box
    > until
    > I can dialup and authenticate on the 12.0 box.
    >
    > The external modem and config files that dialup and authenticate PAP
    > on 10.2 can dial up, yet it refuses to authenticate on the 12.0 box.
    >
    > I am sick and tired of fighting this. What am I missing, or is 12.0
    > missing
    > something?
    >
    > I still think 12.0 is broke!!!!!!
    >


    I stand by my earlier suggestion of trying the 10.2 ppp package on
    12.0. Just use 'removepkg' to remove the 12.0 version, and 'installpkg'
    to install the 10.2 version. It will probably work, I'm still using
    binaries I compiled with Slackware 8.0 and they work fine.

    If it doesn't work, you'll know the problem is somewhere in 12.0 that's
    *not* in the ppp package. If it does work, you'll know the problem *is*
    in the 12.0 ppp package. Except of course if the 10.2 package has
    library issues with 12.0, which would be very tiresome. But like you
    said, you're already tired, so there's no downside!

  14. Re: Slackware Dialup Issues

    (wmreinemer@tns.net) writes:

    > I still think 12.0 is broke!!!!!!
    >


    It's not.

    Put "debug" (without the quotes) in /etc/ppp/options and see if
    that provides any clues. It will issue a lot of messages, to
    the screen and to the log files, and that may help narrow down
    the problem.

    Again, compare the files generated by pppsetup between the versions
    of Slackware,
    /etc/ppp/options
    /ppp/pap-secrets
    /etc/ppp/pppscript
    and maybe even
    /usr/sbin/ppp-off

    If one works, and not the other, then I suspect something is misconfigured.

    ppp-go calls pppd, using pppscript for the information about dialing. pppd
    then uses the information in options to set up the ppp connection over
    the phone line.

    It's a two part thing, and one isn't really related to the other. You
    could theoretically dial by hand (or use a terminal program like
    many of the books suggest), and then start up pppd to start the ppp
    connection. It sure sounds like the dialing is going fine, but then
    the negotiation for the ppp connection is failing. That should help
    to narrow down the issue. It's not magic, but it will remain as
    such until there is understanding.

    Michael


  15. Re: Slackware Dialup Issues

    On Oct 20, 9:22 am, et...@FreeNet.Carleton.CA (Michael Black) wrote:
    > (wmreine...@tns.net) writes:
    > > I still think 12.0 is broke!!!!!!

    >
    > It's not.
    >
    > Put "debug" (without the quotes) in /etc/ppp/options and see if
    > that provides any clues. It will issue a lot of messages, to
    > the screen and to the log files, and that may help narrow down
    > the problem.
    >
    > Again, compare the files generated by pppsetup between the versions
    > of Slackware,
    > /etc/ppp/options
    > /ppp/pap-secrets
    > /etc/ppp/pppscript
    > and maybe even
    > /usr/sbin/ppp-off
    >
    > If one works, and not the other, then I suspect something is misconfigured.
    >
    > ppp-go calls pppd, using pppscript for the information about dialing. pppd
    > then uses the information in options to set up the ppp connection over
    > the phone line.
    >
    > It's a two part thing, and one isn't really related to the other. You
    > could theoretically dial by hand (or use a terminal program like
    > many of the books suggest), and then start up pppd to start the ppp
    > connection. It sure sounds like the dialing is going fine, but then
    > the negotiation for the ppp connection is failing. That should help
    > to narrow down the issue. It's not magic, but it will remain as
    > such until there is understanding.
    >
    > Michael


    #
    For the eleventy-second time. PPP will not authenticate PAP, if you
    have followed this thread I posted the debug from ppp.

    I removed the ppp package from 12.0 and installed the ppp package
    from 10.2. PPP will not authenticate PAP using the config files from
    the
    10.2 box ar any number of results from pppsetup. It seems to me
    there
    is something missing from the 12.0 kernel, or the 12.0 kernel is
    broke.

    PPP debug again!!!!!!

    root@wmr02:~
    # Serial connection established.
    using channel 1
    Using interface ppp0
    Connect: ppp0 <--> /dev/ttyS0
    sent [LCP ConfReq id=0x1
    ]
    rcvd [LCP ConfReq id=0x1 < 00 04 00 00>

    ]
    sent [LCP ConfRej id=0x1 < 00 04 00 00> ]
    rcvd [LCP ConfAck id=0x1
    ]
    rcvd [LCP ConfReq id=0x2
    p> ]
    sent [LCP ConfAck id=0x2
    p> ]
    sent [PAP AuthReq id=0x1 user="wmreinemer" password=]
    rcvd [PAP AuthNak id=0x1 ""]
    PAP authentication failed
    sent [LCP TermReq id=0x2 "Failed to authenticate ourselves to peer"]
    rcvd [LCP TermAck id=0x2]
    Connection terminated.


    Thanks - Walt R.
    #


  16. Re: Slackware Dialup Issues

    On Oct 23, 2:02 pm, wmreine...@tns.net wrote:
    > On Oct 20, 9:22 am, et...@FreeNet.Carleton.CA (Michael Black) wrote:
    >
    >
    >
    > > (wmreine...@tns.net) writes:
    > > > I still think 12.0 is broke!!!!!!

    >
    > > It's not.

    >
    > > Put "debug" (without the quotes) in /etc/ppp/options and see if
    > > that provides any clues. It will issue a lot of messages, to
    > > the screen and to the log files, and that may help narrow down
    > > the problem.

    >
    > > Again, compare the files generated by pppsetup between the versions
    > > of Slackware,
    > > /etc/ppp/options
    > > /ppp/pap-secrets
    > > /etc/ppp/pppscript
    > > and maybe even
    > > /usr/sbin/ppp-off

    >
    > > If one works, and not the other, then I suspect something is misconfigured.

    >
    > > ppp-go calls pppd, using pppscript for the information about dialing. pppd
    > > then uses the information in options to set up the ppp connection over
    > > the phone line.

    >
    > > It's a two part thing, and one isn't really related to the other. You
    > > could theoretically dial by hand (or use a terminal program like
    > > many of the books suggest), and then start up pppd to start the ppp
    > > connection. It sure sounds like the dialing is going fine, but then
    > > the negotiation for the ppp connection is failing. That should help
    > > to narrow down the issue. It's not magic, but it will remain as
    > > such until there is understanding.

    >
    > > Michael

    >
    > #
    > For the eleventy-second time. PPP will not authenticate PAP, if you
    > have followed this thread I posted the debug from ppp.
    >
    > I removed the ppp package from 12.0 and installed the ppp package
    > from 10.2. PPP will not authenticate PAP using the config files from
    > the
    > 10.2 box ar any number of results from pppsetup. It seems to me
    > there
    > is something missing from the 12.0 kernel, or the 12.0 kernel is
    > broke.
    >
    > PPP debug again!!!!!!
    >
    > root@wmr02:~
    > # Serial connection established.
    > using channel 1
    > Using interface ppp0
    > Connect: ppp0 <--> /dev/ttyS0
    > sent [LCP ConfReq id=0x1
    > ]
    > rcvd [LCP ConfReq id=0x1 < 00 04 00 00>
    >
    > ]
    > sent [LCP ConfRej id=0x1 < 00 04 00 00> ]
    > rcvd [LCP ConfAck id=0x1
    > ]
    > rcvd [LCP ConfReq id=0x2
    > > p> ]
    > sent [LCP ConfAck id=0x2
    > > p> ]
    > sent [PAP AuthReq id=0x1 user="wmreinemer" password=]
    > rcvd [PAP AuthNak id=0x1 ""]
    > PAP authentication failed
    > sent [LCP TermReq id=0x2 "Failed to authenticate ourselves to peer"]
    > rcvd [LCP TermAck id=0x2]
    > Connection terminated.
    >
    > Thanks - Walt R.
    > #

    #
    After trying to dialup with kppp I found that /dev/ppp0 did not
    exist.
    The slack12.0 system will dialup and authenticate PAP, if I write a
    symbolic link from /dev/ppp0 to /dev/ppp.

    I have tried several udev rules to accomplish this, but I have had
    to invoke mknod a couple of times due to deletion of device nodes.

    Any ideas about udev rules and ppp0?

    Thanks, Walt R.
    #

  17. Re: Slackware Dialup Issues

    On 2007-11-20, wmreinemer@tns.net wrote:
    > After trying to dialup with kppp I found that /dev/ppp0 did not
    > exist.
    > The slack12.0 system will dialup and authenticate PAP, if I write a
    > symbolic link from /dev/ppp0 to /dev/ppp.
    >
    > I have tried several udev rules to accomplish this, but I have had
    > to invoke mknod a couple of times due to deletion of device nodes.
    >
    > Any ideas about udev rules and ppp0?
    >
    > Thanks, Walt R.


    I managed to get PPP configured manually on 12.0 without too much
    trouble. I use pon and poff and /etc/ppp/options:

    Here's my /etc/ppp/options, and other files, with everything but
    uncommented lines removed:


    /etc/ppp/options

    asyncmap 0
    noauth
    defaultroute
    crtscts
    lock
    hide-password
    modem
    noipdefault
    domain workshop.net ## no idea why that's there -- or a lot of the rest :-)
    lcp-echo-interval 30
    lcp-echo-failure 4
    noipx

    /etc/ppp/peers/provider:

    noauth
    connect "/usr/sbin/chat -v -f /etc/chatscripts/provider"
    defaultroute
    /dev/ttyS0
    115200

    /etc/chatscripts/provider:


    ABORT BUSY
    ABORT "NO CARRIER"
    ABORT VOICE
    ABORT "NO DIALTONE"
    "" ATZW2
    OK ATDT3334444
    ogin "me@somwehere.net"
    word \qXXXXXXXXXX

    -------------------------------------------
    This is used by pppd according to lsof:

    0 crw-rw---- 1 root wheel 108, 0 2001-03-25 13:04 ppp

    Keep in mind that I run as root here.

    That's it besides setting up the serial card.

    Hope this helps you.

    Tom



  18. Re: Slackware Dialup Issues

    On Nov 19, 11:30 pm, Tom N wrote:
    > On 2007-11-20, wmreine...@tns.net wrote:
    >
    > > After trying to dialup with kppp I found that /dev/ppp0 did not
    > > exist.
    > > The slack12.0 system will dialup and authenticate PAP, if I write a
    > > symbolic link from /dev/ppp0 to /dev/ppp.

    >
    > > I have tried several udev rules to accomplish this, but I have had
    > > to invoke mknod a couple of times due to deletion of device nodes.

    >
    > > Any ideas about udev rules and ppp0?

    >
    > > Thanks, Walt R.

    >
    > I managed to get PPP configured manually on 12.0 without too much
    > trouble. I use pon and poff and /etc/ppp/options:
    >
    > Here's my /etc/ppp/options, and other files, with everything but
    > uncommented lines removed:
    >
    > /etc/ppp/options
    >
    > asyncmap 0
    > noauth
    > defaultroute
    > crtscts
    > lock
    > hide-password
    > modem
    > noipdefault
    > domain workshop.net ## no idea why that's there -- or a lot of the rest :-)
    > lcp-echo-interval 30
    > lcp-echo-failure 4
    > noipx
    >
    > /etc/ppp/peers/provider:
    >
    > noauth
    > connect "/usr/sbin/chat -v -f /etc/chatscripts/provider"
    > defaultroute
    > /dev/ttyS0
    > 115200
    >
    > /etc/chatscripts/provider:
    >
    > ABORT BUSY
    > ABORT "NO CARRIER"
    > ABORT VOICE
    > ABORT "NO DIALTONE"
    > "" ATZW2
    > OK ATDT3334444
    > ogin "m...@somwehere.net"
    > word \qXXXXXXXXXX
    >
    > -------------------------------------------
    > This is used by pppd according to lsof:
    >
    > 0 crw-rw---- 1 root wheel 108, 0 2001-03-25 13:04 ppp
    >
    > Keep in mind that I run as root here.
    >
    > That's it besides setting up the serial card.
    >
    > Hope this helps you.
    >
    > Tom


    Thanks tom!!

    my /dev/ppp belongs to the uucp group.

    I solved the problem by adding the following line to /etc/
    modprobe.conf file:

    alias ppp0 ppp_generic

    kppp works, but I have not had the chance to try /sbin/ppp-go

    Thanks Again, Walt R.
    #

  19. Re: Slackware Dialup Issues

    On 2007-11-20, wmreinemer@tns.net wrote:
    > On Nov 19, 11:30 pm, Tom N wrote:
    >> On 2007-11-20, wmreine...@tns.net wrote:
    >>
    >> > After trying to dialup with kppp I found that /dev/ppp0 did not
    >> > exist.
    >> > The slack12.0 system will dialup and authenticate PAP, if I write a

    >


    .....

    > Thanks tom!!


    It helped? Excellent.

    >
    > my /dev/ppp belongs to the uucp group.
    >
    > I solved the problem by adding the following line to /etc/
    > modprobe.conf file:
    >
    > alias ppp0 ppp_generic


    I wish I understood that. :-)

    >
    > kppp works, but I have not had the chance to try /sbin/ppp-go
    >
    > Thanks Again, Walt R.
    > #


    Don't you keep an xterm (or the like) up? If so, and you have the
    configuration files above (deleted) then just enter pon to start
    and poff to terminate.

    Hold on. I just looked over the pon script. You'd need to make
    this file, and the off one, either non-executable or rename
    it:

    /etc/ppp/ppp_on_boot

    Tom



  20. Re: Slackware Dialup Issues

    On Nov 20, 3:50 pm, Tom N wrote:
    > On 2007-11-20, wmreine...@tns.net wrote:
    >
    > > On Nov 19, 11:30 pm, Tom N wrote:
    > >> On 2007-11-20, wmreine...@tns.net wrote:

    >
    > >> > After trying to dialup with kppp I found that /dev/ppp0 did not
    > >> > exist.
    > >> > The slack12.0 system will dialup and authenticate PAP, if I write a

    >
    > ....
    >
    > > Thanks tom!!

    >
    > It helped? Excellent.
    >
    >
    >
    > > my /dev/ppp belongs to the uucp group.

    >
    > > I solved the problem by adding the following line to /etc/
    > > modprobe.conf file:

    >
    > > alias ppp0 ppp_generic

    >
    > I wish I understood that. :-)
    >
    >
    >
    > > kppp works, but I have not had the chance to try /sbin/ppp-go

    >
    > > Thanks Again, Walt R.
    > > #

    >
    > Don't you keep an xterm (or the like) up? If so, and you have the
    > configuration files above (deleted) then just enter pon to start
    > and poff to terminate.
    >
    > Hold on. I just looked over the pon script. You'd need to make
    > this file, and the off one, either non-executable or rename
    > it:
    >
    > /etc/ppp/ppp_on_boot
    >
    > Tom


    I got in the habit of having open terminals/shells on the Amiga.
    There are anywhere up to three or four terminals up at any
    given time.

    I rewrote /sbin/ppp-go to include a phone number selection menu.
    The dialer script is invoked from an admin menu that is brought
    up by su -c in a user shell. IF you break out of the admin menu,
    you end up in a user, not root shell.

    Why that one line in modeprobe.conf enables kppp to work, I have
    no clue.

    There seems to be some major differences between 10.2 and 12.0

    I will download your scripts and take a look at them, thanks.

    If you would like to look at my admin menu and scripts, let me know.
    At least I can access the Internet. Now I need to setup sound,
    printer,
    & etc;.

    "Damncomputer" is one word!!!

    Thanks again, Walt
    #

+ Reply to Thread
Page 1 of 2 1 2 LastLast