Bug 717899

Summary: Firefox starts in offline mode while interfaces are not being managed by NetworkManager
Product: Red Hat Enterprise Linux 6 Reporter: Lubos Kocman <lkocman>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: bugzillaredhat-56f0, jones.peter.busi, rkhan, skrishna, stransky
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-19 18:22:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 718928    
Bug Blocks:    

Description Lubos Kocman 2011-06-30 11:16:07 UTC
Description of problem:

Hello,

I'm using bridged interface which is not managed by NM. The problem is that firefox somehow starts always in offline mode. And I need to turn it on manually.

Version-Release number of selected component (if applicable):

firefox-3.6.17-1.el6_0.x86_64
NetworkManager-0.8.1-9.el6.x86_64

How reproducible:


Steps to Reproduce:
1. set up networking according to (Additional info)
2. pkill -9 firefox # make sure there is no instance running
3. firefox
  
Actual results:

firefox starts in offline mode


Expected results:

firefox should not start in offline mode


Additional info:

/sbin/chkconfig | grep -i network
NetworkManager 	0:off	1:off	2:on	3:on	4:on	5:on	6:off
network        	0:off	1:off	2:on	3:on	4:on	5:on	6:off



cat /etc/sysconfig/network-scripts/ifcfg-{eth0,br0}
DEVICE="eth0"
BOOTPROTO="none"
HWADDR="00:22:68:11:53:67"
NM_CONTROLLED="no"
ONBOOT="yes"
BRIDGE="br0"

DEVICE=br0
TYPE=Bridge
ONBOOT=no
BOOTPROTO=dhcp
DELAY=0

sudo /sbin/ifconfig -a # Interfaces tapn are probably not relevant
br0       Link encap:Ethernet  HWaddr 00:22:68:11:53:67  
          inet addr:10.34.29.98  Bcast:10.34.29.255  Mask:255.255.254.0
          inet6 addr: 2620:52:0:221d:222:68ff:fe11:5367/64 Scope:Global
          inet6 addr: fe80::222:68ff:fe11:5367/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:108564 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16442 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:22902649 (21.8 MiB)  TX bytes:2332584 (2.2 MiB)

eth0      Link encap:Ethernet  HWaddr 00:22:68:11:53:67  
          inet6 addr: fe80::222:68ff:fe11:5367/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:456861 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83474 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:543683016 (518.4 MiB)  TX bytes:10394877 (9.9 MiB)
          Interrupt:20 Memory:fc000000-fc020000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:57839 errors:0 dropped:0 overruns:0 frame:0
          TX packets:57839 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:78177757 (74.5 MiB)  TX bytes:78177757 (74.5 MiB)

pan0      Link encap:Ethernet  HWaddr B2:CA:B4:D4:45:70  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tap3      Link encap:Ethernet  HWaddr C2:2D:25:E2:16:93  
          inet6 addr: fe80::c02d:25ff:fee2:1693/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:38390 errors:0 dropped:0 overruns:0 frame:0
          TX packets:289769 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:4730199 (4.5 MiB)  TX bytes:324259107 (309.2 MiB)

tap4      Link encap:Ethernet  HWaddr B2:4B:9E:A0:A1:A5  
          inet6 addr: fe80::b04b:9eff:fea0:a1a5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:28537 errors:0 dropped:0 overruns:0 frame:0
          TX packets:212113 errors:0 dropped:2 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:3326856 (3.1 MiB)  TX bytes:209901212 (200.1 MiB)

virbr0    Link encap:Ethernet  HWaddr 52:54:00:DB:2F:74  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:3938 (3.8 KiB)

virbr0-nic Link encap:Ethernet  HWaddr 52:54:00:DB:2F:74  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:1E:65:32:A7:E8  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


ping redhat.com
PING redhat.com (10.4.127.15) 56(84) bytes of data.
64 bytes from 10.4.127.15: icmp_seq=1 ttl=123 time=170 ms
...

Comment 1 Roberto Ragusa 2011-07-05 08:00:24 UTC
The same happens with pidgin.

It is a problem with NetworkManager, see bug #718928.

Comment 2 Roberto Ragusa 2011-07-05 08:02:14 UTC
Confirmed on Fedora 14 too.

Comment 3 Suzanne Logcher 2011-10-06 18:50:45 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
               
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 Dan Williams 2013-02-19 18:22:51 UTC
This is not going to be fixed in RHEL6, but will be better in later RHEL releases.