| Summary: | Instruction to disable IPv4 still results in DHCPDISCOVER packets | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Liam Dennehy <liam> | ||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | dcbw, jklimes | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-07 16:02:59 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 515706 [details]
NetworkManager generated ifcfg script for No IPv4 connection
The problem is that you left IPv6 method as "Ignore". That's why when ifcfg-rh plugin reads the connection it sets IPv4 back to "Automatic (DHCP)"; because else there's neither IPv4 nor IPv6 connectivity. So please set IPv6 method to "Automatic", or edit the file to contain IPV6INIT=yes. Actually, there was a change upstream recently that makes "Automatic" as default IPv6 method when creating connections. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
Created attachment 515705 [details] /var/log/messages extract showing DHCP DISCOVERs despite explicitly disabling IPv4 Description of problem: When a connection defined in NetworkManager explicitly disables IPv4, DHCP DISCOVER packets are still transmitted Version-Release number of selected component (if applicable): NetworkManager-0.8.9997-5.git20110702.fc15.i686 How reproducible: Always Steps to Reproduce: 1. Open Network Connections (nm-connection-editor) 2. Remove all configurations for a specific interface (e.g. em1) from nm-connection-editor 3. Create a new connection profile by clicking "Add", e.g. named "No IPv4" 4. Enter the MAC address of the interface, deselect "Connect Automatically" 5. On the "IPv4 Settings" tab select "Disabled" from the "Method" list 6. Save the connection profile 7. Plug in an Ethernet cable 8. Enables the connection from the nm-applet icon, or select it from the list if more than one connection profile is defined for the interface (i.e. step 2 is skipped) Actual results: Once the connection is enabled, DHCP packets are transmitted on the interface Expected results: Absolutely no IPv4 traffic should originate on the interface. The interface config should have a link-local IPv6 address only Additional info: The bug is marked as High severity since it is explicitly the opposite of what should be observed. This configuration is useful for a passive traffic monitor, and any DHCP traffic would interfere with the operation of the observed network, so is unequivocally undesirable.