The internal modem you have IS a Winmodem (check
http://www.o2.net/~gromitkc/winmodem.html for details), but that has nothing
to do with your ppp problem. The external modem is successfully connecting
to the ISP's modem, just not succeeding in negotiating a ppp link. That is
unlikely to be a hardware problem (though I do recall a few obscure
situations in which particular modems needed special init strings to handle
ppp, ther are rare).
Going back to your original message ... as I read your pppd log, it
successfully negotiates with your ISP over authentication (declining to
authenticate via chap, but offering to do so via pap, which the ISP accepts
... I assume you edited the log to conceal your real password behind the
phrase "insert here"), gets IP addresses assigned to both ends of the link,
but then fails over some other piece of the protocol negotiation. I base
this last observation on these messages:
Dec 5 22:57:09 slemay pppd[147]: sent [CCP ConfReq id=0x2]
...
Dec 5 22:57:09 slemay pppd[147]: rcvd [CCP ConfNak id=0x2 < 12 06 00 00 00
01>
After this, the completion of the ip-up script somehow interferes with pppd
seeing the later ConfReq packets sent by the ISP.
The problem apparently lies in CCP negotiation option 0x12, whatever that
is. I'm not familiar with CCP -- it is a data compression standard, defined
in RFC 1962, but beyond that, I don't know the details of why either your
end it trying to use it or your ISP is rejectng it.
One other puzzling thing in the log is this message:
Dec 5 22:57:13 slemay pppd[147]: rcvd [LCP ProtRej id=0x5 80 fd 01 07 00
04]
I can't find a prior id=5 that the ISP is responding to. This makes me
wonder if you have a physical problem with the phone line, one that is
corrupting packets. The protocol that is being rejected is a mess -- my
reference lists no protocol 0x80, and the 0xfd is supposed to be the message
length in octets, but the actual message sent back is only 6 octets long.
Having said all of this, I'm afraid it isn't as helpful as I'd like to be.
Sorry. Perhaps with these details in the log highlighted, somsone else can
suggest a better interpretation of them? Or perhaps you need to post this
one to linux-ppp?
At 01:56 PM 12/6/99 -0500, Stephen LeMay wrote [in part]:
>...the other issue, is an internal modem on
>com2 which linux does not see, at boot, ttyS1 is
>not recognized
>If I disable com1, I may have no connection at all,
>I have a few configuration problems here, I dont know
>if the internal modem is a so called winmodem
>Rockwell HCF 56K data/fax PCI modem
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
