Bug 514

Summary:	ESCAPECHARS effectively always on
Product:	[Retired] Red Hat Linux	Reporter:	Göran Uddeborg <goeran>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.2	CC:	rvokal
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-01-25 13:51:41 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 Göran Uddeborg 1998-12-18 12:29:07 UTC

In ifup-ppp, if ESCAPECHARS is "yes", the flag "asyncmap
FFFFFFF" is added to the options to pppd.  All characters
will be escaped.  So far so good.  If it is not "yes" no
flag is added, no flag is added.  According to the manual
page for pppd "If no asyncmap option is given, no async
character map will be negotiated for the receive direction;
the peer should then escape all control characters."  Which
means all charactars will STILL be escaped.

It appears to me the correct thing to do in ifup-ppp would
be to add "asyncmap 0" if ESCAPECHARS is "no".

Comment 1 David Lawrence 1998-12-18 21:27:59 UTC

This has been assigned to a developer as a change request.

Comment 2 Jeff Johnson 1999-01-25 13:51:59 UTC

Fixed in initscripts 3.83.