(added more use cases) |
(adding date time to relate to thread) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
== Activate network on boot without user assistance == | == Activate network on boot without user assistance == | ||
Pulled from the mailing list as of 2008-10-22 04:10 UTC | |||
'''Status:''' new | '''Status:''' new | ||
| Line 64: | Line 66: | ||
Allow easy bridging of networks through NetworkManager, enabling and disabling them as necessary as networks start and stop. Also, allow simple 'one-click' sharing of one network with one or more other networks. | Allow easy bridging of networks through NetworkManager, enabling and disabling them as necessary as networks start and stop. Also, allow simple 'one-click' sharing of one network with one or more other networks. | ||
== Network Profiles == | |||
'''Status:''' new | |||
NetworkManager lacks support for networking profiles. With networking scripts it had been possible to specify a kernel boot | |||
parameter to switch between different network setups. | |||
= Notes = | |||
None yet. | |||
= References = | |||
# https://www.redhat.com/archives/fedora-list/2008-October/msg02019.html | |||
Latest revision as of 04:10, 23 October 2008
Summary
There is an apparent consensus that NetworkManager is feature incomplete, with several current deficiencies. However, NetworkManager looks to be the way forward for flexible networking in Fedora.
With that in mind, this page attempt to enumerate and detail use cases which NetworkManager either fails completely to resolve, or does not resolve adequately.
Statuses:
- new -- not yet addressed at all
Unresolved Use Cases
Activate network on boot without user assistance
Pulled from the mailing list as of 2008-10-22 04:10 UTC
Status: new
Several services require a working network on boot. There needs to be away to use NetworkManager and have any network setup supported also be able to start on boot.
Fixed IP even though DHCP is available
Status: new
Switching between auto and static IP configuration is either unworkable on the procedure to do it unclear.
Run user scripts as expected
Status: new
NetworkManager should respect and execute user scripts from the standard location or define and document an alternative to executing such scripts.
Automatic mounting/unmounting
Status: new
Have NetworkManager unmount network filesystems as networks go down, and mount them as they go up. This could be entirely automated, or the user could be allowed to associate a network filesystem with one or more networks.
Auto start VPNs (with hooks)
Status: new
On the start of a network VPNs associated with it should be automatically started. Ideally, user defined post scripts could hook into the process before and after a VPN is started/stopped.
Prioritize and override networks based on availability
Status: new
Bugs: 454955
Use networks based on availability and precedence. For example, when a wired connection is plugged in, disable an existing wireless connection. There may be no reliable way to automate this, so this should at least be user configurable.
Cooperate with resolv.conf instead of overriding
Status: new
A user should be able to either specify there own resolv.conf setting per network or instruct NetworkManager to leave resolv.conf alone globally, or for a given network.
Allow starting of network without configuration
Status: new
Some people need to have NetworkManager only bring up an interface, and leave all follow configuration of the interface to a user defined script. One example of this is a network where multiple routes are available, so the user will want to define their own routes. Currently, NetworkManager overrides user defined routes when a network starts.
Simple bridging and sharing
Status: new
Allow easy bridging of networks through NetworkManager, enabling and disabling them as necessary as networks start and stop. Also, allow simple 'one-click' sharing of one network with one or more other networks.
Network Profiles
Status: new
NetworkManager lacks support for networking profiles. With networking scripts it had been possible to specify a kernel boot parameter to switch between different network setups.
Notes
None yet.