Bug 607989
| Summary: | RFE: NetworkManager should detect network address conflicts | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ferry Huberts <mailings> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | dcbw, psimerda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-12-14 14:41:04 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
Ferry Huberts
2010-06-25 11:12:17 UTC
Dan, I'd love to see this in F15 :-) ping “This is a usability issue.“ This is probably a good idea but NM has so many more important issues that I don't belive this is a priority now. But a warning application could probably be prototyped separately from NetworkManager. BTW, it is not very useful to bother non-expert users with decisions like that, so NM would have to act automatically either by stopping the older of the conflicting connections or at least prioritize the new one for routing. My whole point is that this is something that can be handled by _any_ user very easily: NM has detected that network X and network Y will not function correctly when active simultaneously, what do you want to do? 1- use network X 2- use network Y how easy is that? ;-) “how easy is that? ;-)” I understand you but I don't think it's a good idea to interrupt the user and make him decide, if it's not absolutely necessary. NetworkManager should work without user interaction, and even has to work on servers. Even on desktop/laptop, it is better if the networking “just works”. In some environments user network configuration may be even disabled. agree. then don't do this in the core, but in the gnome applet :-) or allow something like a plugin to handle this through some sort of callback/notification. you could then have interactive (desktop), noop (servers), etc. handlers. “or allow something like a plugin to handle this through some sort of callback/notification.” It could be, and it could be even configurable. I suggest moving this request in the Gnome bugzilla. As you can see, it's here since 2010. But it may happen there too, as NM needs work in many areas. |