Bug 14620 - Fatal pppd authentication error connected to MUD clients
Summary: Fatal pppd authentication error connected to MUD clients
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ppp   
(Show other bugs)
Version: 6.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-07-25 15:41 UTC by A. mcleod
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-07-25 15:48:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description A. mcleod 2000-07-25 15:48:17 UTC

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 

Any thoughts?


Comment 1 A. mcleod 2000-07-25 16:20:29 UTC
Fixed by adding noauth to /etc/ppp/options file.  Apologies for inconvinience.

Note You need to log in before you can comment on or make changes to this bug.