wvdial does not connect - PPP

This is a discussion on wvdial does not connect - PPP ; Hi, I am trying to dial to the local GPRS network here in Malaysia. My system is running on linux and I am very new to linux and pppd. After installing linux, pppd and wvdial onto my system, I face ...

+ Reply to Thread
Results 1 to 17 of 17

Thread: wvdial does not connect

  1. wvdial does not connect

    Hi,

    I am trying to dial to the local GPRS network here in Malaysia. My
    system is running on linux and I am very new to linux and pppd. After
    installing linux, pppd and wvdial onto my system, I face a weird
    situation where it can't seem to connect to the GPRS network. I've
    configure all the necessary configurations and below is the snippet
    from the debug log (/var/log/debug).

    Apr 4 15:52:49 ifs pppd[24952]: pppd 2.4.2 started by root, uid 0
    Apr 4 15:52:49 ifs pppd[24952]: using channel 32
    Apr 4 15:52:49 ifs pppd[24952]: Using interface ppp0
    Apr 4 15:52:49 ifs pppd[24952]: Connect: ppp0 <--> /dev/ttyACM0
    Apr 4 15:52:49 ifs pppd[24952]: sent [LCP ConfReq id=0x1 0x0> ]
    Apr 4 15:52:49 ifs pppd[24952]: rcvd [LCP ConfAck id=0x1 0x0> ]
    Apr 4 15:52:52 ifs pppd[24952]: sent [LCP ConfReq id=0x1 0x0> ]
    Apr 4 15:52:52 ifs pppd[24952]: rcvd [LCP ConfAck id=0x1 0x0> ]
    Apr 4 15:52:55 ifs pppd[24952]: sent [LCP ConfReq id=0x1 0x0> ]
    Apr 4 15:52:55 ifs pppd[24952]: rcvd [LCP ConfAck id=0x1 0x0> ]
    Apr 4 15:52:57 ifs pppd[24952]: rcvd [LCP ConfReq id=0x1
    ]
    Apr 4 15:52:57 ifs pppd[24952]: sent [LCP ConfAck id=0x1
    ]
    Apr 4 15:52:57 ifs pppd[24952]: sent [PAP AuthReq id=0x1 user="digi"
    password=]
    Apr 4 15:52:57 ifs pppd[24952]: rcvd [LCP EchoReq id=0x1
    magic=0x30200000]
    Apr 4 15:52:57 ifs pppd[24952]: sent [LCP EchoRep id=0x1
    magic=0x57865201]
    Apr 4 15:53:00 ifs pppd[24952]: sent [PAP AuthReq id=0x2 user="digi"
    password=]
    Apr 4 15:53:00 ifs pppd[24952]: rcvd [PAP AuthAck id=0x2 "Welcome to
    Motorola A760 Software Modem!"]
    Apr 4 15:53:00 ifs pppd[24952]: Remote message: Welcome to Motorola
    A760 Software Modem!
    Apr 4 15:53:00 ifs pppd[24952]: PAP authentication succeeded
    Apr 4 15:53:00 ifs pppd[24952]: sent [CCP ConfReq id=0x1
    ]
    Apr 4 15:53:00 ifs pppd[24952]: sent [IPCP ConfReq id=0x1 0f 01> ]
    Apr 4 15:53:00 ifs pppd[24952]: rcvd [IPCP ConfRej id=0x1 0f 01>]
    Apr 4 15:53:00 ifs pppd[24952]: sent [IPCP ConfReq id=0x2 0.0.0.0> ]
    Apr 4 15:53:02 ifs pppd[24952]: rcvd [LCP EchoReq id=0x1
    magic=0x30200000]
    Apr 4 15:53:02 ifs pppd[24952]: sent [LCP EchoRep id=0x1
    magic=0x57865201]
    Apr 4 15:53:03 ifs pppd[24952]: sent [CCP ConfReq id=0x1
    ]
    Apr 4 15:53:03 ifs pppd[24952]: sent [IPCP ConfReq id=0x2 0.0.0.0> ]
    Apr 4 15:53:05 ifs pppd[24952]: rcvd [IPCP ConfReq id=0x1]
    Apr 4 15:53:05 ifs pppd[24952]: sent [IPCP ConfNak id=0x1 0.0.0.0>]
    Apr 4 15:53:05 ifs pppd[24952]: rcvd [LCP TermReq id=0x2 00 00 00 00
    00 00]
    Apr 4 15:53:05 ifs pppd[24952]: LCP terminated by peer (^@^@^@^@^@^@)
    Apr 4 15:53:05 ifs pppd[24952]: sent [LCP TermAck id=0x2]
    Apr 4 15:53:08 ifs pppd[24952]: Connection terminated.
    Apr 4 15:53:08 ifs pppd[24952]: Exit.

    Does the above problem caused by a timeout? Why does LCP been
    terminated by peer? Does that mean the ISP does not support LCP?

    Any help will be much and greatly appreciated.

    -Ray-


  2. Re: wvdial does not connect

    "usher_raymond82@yahoo.com" writes:
    > I am trying to dial to the local GPRS network here in Malaysia. My


    You might want to search netnews archives. The oddities of GPRS have
    been discussed many times before.

    > Apr 4 15:53:03 ifs pppd[24952]: sent [IPCP ConfReq id=0x2 > 0.0.0.0> ]
    > Apr 4 15:53:05 ifs pppd[24952]: rcvd [IPCP ConfReq id=0x1]
    > Apr 4 15:53:05 ifs pppd[24952]: sent [IPCP ConfNak id=0x1 > 0.0.0.0>]
    > Apr 4 15:53:05 ifs pppd[24952]: rcvd [LCP TermReq id=0x2 00 00 00 00
    > 00 00]


    This behavior is pretty typical for GPRS.

    GPRS is designed very strangely. It does not do peer authentication
    during the PPP Authentication phase. That PAP Authenticate-Ack that
    you see is a complete fabrication: no authentication was done.
    Instead, it waits until IPCP runs to authenticate the user. If
    authentication fails, you then get really strange behavior with the
    peer appearing to be unable to negotiate an IP address.

    This is just a GPRS design flaw.

    > Does the above problem caused by a timeout?


    No. It means that either your user name/password are incorrect, or
    that your GPRS service has not been properly activated.

    > Why does LCP been
    > terminated by peer?


    It means that the peer is asking you to please go away. It doesn't
    want to talk to you anymore. It could just disconnect at layer one
    (hang up the phone), but it's being overly polite.

    Other than the suggestions above, the only way to find out why the
    peer sent the link termination request is to go inspect the debug logs
    on the peer's side. LCP provides a means for some useful text
    information to be included in the termination message, but for some
    reason the peer didn't bother doing that.

    > Does that mean the ISP does not support LCP?


    No.

    --
    James Carlson, KISS Network
    Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677

  3. Re: wvdial does not connect

    Nice to hear from you James. I've been reading your replies in this
    group to guide me on ppp.
    James Carlson wrote:
    > You might want to search netnews archives. The oddities of GPRS have
    > been discussed many times before.
    >

    netnews archives??
    >
    > This behavior is pretty typical for GPRS.
    >
    > GPRS is designed very strangely. It does not do peer authentication
    > during the PPP Authentication phase. That PAP Authenticate-Ack that
    > you see is a complete fabrication: no authentication was done.
    > Instead, it waits until IPCP runs to authenticate the user. If
    > authentication fails, you then get really strange behavior with the
    > peer appearing to be unable to negotiate an IP address.
    >
    > This is just a GPRS design flaw.

    Now I get a clearer picture.


    > No. It means that either your user name/password are incorrect, or
    > that your GPRS service has not been properly activated.
    >

    I believe the username and password should be correct. It is provided
    by the service provider here. I also believe that GPRS service has been
    properly activated as I managed to dial up on MS Win XP platform and
    also do some surfing on the phone itself, just to make sure GPRS and
    the phone works properly. Perhaps the only thing that I am afraid most
    is missing configurations. I've added the user name and password even
    to /etc/ppp/pap-secrets, necessary configurations to /etc/ppp/options
    and configured wvdial.conf. I hope and certainly wish I do not miss
    anything.


    >
    > It means that the peer is asking you to please go away. It doesn't
    > want to talk to you anymore. It could just disconnect at layer one
    > (hang up the phone), but it's being overly polite.

    So this could mean that all the pap authentication messages is a polite
    act? If so, why does IPCP send a ConfReq? If that is normal, then how
    come it can dial on a Win XP system?

    >
    > Other than the suggestions above, the only way to find out why the
    > peer sent the link termination request is to go inspect the debug logs
    > on the peer's side. LCP provides a means for some useful text
    > information to be included in the termination message, but for some
    > reason the peer didn't bother doing that.

    Debug log at the peer side? Do you mean check on the ISP side? I have
    no idea on how to do this.

    Thanks and hope to hear from you soon.

    Regards,
    Raymond


  4. Re: wvdial does not connect

    "usher_raymond82@yahoo.com" writes:
    > > You might want to search netnews archives. The oddities of GPRS have
    > > been discussed many times before.
    > >

    > netnews archives??


    There are many. Try http://groups.google.com/.

    > > No. It means that either your user name/password are incorrect, or
    > > that your GPRS service has not been properly activated.
    > >

    > I believe the username and password should be correct. It is provided
    > by the service provider here. I also believe that GPRS service has been
    > properly activated as I managed to dial up on MS Win XP platform and
    > also do some surfing on the phone itself, just to make sure GPRS and
    > the phone works properly. Perhaps the only thing that I am afraid most
    > is missing configurations. I've added the user name and password even
    > to /etc/ppp/pap-secrets, necessary configurations to /etc/ppp/options
    > and configured wvdial.conf. I hope and certainly wish I do not miss
    > anything.


    You should have something like this in your pppd configuration:

    user yourname

    and something like this in pap-secrets:

    yourname * "your passphrase"

    Be careful; special characters present in your username or passphrase
    must be escaped.

    > > It means that the peer is asking you to please go away. It doesn't
    > > want to talk to you anymore. It could just disconnect at layer one
    > > (hang up the phone), but it's being overly polite.

    > So this could mean that all the pap authentication messages is a polite
    > act?


    No; it's just broken by the GPRS standards. The peer sends PAP
    Authenticate-Ack even if the user name and passphrase you present are
    nonsense.

    > If so, why does IPCP send a ConfReq? If that is normal, then how
    > come it can dial on a Win XP system?


    I'm guessing that your user name / passphrase are correct on that XP
    system but are incorrect on this system.

    > > Other than the suggestions above, the only way to find out why the
    > > peer sent the link termination request is to go inspect the debug logs
    > > on the peer's side. LCP provides a means for some useful text
    > > information to be included in the termination message, but for some
    > > reason the peer didn't bother doing that.

    > Debug log at the peer side? Do you mean check on the ISP side? I have
    > no idea on how to do this.


    Nor do I. Good luck.

    --
    James Carlson, KISS Network
    Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677

  5. Re: wvdial does not connect


    James Carlson wrote:
    >
    > You should have something like this in your pppd configuration:
    >
    > user yourname
    >
    > and something like this in pap-secrets:
    >
    > yourname * "your passphrase"


    This is what I have in /etc/ppp/options
    lock
    crtscts
    defaultroute
    noauth
    noipdefault
    name digi
    debug

    and this is what I have in /etc/ppp/pap-secrets
    # Secrets for authentication using PAP
    # client server secret IP addresses
    name * password

    Is there anything wrong with this?


    > I'm guessing that your user name / passphrase are correct on that XP
    > system but are incorrect on this system.

    Both Systems use different authentication?


    > Nor do I. Good luck.

    If I could somehow manage to check the peer's log, I do not think the
    service provider would grant me access for this. =P

    Hope I do not miss anything.

    Raymond


  6. Re: wvdial does not connect

    "usher_raymond82@yahoo.com" writes:
    > This is what I have in /etc/ppp/options
    > lock
    > crtscts
    > defaultroute
    > noauth
    > noipdefault
    > name digi
    > debug


    You should have "user digi" instead of "name digi," assuming your name
    is in fact "digi." It's a bit of a minor point, but "name" is
    typically used for dial-in servers (which is not what you have) and
    "user" is used for dial-out.

    You may also want "noccp," as it's clear the peer doesn't implement
    that.

    > and this is what I have in /etc/ppp/pap-secrets
    > # Secrets for authentication using PAP
    > # client server secret IP addresses
    > name * password
    >
    > Is there anything wrong with this?


    Is that literal? You should have exactly the same "name" here that's
    given for the name or user option in /etc/ppp/options.

    > > I'm guessing that your user name / passphrase are correct on that XP
    > > system but are incorrect on this system.

    > Both Systems use different authentication?


    I don't understand what you're saying here.

    My comment was that the symptoms here imply that you've correctly
    configured your peer (user) name and passphrase on that XP box, but
    you have not correctly configured the same data on the machine running
    pppd. It is likely to be the incorrectly specified user name and/or
    passphrase that is causing the problem.

    --
    James Carlson, KISS Network
    Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677

  7. Re: wvdial does not connect


    Your MOtorola's implimentation of ppp is bizare.
    Get rid of the request for ccp, (put noccp , novj, into /etc/ppp/options.)

    The remote system does support ppp, but its implimentation seems to be
    exceedingly broken. You are going to have to try to immitate a Win machine
    as much as possible.


    "usher_raymond82@yahoo.com" writes:

    >Hi,


    >I am trying to dial to the local GPRS network here in Malaysia. My
    >system is running on linux and I am very new to linux and pppd. After
    >installing linux, pppd and wvdial onto my system, I face a weird
    >situation where it can't seem to connect to the GPRS network. I've
    >configure all the necessary configurations and below is the snippet
    >from the debug log (/var/log/debug).


    >Apr 4 15:52:49 ifs pppd[24952]: pppd 2.4.2 started by root, uid 0
    >Apr 4 15:52:49 ifs pppd[24952]: using channel 32
    >Apr 4 15:52:49 ifs pppd[24952]: Using interface ppp0
    >Apr 4 15:52:49 ifs pppd[24952]: Connect: ppp0 <--> /dev/ttyACM0
    >Apr 4 15:52:49 ifs pppd[24952]: sent [LCP ConfReq id=0x1 >0x0> ]
    >Apr 4 15:52:49 ifs pppd[24952]: rcvd [LCP ConfAck id=0x1 >0x0> ]
    >Apr 4 15:52:52 ifs pppd[24952]: sent [LCP ConfReq id=0x1 >0x0> ]


    YOur own implimentation also seems to be broken. It gets a ConfAck and
    immediately sends out the same request. What pppd are you running? Are you
    sure that your distribution has not messed it up?

    Mind you the remote machine seems to be incapable of starting its own ppp
    stream, so maybe your side is just trying to wake it up.


    >Apr 4 15:52:52 ifs pppd[24952]: rcvd [LCP ConfAck id=0x1 >0x0> ]
    >Apr 4 15:52:55 ifs pppd[24952]: sent [LCP ConfReq id=0x1 >0x0> ]
    >Apr 4 15:52:55 ifs pppd[24952]: rcvd [LCP ConfAck id=0x1 >0x0> ]
    >Apr 4 15:52:57 ifs pppd[24952]: rcvd [LCP ConfReq id=0x1
    > ]


    Finally a ConfReq from the other side. 10 sec after negotiations start.
    This is not good.


    >Apr 4 15:52:57 ifs pppd[24952]: sent [LCP ConfAck id=0x1
    > ]
    >Apr 4 15:52:57 ifs pppd[24952]: sent [PAP AuthReq id=0x1 user="digi"
    >password=]
    >Apr 4 15:52:57 ifs pppd[24952]: rcvd [LCP EchoReq id=0x1
    >magic=0x30200000]
    >Apr 4 15:52:57 ifs pppd[24952]: sent [LCP EchoRep id=0x1
    >magic=0x57865201]
    >Apr 4 15:53:00 ifs pppd[24952]: sent [PAP AuthReq id=0x2 user="digi"
    >password=]
    >Apr 4 15:53:00 ifs pppd[24952]: rcvd [PAP AuthAck id=0x2 "Welcome to
    >Motorola A760 Software Modem!"]
    >Apr 4 15:53:00 ifs pppd[24952]: Remote message: Welcome to Motorola
    >A760 Software Modem!
    >Apr 4 15:53:00 ifs pppd[24952]: PAP authentication succeeded


    OK, you are authenticated.

    >Apr 4 15:53:00 ifs pppd[24952]: sent [CCP ConfReq id=0x1
    >]


    This may be totally confusing the remote machine. Make sure you put noccp
    into your options file.

    >Apr 4 15:53:00 ifs pppd[24952]: sent [IPCP ConfReq id=0x1 >0f 01> ]
    >Apr 4 15:53:00 ifs pppd[24952]: rcvd [IPCP ConfRej id=0x1 >0f 01>]


    Ah, a response. Also put in novj


    >Apr 4 15:53:00 ifs pppd[24952]: sent [IPCP ConfReq id=0x2 >0.0.0.0> ]


    And now the remote system has gone into a sulk. Who knowns why.

    You might get rid of the ms-dns requests. ( remove them from
    /etc/ppp/options) to see if you at least get a connection.


    >Apr 4 15:53:02 ifs pppd[24952]: rcvd [LCP EchoReq id=0x1
    >magic=0x30200000]


    Sheesh. This is the phone trying to see if yo uare still awake, when it has
    gone to sleep.


    >Apr 4 15:53:02 ifs pppd[24952]: sent [LCP EchoRep id=0x1
    >magic=0x57865201]
    >Apr 4 15:53:03 ifs pppd[24952]: sent [CCP ConfReq id=0x1
    >]


    Again, it will NOT be able to do these compressions. You should not be
    asking. It probably confuses the far side, because the programmer was
    incompetent.

    >Apr 4 15:53:03 ifs pppd[24952]: sent [IPCP ConfReq id=0x2 >0.0.0.0> ]
    >Apr 4 15:53:05 ifs pppd[24952]: rcvd [IPCP ConfReq id=0x1]


    This is silly. It has really gone into a sulk.

    >Apr 4 15:53:05 ifs pppd[24952]: sent [IPCP ConfNak id=0x1 >0.0.0.0>]
    >Apr 4 15:53:05 ifs pppd[24952]: rcvd [LCP TermReq id=0x2 00 00 00 00
    >00 00]


    And finally it says it does not want to talk to you.


    >Apr 4 15:53:05 ifs pppd[24952]: LCP terminated by peer (^@^@^@^@^@^@)
    >Apr 4 15:53:05 ifs pppd[24952]: sent [LCP TermAck id=0x2]
    >Apr 4 15:53:08 ifs pppd[24952]: Connection terminated.
    >Apr 4 15:53:08 ifs pppd[24952]: Exit.


    >Does the above problem caused by a timeout? Why does LCP been


    No.

    >terminated by peer? Does that mean the ISP does not support LCP?


    It means the far side requested that you get lost.
    No it does not mean it does not support LCP. It has been talking LCP during
    the whole negotiation. It is impossible to know what it does not like from
    this exchange since the far side remains largely silent.


    >Any help will be much and greatly appreciated.


    >-Ray-



  8. Re: wvdial does not connect

    "usher_raymond82@yahoo.com" writes:

    >Nice to hear from you James. I've been reading your replies in this
    >group to guide me on ppp.
    >James Carlson wrote:
    >> You might want to search netnews archives. The oddities of GPRS have
    >> been discussed many times before.
    >>

    >netnews archives??
    >>
    >> This behavior is pretty typical for GPRS.
    >>
    >> GPRS is designed very strangely. It does not do peer authentication
    >> during the PPP Authentication phase. That PAP Authenticate-Ack that
    >> you see is a complete fabrication: no authentication was done.
    >> Instead, it waits until IPCP runs to authenticate the user. If
    >> authentication fails, you then get really strange behavior with the
    >> peer appearing to be unable to negotiate an IP address.
    >>
    >> This is just a GPRS design flaw.

    >Now I get a clearer picture.



    >> No. It means that either your user name/password are incorrect, or
    >> that your GPRS service has not been properly activated.
    >>

    >I believe the username and password should be correct. It is provided
    >by the service provider here. I also believe that GPRS service has been
    >properly activated as I managed to dial up on MS Win XP platform and
    >also do some surfing on the phone itself, just to make sure GPRS and
    >the phone works properly. Perhaps the only thing that I am afraid most
    >is missing configurations. I've added the user name and password even
    >to /etc/ppp/pap-secrets, necessary configurations to /etc/ppp/options
    >and configured wvdial.conf. I hope and certainly wish I do not miss
    >anything.



    >>
    >> It means that the peer is asking you to please go away. It doesn't
    >> want to talk to you anymore. It could just disconnect at layer one
    >> (hang up the phone), but it's being overly polite.

    >So this could mean that all the pap authentication messages is a polite
    >act? If so, why does IPCP send a ConfReq? If that is normal, then how
    >come it can dial on a Win XP system?


    Who knows what it is trying to do. It is very confused. It may be that your
    compression requests drive it out of its mind. Win would not ask for those
    compressions.


    >>
    >> Other than the suggestions above, the only way to find out why the
    >> peer sent the link termination request is to go inspect the debug logs
    >> on the peer's side. LCP provides a means for some useful text
    >> information to be included in the termination message, but for some
    >> reason the peer didn't bother doing that.

    >Debug log at the peer side? Do you mean check on the ISP side? I have
    >no idea on how to do this.


    Yes, that is a problem.


    >Thanks and hope to hear from you soon.


    >Regards,
    >Raymond



  9. Re: wvdial does not connect

    James Carlson writes:

    >"usher_raymond82@yahoo.com" writes:
    >> > You might want to search netnews archives. The oddities of GPRS have
    >> > been discussed many times before.
    >> >

    >> netnews archives??


    >There are many. Try http://groups.google.com/.


    >> > No. It means that either your user name/password are incorrect, or
    >> > that your GPRS service has not been properly activated.
    >> >

    >> I believe the username and password should be correct. It is provided
    >> by the service provider here. I also believe that GPRS service has been
    >> properly activated as I managed to dial up on MS Win XP platform and
    >> also do some surfing on the phone itself, just to make sure GPRS and
    >> the phone works properly. Perhaps the only thing that I am afraid most
    >> is missing configurations. I've added the user name and password even
    >> to /etc/ppp/pap-secrets, necessary configurations to /etc/ppp/options
    >> and configured wvdial.conf. I hope and certainly wish I do not miss
    >> anything.


    >You should have something like this in your pppd configuration:


    > user yourname


    >and something like this in pap-secrets:


    > yourname * "your passphrase"


    >Be careful; special characters present in your username or passphrase
    >must be escaped.


    He apparently has those since he does answer the pap authentication
    request. Now it may be that the username or password are wrong of course.


    >> > It means that the peer is asking you to please go away. It doesn't
    >> > want to talk to you anymore. It could just disconnect at layer one
    >> > (hang up the phone), but it's being overly polite.

    >> So this could mean that all the pap authentication messages is a polite
    >> act?


    >No; it's just broken by the GPRS standards. The peer sends PAP
    >Authenticate-Ack even if the user name and passphrase you present are
    >nonsense.


    >> If so, why does IPCP send a ConfReq? If that is normal, then how
    >> come it can dial on a Win XP system?


    >I'm guessing that your user name / passphrase are correct on that XP
    >system but are incorrect on this system.


    >> > Other than the suggestions above, the only way to find out why the
    >> > peer sent the link termination request is to go inspect the debug logs
    >> > on the peer's side. LCP provides a means for some useful text
    >> > information to be included in the termination message, but for some
    >> > reason the peer didn't bother doing that.

    >> Debug log at the peer side? Do you mean check on the ISP side? I have
    >> no idea on how to do this.


    >Nor do I. Good luck.



  10. Re: wvdial does not connect

    "usher_raymond82@yahoo.com" writes:


    >James Carlson wrote:
    >>
    >> You should have something like this in your pppd configuration:
    >>
    >> user yourname
    >>
    >> and something like this in pap-secrets:
    >>
    >> yourname * "your passphrase"


    >This is what I have in /etc/ppp/options
    >lock
    >crtscts
    >defaultroute
    >noauth
    >noipdefault
    >name digi


    This is not causing the problem but use
    user digi
    not name digi
    Also put in novj and noccp

    >debug


    >and this is what I have in /etc/ppp/pap-secrets
    ># Secrets for authentication using PAP
    ># client server secret IP addresses
    >name * password


    I assume that you have
    digi
    not
    name
    in that line. and for password it is the actual password, not the word
    password.


    >Is there anything wrong with this?



    >> I'm guessing that your user name / passphrase are correct on that XP
    >> system but are incorrect on this system.

    >Both Systems use different authentication?



    >> Nor do I. Good luck.

    >If I could somehow manage to check the peer's log, I do not think the
    >service provider would grant me access for this. =P


    >Hope I do not miss anything.


    Trying to figure out how other people could be incompetent is always a hard
    job. The creativity of incompetence seems boundless.



  11. Re: wvdial does not connect

    Unruh writes:
    > >Apr 4 15:52:49 ifs pppd[24952]: sent [LCP ConfReq id=0x1 > >0x0> ]
    > >Apr 4 15:52:49 ifs pppd[24952]: rcvd [LCP ConfAck id=0x1 > >0x0> ]
    > >Apr 4 15:52:52 ifs pppd[24952]: sent [LCP ConfReq id=0x1 > >0x0> ]

    >
    > YOur own implimentation also seems to be broken. It gets a ConfAck and
    > immediately sends out the same request.


    That's not true. Look at the time stamps. That second request is due
    to the restart timer -- three seconds have elapsed without a Configure
    Request message from the peer, which means we're stuck in AckRcvd
    state with the timer running. TO+ causes a new request to be sent.

    This is all correct, and not a bug, and not broken.

    The problems are on the peer's side. That it's using GPRS is probably
    the most significant one.

    --
    James Carlson, KISS Network
    Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677

  12. Re: wvdial does not connect

    James Carlson writes:

    >Unruh writes:
    >> >Apr 4 15:52:49 ifs pppd[24952]: sent [LCP ConfReq id=0x1 >> >0x0> ]
    >> >Apr 4 15:52:49 ifs pppd[24952]: rcvd [LCP ConfAck id=0x1 >> >0x0> ]
    >> >Apr 4 15:52:52 ifs pppd[24952]: sent [LCP ConfReq id=0x1 >> >0x0> ]

    >>
    >> YOur own implimentation also seems to be broken. It gets a ConfAck and
    >> immediately sends out the same request.


    >That's not true. Look at the time stamps. That second request is due
    >to the restart timer -- three seconds have elapsed without a Configure
    >Request message from the peer, which means we're stuck in AckRcvd
    >state with the timer running. TO+ causes a new request to be sent.


    >This is all correct, and not a bug, and not broken.


    Yes, I was beginning to suspect that. Wait 2 sec for a counter proposal
    from the far side and try again if it does not come? It knows that ppp is
    operational on the far side since it did get a ConfAck.

    >The problems are on the peer's side. That it's using GPRS is probably
    >the most significant one.


    Well, it is a useful service. Too bad the implimenters all seem to be
    incompetent. Have not read enough books I guess :-)


  13. Re: wvdial does not connect

    Hi,

    Where is your chatscript to setup physical link ? or you have another

    /etc/ppp/options.ttyACM0 file since pppd using ttyACM0 .

    I have setup GPRS connection with pppd in RedHat on ttyS0 with
    iTegno/Siemen modem.
    My configuration /etc/ppp/options.ttyS0 file;
    lock
    crtscts
    nobsdcomp
    novj
    noipdefault
    deflate 0,0
    defaultroute
    user abc
    pap-timeout 10
    pap-max-authreq 3
    connect "/usr/sbin/chat -v -t 20 -f /etc/ppp/chatscript"

    /etc/ppp/chatscript
    "" "AT"
    OK "AT+CGDCONT=1,\"IP\",\"shsurbana1\""
    OK "AT+CGATT=1"
    OK "ATDT*99***1#"
    TIMEOUT 60 CONNECT

    /etc/ppp/pap-secrets
    abc * *


  14. Re: wvdial does not connect

    Goh Choon Lye wrote:
    > Hi,
    >
    > Where is your chatscript to setup physical link ? or you have another
    >
    > /etc/ppp/options.ttyACM0 file since pppd using ttyACM0 .
    >

    I do not have /etc/ppp/options.ttyACM0. I am using wvdial and below is
    my wvdial.conf

    [Dialer Defaults]
    Modem = /dev/ttyACM0
    Baud = 460800
    Init1 = ATZ
    Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCFLAGS=0
    Init3 = AT+CGDCONT=1, "IP", "diginet"
    Usename = digi
    Password = digi
    ISDN = 0
    Modem Type = USB Modem

    The above uses the default wvdial configuration except the phone
    number, username and password.



    James, Unruh,

    This is my new /etc/ppp/options
    lock
    crtscts
    defaultroute
    noauth
    noipdefault
    noccp
    novj
    user digi
    debug

    and this is my new /etc/ppp/pap-secrets
    # Secrets for authentication using PAP
    # client server secret IP addresses
    digi * digi

    I try connecting and still face the same log message.

    Regards,
    Raymond


  15. Re: wvdial does not connect

    "usher_raymond82@yahoo.com" writes:
    > I try connecting and still face the same log message.


    I think that makes it fairly simple: the problem has to be an
    incorrect user name and/or password. You need to correct those, and I
    don't see how anyone here can really help with that.

    --
    James Carlson, KISS Network
    Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677

  16. Re: wvdial does not connect

    "usher_raymond82@yahoo.com" writes:

    >Goh Choon Lye wrote:
    >> Hi,
    >>
    >> Where is your chatscript to setup physical link ? or you have another
    >>
    >> /etc/ppp/options.ttyACM0 file since pppd using ttyACM0 .
    >>

    >I do not have /etc/ppp/options.ttyACM0. I am using wvdial and below is
    >my wvdial.conf


    >[Dialer Defaults]
    >Modem = /dev/ttyACM0
    >Baud = 460800
    >Init1 = ATZ
    >Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCFLAGS=0
    >Init3 = AT+CGDCONT=1, "IP", "diginet"
    >Usename = digi
    >Password = digi
    >ISDN = 0
    >Modem Type = USB Modem


    >The above uses the default wvdial configuration except the phone
    >number, username and password.




    >James, Unruh,


    >This is my new /etc/ppp/options
    >lock
    >crtscts
    >defaultroute
    >noauth
    >noipdefault
    >noccp
    >novj
    >user digi
    >debug


    >and this is my new /etc/ppp/pap-secrets
    ># Secrets for authentication using PAP
    ># client server secret IP addresses
    >digi * digi


    >I try connecting and still face the same log message.


    No you do not. There should be no compression attempts and no vj requests.
    Please post the output of th elogs. YOu admit that you do not understand
    what is happening. Thus your ability to read the logs is also suspect.

    Finally as James says, it may well be that the remote system thinks your
    username or password are incorrect. You can only find that out by talking
    with your ISP.

    If they are rejecting you because of your password or username, you cannot
    tell from your end. Nothing you post or try to do will work.

    As an example, try replacing your username and password in
    /etc/ppp/pap-secrets with wrong ones, and try logging on. Is there any
    difference in the logon? If there is then the hypothesis is wrong, but if
    there is not, then it is the strongest possibility.



    >Regards,
    >Raymond



  17. Re: wvdial does not connect

    I will post the log message coming monday as I will be away during the
    weekend. In the mean time I will also try some other username and
    password just to verify whether I will get the same log message.

    Thanks for the help all these while.

    Raymond

    Unruh wrote:
    > "usher_raymond82@yahoo.com" writes:
    >
    > >Goh Choon Lye wrote:
    > >> Hi,
    > >>
    > >> Where is your chatscript to setup physical link ? or you have another
    > >>
    > >> /etc/ppp/options.ttyACM0 file since pppd using ttyACM0 .
    > >>

    > >I do not have /etc/ppp/options.ttyACM0. I am using wvdial and below is
    > >my wvdial.conf

    >
    > >[Dialer Defaults]
    > >Modem = /dev/ttyACM0
    > >Baud = 460800
    > >Init1 = ATZ
    > >Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCFLAGS=0
    > >Init3 = AT+CGDCONT=1, "IP", "diginet"
    > >Usename = digi
    > >Password = digi
    > >ISDN = 0
    > >Modem Type = USB Modem

    >
    > >The above uses the default wvdial configuration except the phone
    > >number, username and password.

    >
    >
    >
    > >James, Unruh,

    >
    > >This is my new /etc/ppp/options
    > >lock
    > >crtscts
    > >defaultroute
    > >noauth
    > >noipdefault
    > >noccp
    > >novj
    > >user digi
    > >debug

    >
    > >and this is my new /etc/ppp/pap-secrets
    > ># Secrets for authentication using PAP
    > ># client server secret IP addresses
    > >digi * digi

    >
    > >I try connecting and still face the same log message.

    >
    > No you do not. There should be no compression attempts and no vj requests.
    > Please post the output of th elogs. YOu admit that you do not understand
    > what is happening. Thus your ability to read the logs is also suspect.
    >
    > Finally as James says, it may well be that the remote system thinks your
    > username or password are incorrect. You can only find that out by talking
    > with your ISP.
    >
    > If they are rejecting you because of your password or username, you cannot
    > tell from your end. Nothing you post or try to do will work.
    >
    > As an example, try replacing your username and password in
    > /etc/ppp/pap-secrets with wrong ones, and try logging on. Is there any
    > difference in the logon? If there is then the hypothesis is wrong, but if
    > there is not, then it is the strongest possibility.
    >
    >
    >
    > >Regards,
    > >Raymond



+ Reply to Thread