Bug 3640 – linuxconf generated ppp chat script incompatible with IBM Global Network

Bug 3640 - linuxconf generated ppp chat script incompatible with IBM Global Network

Summary:	linuxconf generated ppp chat script incompatible with IBM Global Network

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	linuxconf (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-06-22 14:20 EDT by jzeiger
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-07-13 12:15:35 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description jzeiger 1999-06-22 14:20:54 EDT

I configured a ppp connection using linuxconf for
connecting to the IBM/ATT Global Network Internet
service provider (www.ibm.net).  The chat script
it generates has the line: "CONNECT" "".  This
causes a carriage return to be sent to the ISP which
prevents PPP from working with this particular
ISP.  If I delete the trailing "" or replace it
with "\c" the connection comes up just fine.  It
would be nice if there was an option on linuxconf
to suppress the carriage return after a connect.

Comment 1 Michael K. Johnson 1999-07-13 12:15:59 EDT

If we added a separate checkbox option to linuxconf's chat script
generation for every possible brokenness from every possible
provider, we would have too many checkboxes to navigate...

Instead, we're working on a more general solution that we hope
will work for more people without clicking any checkboxes at
all.

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