F9 potential service network bug?

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

 



Hi,
I have setup VirtualBox, and set up its bridged networking. The weird part is that somehow the bridge and my eth0 (sky2) were not being brought up on system start! I thought maybe it was NetworkManager weirdness, so I disabled that service. Now here is what happens:

- Upon system start, I only get the following NICs: lo, vbox0
- If I immediately issue a "service network restart", I get the following NICs: eth0, vboxbr0, vbox0, lo

Obviously, since nothing changed that a possible bug! Here are my relevant ifcfg files

[root@magic1 network-scripts]# cat ifcfg-eth0
# Marvell Technology Group Ltd. 88E8036 PCI-E Fast Ethernet Controller
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:a0:d1:2c:c6:08
>SEARCH="example.com"
NM_CONTROLLED=no
TYPE=Ethernet
BRIDGE=vboxbr0
[root@magic1 network-scripts]# cat ifcfg-vboxbr0
DEVICE=vboxbr0
TYPE=Bridge
BROADCAST=192.168.10.255
IPADDR=192.168.0.254
NETMASK=255.255.255.0
NETWORK=192.168.0.0
>NM_CONTROLLED=no


-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux