Bug 98761 - Software flow control (XON/XOFF) not work !
Summary: Software flow control (XON/XOFF) not work !
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: i386 Linux
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
Whiteboard: bzcl34nup
Depends On:
Blocks: rcn-modem
TreeView+ depends on / blocked
Reported: 2003-07-08 16:55 UTC by MEGASOFT HACKERS GROUP
Modified: 2008-05-06 23:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 23:56:10 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 MEGASOFT HACKERS GROUP 2003-07-08 16:55:36 UTC
I configure my modem as 38400 and Sowtware Flow Control (XON/XOFF) (really this
cellular phone Trium Geo@ via datacable - perfectly work in windows and os/2).
Try activate ppp-interface, but modem don't answer.

After some exploring network scripts i decide what XON/XOFF not supported by
default dialer wvdial (but redhat-config-network GUI set some option in
wvdial.conf - FlowControl:).

How reproducible:

Steps to Reproduce:
1. Any modem device with Software FlowControl (XON/XOFF). For example cellular
phone via simple data-cable (RX/TX)
2. Setup modem and ppp-connection in redhat-config-network
3. Try activate ppp-connection and see system log

Comment 1 Hollis Blanchard 2004-08-12 20:54:25 UTC
FlowControl is not a valid wvdial option, at least not as of wvdial
1.54.0. (I'm looking at the stock source; don't know if Red Hat has
patched it.)

Instead you must put these options into a /etc/ppp/options file:
  asyncmap a0000

But wvdial also passes "crtscts" on the pppd command line; this is
hardcoded. So you must also add the following to a wvdial config file:
  PPPD Option = nocrtscts

This seems to finally disable hardware flow control.

Comment 2 Bug Zapper 2008-04-03 15:28:10 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 3 Bug Zapper 2008-05-06 23:56:08 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

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