Re: wvdial Ask Password fails with tcgetattr error

From: Richard (dont.spam.me_at_news.invalid)
Date: 07/10/05

  • Next message: Rick: "Re: Setting up Multiple VirtualHosts in Apache" 
    Date: Sat, 09 Jul 2005 23:56:45 GMT

    Unruh <unruh-spam@physics.ubc.ca> wrote in
    news:dap6it$jna$1@nntp.itservices.ubc.ca:

    >
    > What does your wvdial config file have in it (do not post the password
    > here).
    >
    Configuration files:
    /etc/ppp/options
            asyncmap 0
            noauth
            crtscts
            lock
            hide-password
            modem
            proxyarp
            lcp-echo-interval 30
            lcp-echo-failure 4
            noipx

    /etc/ppp/wvdial.conf
            [Dialer ppp0]
            Init2 = ATL1
            Password = ******
            Stupid mode = 0
            Init1 = AT&F1
            Phone = 421-0549
            Username = XXXXXX
            Dial Command = ATDT
            Modem = /dev/ttyS1
            Baud = 115200
            [Dialer Defaults]
            Modem = /dev/ttyS1
            Baud = 115200
            Init1 = ATZ
            Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0L3
            ISDN = 0
            Modem Type = Analog Modem

    /etc/ppp/peers/ppp0
            usepeerdns
            user XXXXXX
            /dev/ttyS1
            connect "/usr/bin/wvdial --chat ppp0"
            defaultroute
            noipdefault
            noauth

    > As I said (almost) no ISP uses login -- it really is highly unlikely.
    >
    > However wvdial can be stupid, and they realise it, so put in the
    > option Supid Mode = 1
    > Make sure you have pap/chap secrets file properly set up.
    >
    > Also remove the Login and Password or Ask Password entries.
    >
    I tried several experiments at your suggestion, and here are my
    observations:

    With Stupid Mode = 0, wvdial will authenticate via login/password before
    starting pppd.

    With Stupid Mode = 1, wvdial will start pppd immediately and (apparently)
    authenticate via pap/chap-secrets files.

    Either method connects successfully.

    Regardless of how Stupid Mode is set, wvdial gets a username and password
    from wvdial.conf (or asks for a password if Ask Password = 1), and writes
    them to the pap/chap-secrets files. If it cannot find/get both username and
    password, it exits before dialing. When I remove Username, Password and Ask
    Password from wvdial.conf, I get the following result (with Stupid Mode = 1
    or 0):

    --> WvDial: Internet dialer version 1.54.0
    --> Initializing modem.
    --> Sending: AT&F1
    AT&F1
    OK
    --> Sending: ATL1
    ATL1
    OK
    --> Modem initialized.
    --> Configuration does not specify a valid password.
    --> Configuration does not specify a valid user name.
    (exits)

    The wvdial man page does say it automatically updates pap/chap-secrets
    files, so I guess it wants a username/password pair to accomplish that.
    Don't recall seeing any way to turn that behavior off.

  • Next message: Rick: "Re: Setting up Multiple VirtualHosts in Apache"

    Relevant Pages

    • 403: Forbidden exception
      ... Is this because I need to authenticate with username and password? ... username from the config file ... System.Net.NetworkCredential credentials = new System.Net.NetworkCredential ...
      (microsoft.public.dotnet.framework)
    • Re: [SLE] Login screen gone after apt upgrade
      ... >result of this action my login screen (the graphical interface where you put the ... >username and pass when you try to load SuSE) is gone. ... It uses the config file ... God said, ...
      (SuSE)
    • Re: Nonce and Created Values. General Questions
      ... a message without the nonce detail and still got an "invalid token". ... The network is on a private, secure network. ... >> this didn't work when I added to my config file. ... If you have Username Token replay detection ...
      (microsoft.public.dotnet.framework.webservices.enhancements)
    • Server Application Unavailable
      ... aspnet_wp.exe could not be launched because the username ... and/or password supplied in the processModel section of ... the config file are invalid. ...
      (microsoft.public.inetserver.iis.security)