Re: NetworkManager won't become "active"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/08/2011 06:13 PM, Alex wrote:
> Hi,
>
> I just rebooted my FC14 x86_64 desktop, and there's no networking. I
> have a bridge set up with eth0, and despite my best efforts, can't get
> eth0 to be "active" in "Network Device Control". The activate/deactive
> buttons are greyed out.
>
> At one point I was able to click Activate, but even then it wouldn't
> actually activate it. For now, I've just run "ifup br0" and it
> successfully acquired a DHCP address.
>
> I've tried variations of "Controlled by NetworkManager" and other
> ideas I've read in similar threads (mostly from a few years ago), with
> no success.
>
> Here are the contents of /etc/sysconfig/networking/devices
>
> ifcfg-eth0:
> DEVICE=eth0
> HWADDR=48:5b:XX:61:b5:5c
> ONBOOT=yes
> BRIDGE=br0
> BOOTPROTO=dhcp
> TYPE=Ethernet
> NM_CONTROLLED=yes
> USERCTL=yes
> PEERDNS=yes
> IPV6INIT=no
>
> ifcfg-br0:
> DEVICE=br0
> TYPE=Bridge
> BOOTPROTO=dhcp
> ONBOOT=yes
> DELAY=0
> IPV6INIT=no
> USERCTL=yes
>
> There are a few syslog entries in messages that might help:
>
> Jan  8 17:55:06 alex NetworkManager[17711]:<error>
> [1294527306.847724] [nm-dbus-manager.c:338]
> nm_dbus_manager_start_service(): Could not acquire
>   the NetworkManager service as it is already taken.
> Jan  8 17:55:06 alex NetworkManager[17711]:<error>
> [1294527306.847745] [main.c:709] main(): failed to start the dbus
> service.
> Jan  8 17:55:06 alex NetworkManager[17711]:<info>  exiting (error)
> Jan  8 17:55:20 alex NetworkManager[17051]:<info>  caught signal 15,
> shutting down normally.
> Jan  8 17:55:20 alex NetworkManager[17051]:<info>  exiting (success)
> Jan  8 17:56:08 alex NetworkManager[18096]:    ifcfg-rh: Acquired
> D-Bus service com.redhat.ifcfgrh1
> Jan  8 17:56:08 alex NetworkManager[18096]:    ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-lo ...
> Jan  8 17:56:08 alex NetworkManager[18096]:    ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-br0 ...
> Jan  8 17:56:08 alex NetworkManager[18096]:    ifcfg-rh:     error:
> Bridge connections are not yet supported
> Jan  8 17:56:08 alex NetworkManager[18096]:    ifcfg-rh: parsing
> /etc/sysconfig/network-scripts/ifcfg-eth0 ...
> Jan  8 17:56:08 alex NetworkManager[18096]:    ifcfg-rh:     read
> connection 'System eth0'
> Jan  8 17:56:08 alex NetworkManager[18096]:    ifcfg-rh: Ignoring
> connection 'System eth0' and its device due to
> NM_CONTROLLED/BRIDGE/VLAN.
> Jan  8 17:56:08 alex NetworkManager[18096]:<info>  (eth0): carrier is OFF
> Jan  8 17:56:08 alex NetworkManager[18096]:<info>  (eth0): new
> Ethernet device (driver: 'sky2' ifindex: 2)
> Jan  8 17:56:08 alex NetworkManager[18096]:<warn>
> /sys/devices/virtual/net/br0: couldn't determine device driver;
> ignoring...
> Jan  8 17:56:08 alex NetworkManager[18096]:<warn>
> /sys/devices/virtual/net/virbr0: couldn't determine device driver;
> ignoring...
> Jan  8 17:56:08 alex NetworkManager[18096]:<warn>
> /sys/devices/virtual/net/vnet0: couldn't determine device driver;
> ignoring...
> ...
> Jan  8 18:00:16 alex system-config-network[21112]: Error: Bridge not
> in DeviceFactory!
>
> I hope that's legible. What does that mean? Trying to restart the dbus service:
>
> [root@alex network-scripts]# ps ax|grep dbus
>   1296 ?        Ssl    0:14 dbus-daemon --system
>   2225 ?        S      0:00 dbus-launch --sh-syntax --exit-with-session
>   2226 ?        Ssl    0:00 /bin/dbus-daemon --fork --print-pid 5
> --print-address 7 --session
>   2555 ?        S      0:00 dbus-launch
> --autolaunch=a399d32027353da4091b58ae0000000c --binary-syntax
> --close-stderr
>   2556 ?        Ssl    0:00 /bin/dbus-daemon --fork --print-pid 5
> --print-address 7 --session
> 24684 pts/2    S+     0:00 grep --color=auto dbus
> [root@alex network-scripts]# service dbus restart
> Redirecting to /bin/systemctl  restart dbus.service
> Failed to get D-Bus connection: Failed to connect to socket
> /org/freedesktop/systemd1/private: Connection refused
>
> There is also a computer with a red X in the top panel.
>
> Where can I find a good overview of how this all works and interacts
> with udev? I would like to learn everything about it eventually, but
> for now where can I learn the basics about how it makes decisions on
> how the networking works?
>
> Thanks,
> Alex
Hey Alex,

There's an excellent article on bridging and related topics in an article:

VLAN Support in Linux by Henry Van Styn Linux Journal January 2011 Page 54.

Hope this helps.

Mark LaPierre
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux