Bug 85385
| Summary: | ippp0 isdn connection not terminated after timeout | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | drcbusch <carsten> |
| Component: | isdn4k-utils | Assignee: | Than Ngo <than> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | FC5 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-05-02 12:50:52 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 125273 | ||
do you have dial-on-demand activated? If so, the line will come up again, if you check for the status... no, I have not enabled dial on demand Best regards Carsten I assume i's fixed in current release. Please reassign it to FC5 if it still appears. Thanks |
Description of problem: my ippp0 network device is configured to hangup after an idle time of 600 seconds. In the network devices control /usr/bin/neat-control the status of ippp0 changes in fact from "activated" to "deactivated" after this time. But in spite of this the ppp isdn connection is really still active! So I am connected to my ISP longer than wanted without recognizing that. Version-Release number of selected component (if applicable): Redhat Linux 8.0, AVM Fritzcard! PCI ISDN Adapter How reproducible: Steps to Reproduce: 0. under network configuration, configure a timeout for ippp0 of 600 seconds 1. run /usr/bin/neat-control 2. activate the ippp0 network device (i. e. dial the ISP via ISDN) 3. after the connection has been established, wait for the time out 4. with /usr/bin/neat-control still open, watch the status of ippp0 changing from activated to deactivated 5. send data over ippp0 to the internet or look at the network configuration or close and restart /usr/bin/neat-control and you will find that ippp0 is still activated Actual results: after the timeout ippp0 is still activated, the isdn connection is not closed Expected results: hang up isdn connection after timeout for ippp0 Additional info: