Bug 14620

Summary:	Fatal pppd authentication error connected to MUD clients
Product:	[Retired] Red Hat Linux	Reporter:	A. mcleod <amcleod>
Component:	ppp	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	amcleod
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:	2000-07-25 15:48:19 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 A. mcleod 2000-07-25 15:48:17 UTC

Hi,

I'm running an Athlon 750Mhz, and connecting to my ISP with a Practical 
Peripherals PM288MT II V.34.  Red Hat installed fine, and on first running pppd 
works flawlessly (pppd /dev/modem defaultroute crtscts).  However, when I run 
any version of TinyFugue (available at tf.tcp.com), or Trebuchet (available at 
belfry.com), they do something to the system.  Whatever they do, it prevents 
pppd from connecting again.  The modem handshakes succesfully, and when the 
pppd command line is entered, it immidiately dies, reporting that I am "not 
authorized to use <dynamic IP assigned to me>".  Running pppd with the noauth 
option just makes the connection hang.  Installing and running these programs 
as a user and not root does no good.  Extracting, compiling, saving the 
executable, reformatting, reinstalling Linux, then running the executable also 
does no good-- Implying that untarring and compiling do not do the fatal 
action.  

Any thoughts?

AM

Comment 1 A. mcleod 2000-07-25 16:20:29 UTC

Fixed by adding noauth to /etc/ppp/options file.  Apologies for inconvinience.