It appear from my experiences a similar problem is reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=964139 where options in
ifcfg files are ignored. In addition, the presence of an ifcfg-Profile
file explains why network init behavior differed from options in ifcfg
br0 and slave files.
On 2013-06-08 13:09, flashl@xxxxxxxxxxxxxx wrote:
Greetings all,
I am a long-time Fedora-enthusiast. Long-time as in since Fedora
Core 1. I've always been an early adopter of releases although I've
never officially signed up as a tester.
Switching to my Network-Manager inquiry ... I'm currently using
NM-0.9.8.2-1, kernel 3.9.4-301_x86_64, and bridge-utils-1.5-7. I'm
having difficulties with my bridge configuration although from visual
inspection the bridge and slave's network-scripts appears to be OK.
My problem: the bridge's slave is acquiring the dhcp ipv4 address
from the isp instead of the bridge and when issuing a "brctl show"
there is no slave interface attached. This behavior is not what's in
system interface files (ifcfg). In particular, the interface file for
bridge contains: BOOTPROTO=dhcp, ONBOOT=yes, the slave's interface
file contains: ONBOOT=no and slave's Bridge UUID matches UUID in
bridge-interface file. Ifconfig output shows bridge (br0) is up and
slave (p1p1) up with ipv4 ip.
Can someone give me a nudge into right the direction or share
troubleshooting tools to resolve this behavior?
Thanks in advance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
