Can't connect to ATT dial-up - Networking

This is a discussion on Can't connect to ATT dial-up - Networking ; I have ATT DSL which also comes with dial-up access. The DSL is working but the dial-up is not and I'm trying to figure out why. There are two errors that show up in /var/log/messages: LCP: timeout sending Config-Requests CHAP ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: Can't connect to ATT dial-up

  1. Can't connect to ATT dial-up

    I have ATT DSL which also comes with dial-up access. The DSL is working
    but the dial-up is not and I'm trying to figure out why. There are two
    errors that show up in /var/log/messages:

    LCP: timeout sending Config-Requests
    CHAP authentication failed

    (see full log at bottom)

    The chap error led me to believe it was a usr/pwd problem, however, I've
    checked that in the config files and also verified that the usr/pwd does
    work (for dial-up) on another machine (using windows xp).

    I'm using "network device control" (os is fedora core 3) which uses wvdial
    and as can be seen in the log at the end of this message it is
    successfully connecting but then dropping the connection shortly
    thereafter. I used this pc & modem for a year with Earthlink dial-up with
    no problem and didn't expect to have any problem with the switch to ATT.
    I've googled extensively on the error messages & wvdial and a few other
    things and am not finding a solution to this, so perhaps someone here
    knows the answer? If nothing else, it would be very helpful to see the
    wvdial.conf from someone who is able to connect (dial-up) to
    sbcglobal.net.

    Following is some information from my config files.

    The chap-secrets file has these two lines:

    "my_username@sbcglobal.net" "ATT" "my_password"
    "my_username@sbcglobal.net" * "my_password"

    Here's wvdial.conf:

    [Modem0]
    Modem = /dev/ttyS1
    Baud = 115200
    SetVolume = 1
    Dial Command = ATDT
    Init1 = ATZ
    Init3 = ATM1L1
    FlowControl = CRTSCTS
    [Dialer ATT]
    Area Code = 330
    Username =
    Password =
    Phone = 983-0000
    Stupid Mode = 1
    Init1 = ATZ
    Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Inherits = Modem0

    Here's /var/log/messages which shows two attempts to connect:

    Jun 17 13:48:26 localhost ifup-ppp: pppd started for ATT on /dev/ttyS1 at 115200
    Jun 17 13:48:26 localhost pppd[22661]: pppd 2.4.2 started by root, uid 0
    Jun 17 13:48:27 localhost wvdial[22674]: WvDial: Internet dialer version 1.54.0
    Jun 17 13:48:27 localhost wvdial[22674]: Initializing modem.
    Jun 17 13:48:27 localhost wvdial[22674]: Sending: ATZ
    Jun 17 13:48:27 localhost wvdial[22674]: ATZ
    Jun 17 13:48:27 localhost wvdial[22674]: OK
    Jun 17 13:48:27 localhost wvdial[22674]: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Jun 17 13:48:27 localhost wvdial[22674]: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Jun 17 13:48:28 localhost wvdial[22674]: OK
    Jun 17 13:48:28 localhost wvdial[22674]: Sending: ATM0
    Jun 17 13:48:28 localhost wvdial[22674]: ATM0
    Jun 17 13:48:28 localhost wvdial[22674]: OK
    Jun 17 13:48:28 localhost wvdial[22674]: Modem initialized.
    Jun 17 13:48:28 localhost wvdial[22674]: Sending: ATDT330983-0000
    Jun 17 13:48:28 localhost wvdial[22674]: Waiting for carrier.
    Jun 17 13:48:28 localhost wvdial[22674]: ATDT330983-0000
    Jun 17 13:48:56 localhost wvdial[22674]: CONNECT 45333/V90/NONE
    Jun 17 13:48:56 localhost wvdial[22674]: Carrier detected. Chatmode finished.
    Jun 17 13:48:56 localhost pppd[22661]: Serial connection established.
    Jun 17 13:48:56 localhost pppd[22661]: Using interface ppp0
    Jun 17 13:48:56 localhost pppd[22661]: Connect: ppp0 <--> /dev/ttyS1
    Jun 17 13:49:27 localhost pppd[22661]: LCP: timeout sending Config-Requests
    Jun 17 13:49:27 localhost pppd[22661]: Connection terminated.
    Jun 17 13:49:27 localhost pppd[22661]: Hangup (SIGHUP)
    Jun 17 13:49:27 localhost pppd[22661]: Exit.

    Jun 17 13:49:57 localhost ifup-ppp: pppd started for ATT on /dev/ttyS1 at 115200
    Jun 17 13:49:57 localhost pppd[22719]: pppd 2.4.2 started by root, uid 0
    Jun 17 13:49:58 localhost wvdial[22732]: WvDial: Internet dialer version 1.54.0
    Jun 17 13:49:58 localhost wvdial[22732]: Initializing modem.
    Jun 17 13:49:58 localhost wvdial[22732]: Sending: ATZ
    Jun 17 13:49:58 localhost wvdial[22732]: ATZ
    Jun 17 13:49:58 localhost wvdial[22732]: OK
    Jun 17 13:49:58 localhost wvdial[22732]: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Jun 17 13:49:59 localhost wvdial[22732]: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Jun 17 13:49:59 localhost wvdial[22732]: OK
    Jun 17 13:49:59 localhost wvdial[22732]: Sending: ATM0
    Jun 17 13:49:59 localhost wvdial[22732]: ATM0
    Jun 17 13:49:59 localhost wvdial[22732]: OK
    Jun 17 13:49:59 localhost wvdial[22732]: Modem initialized.
    Jun 17 13:49:59 localhost wvdial[22732]: Sending: ATDT330983-0000
    Jun 17 13:49:59 localhost wvdial[22732]: Waiting for carrier.
    Jun 17 13:49:59 localhost wvdial[22732]: ATDT330983-0000
    Jun 17 13:50:28 localhost wvdial[22732]: CONNECT 45333/V90/NONE
    Jun 17 13:50:28 localhost wvdial[22732]: Carrier detected. Chatmode finished.
    Jun 17 13:50:28 localhost pppd[22719]: Serial connection established.
    Jun 17 13:50:28 localhost pppd[22719]: Using interface ppp0
    Jun 17 13:50:28 localhost pppd[22719]: Connect: ppp0 <--> /dev/ttyS1
    Jun 17 13:51:07 localhost pppd[22719]: CHAP authentication failed
    Jun 17 13:51:10 localhost pppd[22719]: Hangup (SIGHUP)
    Jun 17 13:51:10 localhost pppd[22719]: Modem hangup
    Jun 17 13:51:10 localhost pppd[22719]: Connection terminated.
    Jun 17 13:51:11 localhost pppd[22719]: Exit.






  2. Re: Can't connect to ATT dial-up

    mike wrote:
    > I have ATT DSL which also comes with dial-up access. The DSL is working
    > but the dial-up is not and I'm trying to figure out why. There are two
    > errors that show up in /var/log/messages:


    > LCP: timeout sending Config-Requests
    > CHAP authentication failed


    Curious.

    If you don't get a better response then add the line

    daemon.*;local2.* /var/log/ppp.log

    to /etc/syslog.conf, do "kill -HUP $(pidof syslogd)" to get syslogd to
    reread syslog.conf, try to connect, and then post ppp.log for comments.

    > (see full log at bottom)


    WvDial's log lacks detail.

    --
    Clifford Kite


  3. Re: Can't connect to ATT dial-up

    On Tue, 19 Jun 2007 17:59:53 -0500, Clifford Kite wrote:

    > mike wrote:
    >> I have ATT DSL which also comes with dial-up access. The DSL is working
    >> but the dial-up is not and I'm trying to figure out why. There are two
    >> errors that show up in /var/log/messages:

    >
    >> LCP: timeout sending Config-Requests
    >> CHAP authentication failed

    >
    > Curious.
    >
    > If you don't get a better response then add the line
    >
    > daemon.*;local2.* /var/log/ppp.log
    >
    > to /etc/syslog.conf, do "kill -HUP $(pidof syslogd)" to get syslogd to
    > reread syslog.conf, try to connect, and then post ppp.log for comments.
    >
    >> (see full log at bottom)

    >
    > WvDial's log lacks detail.



    /var/log/ppp.log:

    Jun 19 19:11:59 localhost ifup-ppp: pppd started for ATT on /dev/ttyS1 at 115200
    Jun 19 19:11:59 localhost pppd[32416]: pppd 2.4.2 started by root, uid 0
    Jun 19 19:12:00 localhost wvdial[32429]: WvDial: Internet dialer version 1.54.0
    Jun 19 19:12:00 localhost wvdial[32429]: Initializing modem.
    Jun 19 19:12:00 localhost wvdial[32429]: Sending: ATZ
    Jun 19 19:12:00 localhost wvdial[32429]: ATZ
    Jun 19 19:12:00 localhost wvdial[32429]: OK
    Jun 19 19:12:00 localhost wvdial[32429]: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Jun 19 19:12:00 localhost wvdial[32429]: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Jun 19 19:12:01 localhost wvdial[32429]: OK
    Jun 19 19:12:01 localhost wvdial[32429]: Sending: ATM1L1
    Jun 19 19:12:01 localhost wvdial[32429]: ATM1L1
    Jun 19 19:12:01 localhost wvdial[32429]: OK
    Jun 19 19:12:01 localhost wvdial[32429]: Modem initialized.
    Jun 19 19:12:01 localhost wvdial[32429]: Sending: ATDT330983-0000
    Jun 19 19:12:01 localhost wvdial[32429]: Waiting for carrier.
    Jun 19 19:12:01 localhost wvdial[32429]: ATDT330983-0000
    Jun 19 19:12:23 localhost wvdial[32429]: CONNECT 31200/ARQ/V34/LAPM/V42BIS
    Jun 19 19:12:23 localhost wvdial[32429]: Carrier detected. Chatmode finished.
    Jun 19 19:12:23 localhost pppd[32416]: Serial connection established.
    Jun 19 19:12:23 localhost pppd[32416]: Using interface ppp0
    Jun 19 19:12:23 localhost pppd[32416]: Connect: ppp0 <--> /dev/ttyS1
    Jun 19 19:12:23 localhost wait_for_sysfs[32431]: main: class device opened '/sys/class/net/ppp0'
    Jun 19 19:12:23 localhost wait_for_sysfs[32431]: wait_for_class_device_attributes: looking at class
    'net' for specific file '/sys/class/net/ppp0' with full name /sys/class/net/ppp0/ifindex
    Jun 19 19:12:23 localhost wait_for_sysfs[32431]: wait_for_class_device_attributes: class 'net' specific file 'ifindex' found
    Jun 19 19:12:23 localhost wait_for_sysfs[32431]: wait_for_class_device: no device symlink expected for 'ppp0',
    Jun 19 19:12:23 localhost wait_for_sysfs[32431]: main: result: waiting for sysfs successful '/class/net/ppp0'
    Jun 19 19:12:23 localhost udevsend[32432]: main: version 039
    Jun 19 19:12:23 localhost udevsend[32432]: main: subsystem = 'net'
    Jun 19 19:12:23 localhost udevsend[32432]: main: DEVPATH = '/class/net/ppp0'
    Jun 19 19:12:23 localhost udevsend[32432]: main: ACTION = 'add'
    Jun 19 19:12:23 localhost udevsend[32432]: main: SEQNUM = '343'
    Jun 19 19:12:23 localhost udevd[1222]: msg_queue_insert: queued message seq 343
    Jun 19 19:12:23 localhost udevd[1222]: msg_queue_manager: msg queue manager, next expected is 343
    Jun 19 19:12:23 localhost udevd[1222]: msg_move_exec: moved seq 343 to exec, next expected is 344
    Jun 19 19:12:23 localhost udevd[1222]: udev_run: ==> exec seq 343 [32440] working at '/class/net/ppp0'
    Jun 19 19:12:23 localhost udev[32440]: get_dirs: sysfs_path='/sys'
    Jun 19 19:12:23 localhost udevd[1222]: exec_queue_manager: moved seq 343 to running list
    Jun 19 19:12:23 localhost udev[32440]: parse_config_file: reading '/etc/udev/udev.conf' as config file
    Jun 19 19:12:23 localhost udevd[1222]: udev_done: <== exec seq 343 came back
    Jun 19 19:12:30 localhost pppd[32416]: CHAP authentication failed
    Jun 19 19:12:31 localhost pppd[32416]: Hangup (SIGHUP)
    Jun 19 19:12:31 localhost pppd[32416]: Modem hangup
    Jun 19 19:12:31 localhost pppd[32416]: Connection terminated.
    Jun 19 19:12:31 localhost wait_for_sysfs[32442]: main: no add ACTION
    Jun 19 19:12:31 localhost wait_for_sysfs[32442]: main: result: waiting for sysfs successful '/class/net/ppp0'
    Jun 19 19:12:31 localhost udevsend[32443]: main: version 039
    Jun 19 19:12:31 localhost udevsend[32443]: main: subsystem = 'net'
    Jun 19 19:12:31 localhost udevsend[32443]: main: DEVPATH = '/class/net/ppp0'
    Jun 19 19:12:31 localhost udevsend[32443]: main: ACTION = 'remove'
    Jun 19 19:12:31 localhost udevsend[32443]: main: SEQNUM = '344'
    Jun 19 19:12:31 localhost udevd[1222]: msg_queue_insert: queued message seq 344
    Jun 19 19:12:31 localhost udevd[1222]: msg_queue_manager: msg queue manager, next expected is 344
    Jun 19 19:12:31 localhost udevd[1222]: msg_move_exec: moved seq 344 to exec, next expected is 345
    Jun 19 19:12:32 localhost udevd[1222]: udev_run: ==> exec seq 344 [32451] working at '/class/net/ppp0'
    Jun 19 19:12:32 localhost udev[32451]: get_dirs: sysfs_path='/sys'
    Jun 19 19:12:32 localhost udevd[1222]: exec_queue_manager: moved seq 344 to running list
    Jun 19 19:12:32 localhost udev[32451]: parse_config_file: reading '/etc/udev/udev.conf' as config file
    Jun 19 19:12:32 localhost udevd[1222]: udev_done: <== exec seq 344 came back
    Jun 19 19:12:33 localhost pppd[32416]: Exit.




  4. Re: Can't connect to ATT dial-up

    Clifford Kite wrote:
    > mike wrote:
    >> I have ATT DSL which also comes with dial-up access. The DSL is working
    >> but the dial-up is not and I'm trying to figure out why. There are two
    >> errors that show up in /var/log/messages:


    >> LCP: timeout sending Config-Requests
    >> CHAP authentication failed


    > Curious.


    > If you don't get a better response then add the line


    > daemon.*;local2.* /var/log/ppp.log


    > to /etc/syslog.conf, do "kill -HUP $(pidof syslogd)" to get syslogd to
    > reread syslog.conf, try to connect, and then post ppp.log for comments.


    Well, Doh!! Also add the pppd "debug" option to WvDial's configuration,
    wherever appropriate.

    >> (see full log at bottom)


    > WvDial's log lacks detail.


    --
    Clifford Kite

  5. Re: Can't connect to ATT dial-up

    On Tue, 19 Jun 2007 18:48:21 -0500, Clifford Kite wrote:

    > Clifford Kite wrote:
    >> mike wrote:
    >>> I have ATT DSL which also comes with dial-up access. The DSL is working
    >>> but the dial-up is not and I'm trying to figure out why. There are two
    >>> errors that show up in /var/log/messages:

    >
    >>> LCP: timeout sending Config-Requests
    >>> CHAP authentication failed

    >
    >> Curious.

    >
    >> If you don't get a better response then add the line

    >
    >> daemon.*;local2.* /var/log/ppp.log

    >
    >> to /etc/syslog.conf, do "kill -HUP $(pidof syslogd)" to get syslogd to
    >> reread syslog.conf, try to connect, and then post ppp.log for comments.

    >
    > Well, Doh!! Also add the pppd "debug" option to WvDial's configuration,
    > wherever appropriate.
    >


    I put debug in /etc/ppp/options and the following is the result. I
    changed my username to "my_userid" in the output:

    Jun 19 22:41:22 localhost ifup-ppp: pppd started for ATT on /dev/ttyS1 at 115200
    Jun 19 22:41:22 localhost pppd[3886]: pppd 2.4.2 started by root, uid 0
    Jun 19 22:41:23 localhost wvdial[3899]: WvDial: Internet dialer version 1.54.0
    Jun 19 22:41:23 localhost wvdial[3899]: Initializing modem.
    Jun 19 22:41:23 localhost wvdial[3899]: Sending: ATZ
    Jun 19 22:41:23 localhost wvdial[3899]: ATZ
    Jun 19 22:41:23 localhost wvdial[3899]: OK
    Jun 19 22:41:23 localhost wvdial[3899]: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Jun 19 22:41:23 localhost wvdial[3899]: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    Jun 19 22:41:23 localhost wvdial[3899]: OK
    Jun 19 22:41:23 localhost wvdial[3899]: Sending: ATM1L1
    Jun 19 22:41:23 localhost wvdial[3899]: ATM1L1
    Jun 19 22:41:23 localhost wvdial[3899]: OK
    Jun 19 22:41:23 localhost wvdial[3899]: Modem initialized.
    Jun 19 22:41:23 localhost wvdial[3899]: Sending: ATDT330983-0000
    Jun 19 22:41:23 localhost wvdial[3899]: Waiting for carrier.
    Jun 19 22:41:23 localhost wvdial[3899]: ATDT330983-0000
    Jun 19 22:41:53 localhost wvdial[3899]: CONNECT 31200/ARQ/V34/LAPM/V42BIS
    Jun 19 22:41:53 localhost wvdial[3899]: Carrier detected. Chatmode finished.
    Jun 19 22:41:53 localhost pppd[3886]: Serial connection established.
    Jun 19 22:41:53 localhost pppd[3886]: using channel 15
    Jun 19 22:41:53 localhost wait_for_sysfs[3909]: main: class device opened '/sys/class/net/ppp0'
    Jun 19 22:41:53 localhost wait_for_sysfs[3909]: wait_for_class_device_attributes: looking at class 'net' for specific file '/sys/class/net/ppp0' with full name /sys/class/net/ppp0/ifindex
    Jun 19 22:41:53 localhost pppd[3886]: Using interface ppp0
    Jun 19 22:41:53 localhost pppd[3886]: Connect: ppp0 <--> /dev/ttyS1
    Jun 19 22:41:53 localhost wait_for_sysfs[3909]: wait_for_class_device_attributes: class 'net' specific file 'ifindex' found
    Jun 19 22:41:53 localhost wait_for_sysfs[3909]: wait_for_class_device: no device symlink expected for 'ppp0',
    Jun 19 22:41:53 localhost wait_for_sysfs[3909]: main: result: waiting for sysfs successful '/class/net/ppp0'
    Jun 19 22:41:53 localhost udevsend[3910]: main: version 039
    Jun 19 22:41:53 localhost udevsend[3910]: main: subsystem = 'net'
    Jun 19 22:41:53 localhost udevsend[3910]: main: DEVPATH = '/class/net/ppp0'
    Jun 19 22:41:53 localhost udevsend[3910]: main: ACTION = 'add'
    Jun 19 22:41:53 localhost udevsend[3910]: main: SEQNUM = '349'
    Jun 19 22:41:54 localhost udevd[1222]: msg_queue_insert: queued message seq 349
    Jun 19 22:41:54 localhost udevd[1222]: msg_queue_manager: msg queue manager, next expected is 349
    Jun 19 22:41:54 localhost udevd[1222]: msg_move_exec: moved seq 349 to exec, next expected is 350
    Jun 19 22:41:54 localhost udevd[1222]: udev_run: ==> exec seq 349 [3918] working at '/class/net/ppp0'
    Jun 19 22:41:54 localhost udev[3918]: get_dirs: sysfs_path='/sys'
    Jun 19 22:41:54 localhost udevd[1222]: exec_queue_manager: moved seq 349 to running list
    Jun 19 22:41:54 localhost udev[3918]: parse_config_file: reading '/etc/udev/udev.conf' as config file
    Jun 19 22:41:54 localhost udevd[1222]: udev_done: <== exec seq 349 came back
    Jun 19 22:41:54 localhost pppd[3886]: sent [LCP ConfReq id=0x1 ]
    Jun 19 22:41:55 localhost pppd[3886]: rcvd [LCP ConfReq id=0x1 ]
    Jun 19 22:41:55 localhost pppd[3886]: sent [LCP ConfRej id=0x1 ]
    Jun 19 22:41:55 localhost pppd[3886]: rcvd [LCP ConfAck id=0x1 ]
    Jun 19 22:41:55 localhost pppd[3886]: rcvd [LCP ConfReq id=0x2 ]
    Jun 19 22:41:55 localhost pppd[3886]: sent [LCP ConfAck id=0x2 ]
    Jun 19 22:41:55 localhost pppd[3886]: rcvd [CHAP Challenge id=0x3 <2890c792788f41c9dc8c6094cc7ed2e3>, name = "HiPer.att.net"]
    Jun 19 22:41:55 localhost pppd[3886]: sent [CHAP Response id=0x3 <40584dfbb748cce99acb29bca9f33cae>, name = "my_userid@sbcglobal.net"]
    Jun 19 22:41:56 localhost pppd[3886]: rcvd [CHAP Failure id=0x3 ""]
    Jun 19 22:41:56 localhost pppd[3886]: CHAP authentication failed
    Jun 19 22:41:56 localhost pppd[3886]: sent [LCP TermReq id=0x2 "Failed to authenticate ourselves to peer"]
    Jun 19 22:41:56 localhost pppd[3886]: rcvd [LCP TermReq id=0x4]
    Jun 19 22:41:56 localhost pppd[3886]: sent [LCP TermAck id=0x4]
    Jun 19 22:41:57 localhost pppd[3886]: Hangup (SIGHUP)
    Jun 19 22:41:57 localhost pppd[3886]: Modem hangup
    Jun 19 22:41:57 localhost pppd[3886]: Connection terminated.
    Jun 19 22:41:57 localhost wait_for_sysfs[3920]: main: no add ACTION
    Jun 19 22:41:57 localhost wait_for_sysfs[3920]: main: result: waiting for sysfs successful '/class/net/ppp0'
    Jun 19 22:41:57 localhost udevsend[3921]: main: version 039
    Jun 19 22:41:57 localhost udevsend[3921]: main: subsystem = 'net'
    Jun 19 22:41:57 localhost udevsend[3921]: main: DEVPATH = '/class/net/ppp0'
    Jun 19 22:41:57 localhost udevsend[3921]: main: ACTION = 'remove'
    Jun 19 22:41:57 localhost udevsend[3921]: main: SEQNUM = '350'
    Jun 19 22:41:57 localhost udevd[1222]: msg_queue_insert: queued message seq 350
    Jun 19 22:41:57 localhost udevd[1222]: msg_queue_manager: msg queue manager, next expected is 350
    Jun 19 22:41:57 localhost udevd[1222]: msg_move_exec: moved seq 350 to exec, next expected is 351
    Jun 19 22:41:57 localhost udevd[1222]: udev_run: ==> exec seq 350 [3929] working at '/class/net/ppp0'
    Jun 19 22:41:57 localhost udev[3929]: get_dirs: sysfs_path='/sys'
    Jun 19 22:41:57 localhost udevd[1222]: exec_queue_manager: moved seq 350 to running list
    Jun 19 22:41:57 localhost udev[3929]: parse_config_file: reading '/etc/udev/udev.conf' as config file
    Jun 19 22:41:57 localhost udevd[1222]: udev_done: <== exec seq 350 came back
    Jun 19 22:41:58 localhost pppd[3886]: Exit.



  6. Re: Can't connect to ATT dial-up

    In newsan.2007.06.19.19.01.30.366793@localhost.localdomai n,
    mike wrote:

    > The chap-secrets file has these two lines:
    >
    > "my_username@sbcglobal.net" "ATT" "my_password"
    > "my_username@sbcglobal.net" * "my_password"


    Remove the quotation marks from the file, given your later post detail of:

    > Jun 19 22:41:55 localhost pppd[3886]: sent [CHAP Response id=0x3
    > <40584dfbb748cce99acb29bca9f33cae>, name = "my_userid@sbcglobal.net"]
    > Jun 19 22:41:56 localhost pppd[3886]: rcvd [CHAP Failure id=0x3 ""]
    > Jun 19 22:41:56 localhost pppd[3886]: CHAP authentication failed
    > Jun 19 22:41:56 localhost pppd[3886]: sent [LCP TermReq id=0x2
    > "Failed to authenticate ourselves to peer"]



  7. Re: Can't connect to ATT dial-up

    On Tue, 19 Jun 2007 20:28:11 -0700, Patrick wrote:

    > In newsan.2007.06.19.19.01.30.366793@localhost.localdomai n,
    > mike wrote:
    >
    >> The chap-secrets file has these two lines:
    >>
    >> "my_username@sbcglobal.net" "ATT" "my_password"
    >> "my_username@sbcglobal.net" * "my_password"

    >
    > Remove the quotation marks from the file, given your later post detail of:
    >
    >> Jun 19 22:41:55 localhost pppd[3886]: sent [CHAP Response id=0x3
    >> <40584dfbb748cce99acb29bca9f33cae>, name = "my_userid@sbcglobal.net"]
    >> Jun 19 22:41:56 localhost pppd[3886]: rcvd [CHAP Failure id=0x3 ""]
    >> Jun 19 22:41:56 localhost pppd[3886]: CHAP authentication failed
    >> Jun 19 22:41:56 localhost pppd[3886]: sent [LCP TermReq id=0x2
    >> "Failed to authenticate ourselves to peer"]


    I took out the quotes and the result was the same.


  8. Re: Can't connect to ATT dial-up

    mike wrote:
    > On Tue, 19 Jun 2007 18:48:21 -0500, Clifford Kite wrote:
    >> Clifford Kite wrote:


    >>> If you don't get a better response then add the line

    >>
    >>> daemon.*;local2.* /var/log/ppp.log

    >>
    >>> to /etc/syslog.conf, do "kill -HUP $(pidof syslogd)" to get syslogd to
    >>> reread syslog.conf, try to connect, and then post ppp.log for comments.

    >>
    >> Well, Doh!! Also add the pppd "debug" option to WvDial's configuration,
    >> wherever appropriate.


    > I put debug in /etc/ppp/options and the following is the result. I
    > changed my username to "my_userid" in the output:


    > Jun 19 22:41:22 localhost ifup-ppp: pppd started for ATT on /dev/ttyS1
    > at 115200
    > Jun 19 22:41:22 localhost pppd[3886]: pppd 2.4.2 started by root, uid 0
    > Jun 19 22:41:23 localhost wvdial[3899]: WvDial: Internet dialer version
    > 1.54.0




    > Jun 19 22:41:54 localhost pppd[3886]: sent [LCP ConfReq id=0x1
    0x0> ]
    > Jun 19 22:41:55 localhost pppd[3886]: rcvd [LCP ConfReq id=0x1
    1514>
    ]
    > Jun 19 22:41:55 localhost pppd[3886]: sent [LCP ConfRej id=0x1 ]
    > Jun 19 22:41:55 localhost pppd[3886]: rcvd [LCP ConfAck id=0x1
    0x0> ]
    > Jun 19 22:41:55 localhost pppd[3886]: rcvd [LCP ConfReq id=0x2

    ]
    > Jun 19 22:41:55 localhost pppd[3886]: sent [LCP ConfAck id=0x2

    ]
    > Jun 19 22:41:55 localhost pppd[3886]: rcvd [CHAP Challenge id=0x3

    <2890c792788f41c9dc8c6094cc7ed2e3>, name = "HiPer.att.net"]
    > Jun 19 22:41:55 localhost pppd[3886]: sent [CHAP Response id=0x3

    <40584dfbb748cce99acb29bca9f33cae>, name = "my_userid@sbcglobal.net"]
    > Jun 19 22:41:56 localhost pppd[3886]: rcvd [CHAP Failure id=0x3 ""]
    > Jun 19 22:41:56 localhost pppd[3886]: CHAP authentication failed
    > Jun 19 22:41:56 localhost pppd[3886]: sent [LCP TermReq id=0x2 "Failed

    to authenticate ourselves to peer"]

    Okay, I'm convinced the authentication failure is real and now know normal
    (MD5) CHAP is requested. Some things that might cause the failure:

    1) The password or account name pppd sends is incorrect,
    2) sbcglobal.net doesn't have a PPP account set up for you,
    3) HiPer.att.net doesn't know about the account,
    4) the password in chap-secrets may need '' quotes when non-alphanumeric
    characters are present, or
    5) the chap-secrets line containing ATT may need to be commented out.

    The "LCP: timeout" appears to be a 30 second pppd timeout caused by
    there being no response to it's LCP requests. That could be caused by
    a login prompt, among other things - nothing I saw suggests anything
    definite.

    > Jun 19 22:41:56 localhost pppd[3886]: rcvd [LCP TermReq id=0x4]
    > Jun 19 22:41:56 localhost pppd[3886]: sent [LCP TermAck id=0x4]
    > Jun 19 22:41:57 localhost pppd[3886]: Hangup (SIGHUP)
    > Jun 19 22:41:57 localhost pppd[3886]: Modem hangup
    > Jun 19 22:41:57 localhost pppd[3886]: Connection terminated.
    > Jun 19 22:41:58 localhost pppd[3886]: Exit.


    --
    Clifford Kite
    /* I hear and I forget. I see and I remember. I do and I understand.
    --Confucius, 551-479 BC */

  9. Re: Can't connect to ATT dial-up

    On Wed, 20 Jun 2007 10:47:57 -0500, Clifford Kite wrote:

    > mike wrote:
    >> On Tue, 19 Jun 2007 18:48:21 -0500, Clifford Kite wrote:
    >>> Clifford Kite wrote:

    >
    >>>> If you don't get a better response then add the line
    >>>
    >>>> daemon.*;local2.* /var/log/ppp.log
    >>>
    >>>> to /etc/syslog.conf, do "kill -HUP $(pidof syslogd)" to get syslogd to
    >>>> reread syslog.conf, try to connect, and then post ppp.log for comments.
    >>>
    >>> Well, Doh!! Also add the pppd "debug" option to WvDial's configuration,
    >>> wherever appropriate.

    >
    >> I put debug in /etc/ppp/options and the following is the result. I
    >> changed my username to "my_userid" in the output:

    >
    >> Jun 19 22:41:22 localhost ifup-ppp: pppd started for ATT on /dev/ttyS1
    >> at 115200
    >> Jun 19 22:41:22 localhost pppd[3886]: pppd 2.4.2 started by root, uid 0
    >> Jun 19 22:41:23 localhost wvdial[3899]: WvDial: Internet dialer version
    >> 1.54.0

    >
    >
    >
    >> Jun 19 22:41:54 localhost pppd[3886]: sent [LCP ConfReq id=0x1
    > 0x0> ]
    >> Jun 19 22:41:55 localhost pppd[3886]: rcvd [LCP ConfReq id=0x1
    > 1514>
    > ]
    >> Jun 19 22:41:55 localhost pppd[3886]: sent [LCP ConfRej id=0x1 ]
    >> Jun 19 22:41:55 localhost pppd[3886]: rcvd [LCP ConfAck id=0x1
    > 0x0> ]
    >> Jun 19 22:41:55 localhost pppd[3886]: rcvd [LCP ConfReq id=0x2

    > ]
    >> Jun 19 22:41:55 localhost pppd[3886]: sent [LCP ConfAck id=0x2

    > ]
    >> Jun 19 22:41:55 localhost pppd[3886]: rcvd [CHAP Challenge id=0x3

    > <2890c792788f41c9dc8c6094cc7ed2e3>, name = "HiPer.att.net"]
    >> Jun 19 22:41:55 localhost pppd[3886]: sent [CHAP Response id=0x3

    > <40584dfbb748cce99acb29bca9f33cae>, name = "my_userid@sbcglobal.net"]
    >> Jun 19 22:41:56 localhost pppd[3886]: rcvd [CHAP Failure id=0x3 ""]
    >> Jun 19 22:41:56 localhost pppd[3886]: CHAP authentication failed
    >> Jun 19 22:41:56 localhost pppd[3886]: sent [LCP TermReq id=0x2 "Failed

    > to authenticate ourselves to peer"]
    >
    > Okay, I'm convinced the authentication failure is real and now know normal
    > (MD5) CHAP is requested. Some things that might cause the failure:
    >
    > 1) The password or account name pppd sends is incorrect,
    > 2) sbcglobal.net doesn't have a PPP account set up for you,
    > 3) HiPer.att.net doesn't know about the account,
    > 4) the password in chap-secrets may need '' quotes when non-alphanumeric
    > characters are present, or
    > 5) the chap-secrets line containing ATT may need to be commented out.
    >


    As I said in my initial post, the usr/pwd works for dial-up from windows
    xp so I know the PPP account is set up. I tried single-quotes in the
    chap-secrets file and also deleted the ATT line and it still doesn't work.
    I can see by the username in the logfile that it's being read correctly
    but the password is not shown in the log so can't say for sure if it's
    being read correctly.

    Well thanks for the help, I learned a new debugging technique at any rate.



    > The "LCP: timeout" appears to be a 30 second pppd timeout caused by
    > there being no response to it's LCP requests. That could be caused by
    > a login prompt, among other things - nothing I saw suggests anything
    > definite.
    >
    >> Jun 19 22:41:56 localhost pppd[3886]: rcvd [LCP TermReq id=0x4]
    >> Jun 19 22:41:56 localhost pppd[3886]: sent [LCP TermAck id=0x4]
    >> Jun 19 22:41:57 localhost pppd[3886]: Hangup (SIGHUP)
    >> Jun 19 22:41:57 localhost pppd[3886]: Modem hangup
    >> Jun 19 22:41:57 localhost pppd[3886]: Connection terminated.
    >> Jun 19 22:41:58 localhost pppd[3886]: Exit.



  10. Re: Can't connect to ATT dial-up

    mike wrote:
    > On Wed, 20 Jun 2007 10:47:57 -0500, Clifford Kite wrote:


    >> Okay, I'm convinced the authentication failure is real and now know normal
    >> (MD5) CHAP is requested. Some things that might cause the failure:
    >>
    >> 1) The password or account name pppd sends is incorrect,
    >> 2) sbcglobal.net doesn't have a PPP account set up for you,
    >> 3) HiPer.att.net doesn't know about the account,
    >> 4) the password in chap-secrets may need '' quotes when non-alphanumeric
    >> characters are present, or
    >> 5) the chap-secrets line containing ATT may need to be commented out.
    >>


    > As I said in my initial post, the usr/pwd works for dial-up from windows
    > xp so I know the PPP account is set up. I tried single-quotes in the


    Yes, sorry, I had forgotten that.

    > chap-secrets file and also deleted the ATT line and it still doesn't work.
    > I can see by the username in the logfile that it's being read correctly
    > but the password is not shown in the log so can't say for sure if it's
    > being read correctly.


    Well, something is causing authentication to fail and unless the CHAP
    challenge or response is somehow corrupted a disagreement about the
    secret (password) or the account name seems to me to be all that's left.
    The negotiations proceeded in a timely manner and nothing that was
    negotiated rang any bells.

    > Well thanks for the help, I learned a new debugging technique at any rate.


    Thanks for the introduction to udev. I think!

    --
    Clifford Kite
    /* Those who can't write, write manuals. */