Bug 7335
| Summary: | PPP doesn't work in 6.1 | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | collin |
| Component: | ppp | Assignee: | Michael K. Johnson <johnsonm> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | ramiro |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 1999-12-07 15:34:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
collin
1999-11-26 00:13:48 UTC
This does not appear to have anything to do with PAP. This timeout sending config requests means that the PPP daemon is unable to negotiate a working PPP connection with the remote side. There are all sorts of reasons this could be going wrong. Try adding the line DEBUG=yes to your ifcfg-ppp0 file and see what additional information it produces. Added DEBUG=yes to ifcfg-ppp0 file, and I am getting the following: Unsupported protocol (0x80fd) received Looks like protocol 0x80fd is unsupported and the other side insists that it work in order to have a connection. I don't know what protocol 0x80fd is, though, so I don't have much idea what to tell you at this point. The unsupported protocol problem only showed once and did not appear ever again. Now, do I need anything in the /etc/resolv.conf, /etc/hosts.deny, hosts.allow, /etc/networks files?? 80fd, it turns out, is compression control protocol, which should be supported. Not sure why you got the error message, but glad to know it isn't a continuing problem. If you have all the latest errata updates, /etc/resolv.conf will be updated automatically. You should not need to set up /etc/sysconfig/network or the /etc/host.* files to get your PPP connection working. You are still getting "LCP: timeout sending Config-Requests", right? Yep, I am still getting the time-outs. I am going to delete evrything from my
host.* files and see what happens. I also have the following entry in
my /etc/networks file
loopback 127.0.0.0
localnet 0.0.0.0
Should I have this? I took this from an old config. manual
I really don't think those are related. I have nothing in /etc/networks and I haven't touched the hosts.* files, but they really shouldn't have anything to do with this. Have you tried lowering your LINESPEED=57600 to LINESPEED=38400 to see if that helps? I haven't tried lowering my line speed. Does that have anythong to do with 'pppd' at all or is it just related to the connection? That's about the only recommended thing I haven't done so far! That changes the speed that ppp sets the modem to before connecting. Please try it. I lowered my modem speed, LINESPEED=38400, but the same thing happened. At this point, I am really baffled. I am just gonna go back to RedHat 6.0. What's the significance of LCP? LCP is the link control protocol; it's one of the base protocols that pppd uses to set up other PPP protocols. It isn't totally broken -- if it were, then no one would be able to connect via PPP at all. One other thing that has caused this problem in the past is a modem with misconfigured interrupts. If Linux is misinformed about what interrupt the modem is on, it will default to polled mode, and that goes slowly -- too slowly for LCP to work. Are your kernel messages at boot time about what IRQ it is using for ttyS2 correct? Is it a different IRQ from ttyS0? (It needs to be different.) That could be it. When I use RP3 to detect the modem, it looks like it finds
something on /dev/ttyS0 (says determining modem type, etc,etc) then comes back
and says no modem detected.
Also, I have an /etc/rc.d/rc.serial with the following command:
setserial /dev/ttyS2 auto_irq autoconfig skip_test uart 16450
Do I need this command? Another thing, how do I set up the irq for /dev/ttyS2
to be different from /dev/ttyS0 's irq? I know pppd is not broken at all; I
have a Compaq Netelligent plug and play modem.
Oooh, a 16450 uart can't handle PPP very well at speeds that are at
all high, particularly if you have IDE hard drives.
plug and play modems are often unsupported "winmodems"; you are sure
that this is not the case?
Try using the isapnp program to set the IRQ for that modem to something
that is not used anywhere on the system, and particularly neither 3 nor
4 (the common ttyS{0,1} IRQs.
In any case, this does not sound like a bug, it sounds like a hardware
configuration issue, so I've marked it as not a bug.
How do I set up ppp to work with MSCHAP? Do I need to recompile the PPP packages or is MSCHAP compiled in? I found out my ISP uses an NT server and I might require MSCHAP. Our ppp package does not currently include MSCHAP support because MSCHAP requires DES encryption, which historically we have not been able to legally export. The README.MSCHAP80 file in the ppp source package includes information on rebuilding pppd with MSCHAP support. However, before you go to the trouble, I'd suggest asking your ISP to enable normal CHAP authentication. If they refuse and you have other options, you may wish to take your business elsewhere. |