Bug 14620 - Fatal pppd authentication error connected to MUD clients
Fatal pppd authentication error connected to MUD clients
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: ppp (Show other bugs)
6.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-07-25 11:41 EDT by A. mcleod
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-07-25 11:48:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description A. mcleod 2000-07-25 11:48:17 EDT
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 12:20:29 EDT
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.