Bug 1032819

Summary: broadcast address not configured
Product: [Fedora] Fedora Reporter: Louis Lagendijk <louis>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 20CC: awilliam, dcbw, dopey, raad_orfali, rstonehouse, samuel-rhbugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: NetworkManager-0.9.9.0-22.git20131003.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1034900 (view as bug list) Environment:
Last Closed: 2013-12-22 05:36:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Louis Lagendijk 2013-11-20 22:39:16 UTC
Description of problem:
The broadcast address is not set on my interfaces. After system start my interfaces have 0.0.0.0 as broadcast address

Version-Release number of selected component (if applicable):
F20 with all updates installed as of 2013-11-20

How reproducible:


Steps to Reproduce:
1.Start the system
2. in a terminal type: ifconfig p5p1


Actual results:
Broadcast address set to 0.0.0.0

Expected results:
Broadcast address set (for my 192.168.159.3 address: 192.168.159.255)

Additional info:
This issue occurs on my desktop system that has been installed with one of the TC's for Alpha, but I now see the same on my laptop that I installed with Fedora 20 Beta

Comment 1 Louis Lagendijk 2013-11-20 22:41:39 UTC
This issue occurs on the ethernet interfaces as well on the WLan on the laptop

Comment 2 Dan Williams 2013-12-03 20:25:37 UTC
upstream commit 7eb12a5b21f87d7592ec2c5235d1ed90c4fac132

Comment 3 Andy Wang 2013-12-18 16:47:06 UTC
Is there a workaround for this issue short of manually configuring broadcast via ifconfig?  I have a few scenarios where broadcast needs to work properly.

Comment 4 Fedora Update System 2013-12-18 20:16:37 UTC
NetworkManager-0.9.9.0-21.git20131003.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/NetworkManager-0.9.9.0-21.git20131003.fc20

Comment 5 Fedora Update System 2013-12-20 01:35:08 UTC
Package NetworkManager-0.9.9.0-21.git20131003.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.9.0-21.git20131003.fc20'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-23593/NetworkManager-0.9.9.0-21.git20131003.fc20
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-12-20 03:03:23 UTC
NetworkManager-0.9.9.0-22.git20131003.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/NetworkManager-0.9.9.0-22.git20131003.fc20

Comment 7 Andy Wang 2013-12-20 16:00:01 UTC
Woo hoo.  Fix worked for me.

Comment 8 Fedora Update System 2013-12-22 05:36:34 UTC
NetworkManager-0.9.9.0-22.git20131003.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Thomas Woerner 2014-01-10 13:29:58 UTC
*** Bug 1038959 has been marked as a duplicate of this bug. ***

Comment 10 raad.orfali 2014-01-23 14:11:10 UTC
I have the NetworkManager-0.9.9.0-22.git20131003.fc20 version but I am still cannot access shared file only after disabling the firewall