Re: Connection problem between ppp-2.4.1-3 and an ISP - PPP

This is a discussion on Re: Connection problem between ppp-2.4.1-3 and an ISP - PPP ; Juhani Jaakola wrote: > I use Red Hat 7.2 with ppp-2.4.1-3 (the updated version). I can > successfully connect to two ISPs, but I have the following problem > with another ISP (see the debug log below). I have tried ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Re: Connection problem between ppp-2.4.1-3 and an ISP

  1. Re: Connection problem between ppp-2.4.1-3 and an ISP

    Juhani Jaakola wrote:
    > I use Red Hat 7.2 with ppp-2.4.1-3 (the updated version). I can
    > successfully connect to two ISPs, but I have the following problem
    > with another ISP (see the debug log below). I have tried to use pppd
    > parameters such as "noccp" or "noaccomp" or "nopcomp" or "mru 296" or
    > "nobsdcomp" but I have been unable to make a connection. I can connect
    > to that ISP with Nokia 9110 Communicator and Red Hat 6.1.


    > I'm using IBM ThinkPad 560Z with Nokia 9110 Communicator (a GSM cell
    > phone) as my modem.


    > What is the problem here and is there a parameter to pppd that could
    > solve my problem?


    Highly unlikely if my guess (see below) is correct.

    > This is what happens when I try to connect (without any exotic pppd
    > parameters):


    ....

    > sent [PAP AuthReq id=0x2 user="USERNAME" password=]
    > rcvd [PAP AuthAck id=0x2 ""]
    > sent [IPCP ConfReq id=0x1 ]
    > sent [CCP ConfReq id=0x1 ]
    > rcvd [IPCP ConfReq id=0x3 ]
    > sent [IPCP ConfAck id=0x3 ]
    > rcvd [CCP ConfReq id=0x4 < 11 05 00 01 03> ]
    > sent [CCP ConfRej id=0x4 < 11 05 00 01 03>]


    I'll hazard a guess. The ISP has a PPP implementation with broken
    CCP negotiation that requests STAC data compression (11 05 00 01 03),
    as well as other varieties of CCP, but won't accept no as an answer
    (ConfRej) for STAC. Microsoft would likely have STAC and the rest
    of us don't matter to the ISP.

    STAC compression requires a license so pppd doesn't implement it.
    After receiving the ConfRej the ISP should resend the CCP request sans
    STAC, but it doesn't do so. That's really unfortunate since I think
    the other CCP algorithms in the request are supported by pppd.

    > sent [IPCP ConfReq id=0x1 ]
    > sent [CCP ConfReq id=0x1 ]


    ....

    Since pppd hasn't received any answer to it's IPCP request or it's CCP
    request it resends them numerous times until ...

    > IPCP: timeout sending Config-Requests
    > sent [LCP TermReq id=0x2 "No network protocols running"]
    > sent [LCP TermReq id=0x3 "No network protocols running"]
    > Modem hangup
    > Connection terminated.


    it times out on IPCP requests.

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* The wealth of a nation is created by the productive labor of its
    * citizens. */

  2. Re: Connection problem between ppp-2.4.1-3 and an ISP

    I can connect to that ISP using Red Hat 6.1 which has ppp-2.3.10-1.
    When connecting to that ISP pppd displays twice message "BSD-Compress
    (15/12) compression enabled"

    Why ppp-2.3.10-1 can connect but ppp-2.4.1-3 can't? Is there an option
    to pppd to force ppp-2.4.1-3 to behave like ppp-2.3.10-1? Should I try
    forcing BSD compression?

    Clifford Kite wrote in message news:...
    > Juhani Jaakola wrote:
    > > I use Red Hat 7.2 with ppp-2.4.1-3 (the updated version). I can
    > > successfully connect to two ISPs, but I have the following problem
    > > with another ISP (see the debug log below). I have tried to use pppd
    > > parameters such as "noccp" or "noaccomp" or "nopcomp" or "mru 296" or
    > > "nobsdcomp" but I have been unable to make a connection. I can connect
    > > to that ISP with Nokia 9110 Communicator and Red Hat 6.1.

    >
    > > I'm using IBM ThinkPad 560Z with Nokia 9110 Communicator (a GSM cell
    > > phone) as my modem.

    >
    > > What is the problem here and is there a parameter to pppd that could
    > > solve my problem?

    >
    > Highly unlikely if my guess (see below) is correct.
    >
    > > This is what happens when I try to connect (without any exotic pppd
    > > parameters):

    > ...
    >
    > > sent [PAP AuthReq id=0x2 user="USERNAME" password=]
    > > rcvd [PAP AuthAck id=0x2 ""]
    > > sent [IPCP ConfReq id=0x1 ]
    > > sent [CCP ConfReq id=0x1 ]
    > > rcvd [IPCP ConfReq id=0x3 ]
    > > sent [IPCP ConfAck id=0x3 ]
    > > rcvd [CCP ConfReq id=0x4 < 11 05 00 01 03> ]
    > > sent [CCP ConfRej id=0x4 < 11 05 00 01 03>]

    >
    > I'll hazard a guess. The ISP has a PPP implementation with broken
    > CCP negotiation that requests STAC data compression (11 05 00 01 03),
    > as well as other varieties of CCP, but won't accept no as an answer
    > (ConfRej) for STAC. Microsoft would likely have STAC and the rest
    > of us don't matter to the ISP.
    >
    > STAC compression requires a license so pppd doesn't implement it.
    > After receiving the ConfRej the ISP should resend the CCP request sans
    > STAC, but it doesn't do so. That's really unfortunate since I think
    > the other CCP algorithms in the request are supported by pppd.


  3. Re: Connection problem between ppp-2.4.1-3 and an ISP

    juhani.jaakola@kolumbus.fi (Juhani Jaakola) writes:
    > I can connect to that ISP using Red Hat 6.1 which has ppp-2.3.10-1.
    > When connecting to that ISP pppd displays twice message "BSD-Compress
    > (15/12) compression enabled"


    Why is the ISP asking for STAC compression? That's no ppp-2.3.10
    option. Are you _sure_ that the peer is actually using ppp-2.3.10?
    If so, I'd hazard to guess that this ISP has a hacked version of pppd,
    and it might well be buggy.

    > Why ppp-2.3.10-1 can connect but ppp-2.4.1-3 can't? Is there an option
    > to pppd to force ppp-2.4.1-3 to behave like ppp-2.3.10-1? Should I try
    > forcing BSD compression?


    "nodeflate" *should* do it, but ...

    > > > sent [CCP ConfReq id=0x1 ]


    .... this implies that either your copy of pppd or your kernel (for
    some reason) doesn't actually support BSD compression, which is quite
    odd.

    --
    James Carlson, Solaris Networking
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  4. Re: Connection problem between ppp-2.4.1-3 and an ISP

    James Carlson writes:
    > juhani.jaakola@kolumbus.fi (Juhani Jaakola) writes:
    > > I can connect to that ISP using Red Hat 6.1 which has ppp-2.3.10-1.
    > > When connecting to that ISP pppd displays twice message "BSD-Compress
    > > (15/12) compression enabled"

    >
    > Why is the ISP asking for STAC compression? That's no ppp-2.3.10
    > option. Are you _sure_ that the peer is actually using ppp-2.3.10?
    > If so, I'd hazard to guess that this ISP has a hacked version of pppd,
    > and it might well be buggy.


    Oh ... grumble. I misread that text above -- you're not saying that
    the ISP has pppd, but rather that this all works when *you* use
    ppp-2.3.10.

    > > Why ppp-2.3.10-1 can connect but ppp-2.4.1-3 can't? Is there an option
    > > to pppd to force ppp-2.4.1-3 to behave like ppp-2.3.10-1? Should I try
    > > forcing BSD compression?

    >
    > "nodeflate" *should* do it, but ...
    >
    > > > > sent [CCP ConfReq id=0x1 ]

    >
    > ... this implies that either your copy of pppd or your kernel (for
    > some reason) doesn't actually support BSD compression, which is quite
    > odd.


    .... or that you have it explicitly disabled somehow.

    --
    James Carlson, Solaris Networking
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  5. Re: Connection problem between ppp-2.4.1-3 and an ISP

    James Carlson wrote:
    > James Carlson writes:
    >> juhani.jaakola@kolumbus.fi (Juhani Jaakola) writes:
    >> > Why ppp-2.3.10-1 can connect but ppp-2.4.1-3 can't? Is there an option
    >> > to pppd to force ppp-2.4.1-3 to behave like ppp-2.3.10-1? Should I try
    >> > forcing BSD compression?

    >>
    >> "nodeflate" *should* do it, but ...


    I don't see how, the peer didn't re-request it's CCP alternatives to
    STAC compression.

    >> > > > sent [CCP ConfReq id=0x1 ]

    >>
    >> ... this implies that either your copy of pppd or your kernel (for
    >> some reason) doesn't actually support BSD compression, which is quite
    >> odd.


    > ... or that you have it explicitly disabled somehow.


    Don't you have to explicitly request it in order to receive BSD
    compressed data?

    Although I guess you could consider omitting the option as explicitly
    disabling it...

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* For every credibility gap, there is a gullibility fill.
    -- R. Clopton */

  6. Re: Connection problem between ppp-2.4.1-3 and an ISP

    Clifford Kite writes:
    > Don't you have to explicitly request it in order to receive BSD
    > compressed data?


    No ... by default, pppd offers all of the compression mechanisms that
    it knows it can support at once. The fact that BSD compression was
    omitted from his CCP Configure-Request message means one of these:

    - it's explicitly disabled by configuration (not the default)
    - it's compiled out of his copy of pppd (not the default)
    - the support module is missing from his kernel

    I can't tell which one, though ...

    --
    James Carlson, Solaris Networking
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

+ Reply to Thread