NetworkManager Bridges in Fedora

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Tue Jan 21 15:40:13 UTC 2014


On Fri, Jan 17, 2014 at 01:30:31PM +0100, Harald Hoyer wrote:
> On 01/16/2014 08:09 PM, Dan Williams wrote:
> > On Thu, 2014-01-16 at 13:53 -0500, Steve Dickson wrote:
> >> Hello,
> >>
> >> Has anybody had any luck with getting bridges
> >> consistently up in running in either F19 or F20?
> >> I know I have not... 
> >>
> >> I go into setup/networks. Add a bridge which creates 
> >> two file in /etc/sysconfig/network-scripts
> >>
> >> ifcfg-Bridge_connection_1
> >> ifcfg-bridge0_slave_1
> >>
> >> The contents seem reasonable. 
> >>
> >> After I reboot, I go back in to setup/networks. The status
> >> of the bridge is "connecting" and the Bridge slaves
> >> are "none"???
> > 
> > Quick question on that, are both the master and the slave set to
> > "connect automatically?"  Or, in the ifcfg files, is ONBOOT=yes set for
> > both master and slave?
> > 
> > Also, if wouldn't mind passing along the systemd journal output for
> > NetworkManager, that might help us figure out what's going on:
> > 
> > journalctl -b _SYSTEMD_UNIT=NetworkManager.service
> 
> better use
> 
> # journalctl -b -u NetworkManager
> 
> "-u" has the advantage, that you can specify it multiple times with different
> units and get a combined output.
For the record: -u has also other advantages: it includes information
about the unit from systemd (whereas _SYSTEMD_UNIT only looks for messages from
the unit itself), and possibly setroubleshoot and other relevant sources in the
future.

Also, as Harald mentioned, you don't need to specify the .service suffix.

Zbyszek


More information about the devel mailing list