Hide Forgot
Description of problem: After I suspend my PC and then resume the networking ins't fully restored. I have a bridge device. I am *not* using network manager. For a workaround I can use a static IP but this isn't desireable. Version-Release number of selected component (if applicable): kernel 3.1.1-2.fc16.x86_64 bridge-utils-1.5-2 avahi-0.6.30-4 dhclient-4.2.3-3 How reproducible: 100% Steps to Reproduce: 1. Ensure that networking is fully functional with bridge working 2. suspend 3. resume Actual results: ifconfig br0 returns the following: Link encap:Ethernet HWaddr 48:5B:39:96:A4:90 inet6 addr: fe80::fc54:ff:fe3d:34e7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:20510 errors:0 dropped:0 overruns:0 frame:0 TX packets:17159 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:15064995 (14.3 MiB) TX bytes:7601165 (7.2 MiB) Notice that there is no ip4 ipaddress in the result Expected results: I expect the br0 interface to have an IP address Additional info: The system log has the following information which may be relevant: ov 21 23:30:06 localhost dhclient[6609]: DHCPREQUEST on br0 to 255.255.255.255 port 67 Nov 21 23:30:07 localhost avahi-daemon[1042]: Registering new address record for fe80::fc54:ff:fe3d:34e7 on br0.*. Nov 21 23:30:13 localhost dhclient[6609]: DHCPREQUEST on br0 to 255.255.255.255 port 67 Nov 21 23:30:32 localhost dhclient[6609]: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 7 Nov 21 23:30:39 localhost dhclient[6609]: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 8 Nov 21 23:30:47 localhost dhclient[6609]: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 10 Nov 21 23:30:57 localhost dhclient[6609]: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 19 Nov 21 23:31:16 localhost dhclient[6609]: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 17 Nov 21 23:31:33 localhost dhclient[6609]: No DHCPOFFERS received. Nov 21 23:31:33 localhost dhclient[6609]: Trying recorded lease 192.168.1.115 Nov 21 23:31:33 localhost avahi-daemon[1042]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.115. Nov 21 23:31:33 localhost avahi-daemon[1042]: New relevant interface br0.IPv4 for mDNS. Nov 21 23:31:33 localhost avahi-daemon[1042]: Registering new address record for 192.168.1.115 on br0.IPv4. Nov 21 23:31:36 localhost avahi-daemon[1042]: Withdrawing address record for 192.168.1.115 on br0. Nov 21 23:31:36 localhost avahi-daemon[1042]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.115. Nov 21 23:31:36 localhost avahi-daemon[1042]: Interface br0.IPv4 no longer relevant for mDNS. Nov 21 23:31:36 localhost kernel: [ 3513.725548] r8169 0000:03:00.0: p10p1: link down Nov 21 23:31:36 localhost kernel: [ 3513.725562] r8169 0000:03:00.0: p10p1: link down Nov 21 23:31:36 localhost kernel: [ 3513.726409] ADDRCONF(NETDEV_UP): p10p1: link is not ready The file /etc/sysconfig/network-scripts/ifcfg-p10p1 has the following content: DEVICE=p10p1 HWADDR=48:5B:39:96:A4:90 ONBOOT=yes BRIDGE=br0 NM_CONTROLLED=no The file /etc/sysconfig/network-scripts/ifcfg-br0 has the following content: DEVICE=br0 TYPE=Bridge BOOTPROTO=dhcp ONBOOT=yes DELAY=0 NM_CONTROLLED=no
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is 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" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.