Re: Ensuring predictable MAC address for bond interface

2014-10-07 Thread Dan Williams
On Mon, 2014-10-06 at 12:51 -0700, Ed Swierk wrote: I'm using NetworkManager on a server with two wired Ethernet interfaces (eth0 and eth1) configured as slaves of a bond in active-backup mode. I'd like the bond interface to always be assigned eth0's MAC address. This is easy with old-school

Re: Link MTU option ignored in IPv6 router advertisements

2014-10-07 Thread Chuck Anderson
Thanks, bug filed: https://bugzilla.gnome.org/show_bug.cgi?id=738104 On Fri, Oct 03, 2014 at 12:01:38PM -0500, Dan Williams wrote: On Fri, 2014-10-03 at 11:36 -0400, Chuck Anderson wrote: I'm not sure if this is a kernel thing or a NetworkManager thing. Did something change in how IPv6

[MM PATCH] port-serial: fix forced closing after b28230411

2014-10-07 Thread Dan Williams
b28230411 moved up the self-priv-forced_close = TRUE, which caused mm_port_serial_close() to just return without actually closing the port and cleaning up. Also, cancel the reopen separately from closing the port since the two operations are actually independent of each other. ---

Ad-Hoc network creation took too long, failing activation

2014-10-07 Thread poma
Starting Network Manager... info NetworkManager (version 0.9.10.0-5.git20140704.fc21) is starting... info WEXT support is enabled info WiFi hardware radio set enabled info Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so info WiFi enabled by radio killswitch; enabled by

Re: [MM PATCH] port-serial: fix forced closing after b28230411

2014-10-07 Thread Aleksander Morgado
On Tue, Oct 7, 2014 at 11:06 PM, Dan Williams d...@redhat.com wrote: b28230411 moved up the self-priv-forced_close = TRUE, which caused mm_port_serial_close() to just return without actually closing the port and cleaning up. Also, cancel the reopen separately from closing the port since the

Re: Ensuring predictable MAC address for bond interface

2014-10-07 Thread Ed Swierk
For these experiments I upgraded to NetworkManager 0.9.10.0. I tried setting primary=eth0 in the bond options. This option has an effect in only one case: if I start with only eth1 plugged in (i.e. carrier up), and then plug in eth0, the bond driver will switch the active slave from eth1 to eth0