Bug 1229560 - No network configuration for MULTIPLE Internet connections (multiple ISPs, etc.)
Summary: No network configuration for MULTIPLE Internet connections (multiple ISPs, etc.)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: networking-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stephen Wadeley
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-09 05:32 UTC by Răzvan Sandu
Modified: 2019-11-07 15:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-07 15:29:41 UTC


Attachments (Terms of Use)

Description Răzvan Sandu 2015-06-09 05:32:35 UTC
Description of problem:

Reading Fedora Networking Guide and other pieces of official documentation, there is no description of a scenario in which a box is connected to the Internet via *multiple* connections (multiple providers?) and a completely *automatic* failover between these connections is sought.

Please see:

http://docs.fedoraproject.org/en-US/Fedora/22/html/Networking_Guide/ch-Configure_Networking.html


Version-Release number of selected component (if applicable):

Fedora 22 Networking Guide Edition 1.0, as of June 9th, 2015.


Actual results:

There is no official documentation about automatical failover between multiple Internet connections, using NetworkManager or not.

Expected results:

Such official documentation should exist, for both Fedora and Red Hat Enterprise Linux (especially regarding the scenario in which the Fedora box is used as an Internet gateway/router, which is very common... almost a FAQ...).

Additional info:

http://lartc.org/lartc.html#LARTC.RPDB.MULTIPLE-LINKS

Comment 1 Stephen Wadeley 2015-06-09 08:30:26 UTC
Hello Răzvan

Thank you for raising this bug.

Comment 2 Petr Bokoc 2019-11-07 15:29:41 UTC
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.


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