On Mon, 28 Sep 2015 09:05:02 +0200
Olaf Hering wrote:
> I'm running openSUSE Tumbleweed, with GNOME 3.16.2 and NM 1.0.6, and
> have odd issues with networking.
>
> Initially GNOME automatically configured the onboard ethernet and
> named it "Wired Connection 1". I added a few
On Mon, 28 Sep 2015 19:18:12 +0200
Olaf Hering wrote:
> Am 28.09.2015 um 09:05 schrieb Olaf Hering:
> > connection.autoconnect-slaves: -1 (default)
>
> Did I miss that knob in the GUI? Setting it to 1 with
> "nmcli connection edit bridge" seems to fix the "up" command.
Hi,
I've got an esoteric NM question. I've got two distinct networks that
share an ethernet fabric (poor man's vlans). I have a F22 server that I
want to put on both networks. It's currently configured to use DHCP for
the primary network (and my DHCP server provides a static address).
AFAICT
29.09.2015 20:54, Dan Williams пишет:
Basically I want to automate NM doing, effectively:
ifconfig eth0:0 192.168.x.y
Don't do this with interface aliases; the kernel is perfectly capable of
using more than one address on the same interface. Simply do:
ip addr add 192.168.x.y/24 dev
Hey guys!
I'm using Ubuntu 14.04 LTS, and using the applet I am able to do basic
configuration of an AP. I can then start it, connect to it, and use it.
But this base config is very simplistic. I need something more. I need
Radius server authentication, and VLANs. (Things that are
On Tue, 2015-09-29 at 12:16 -0400, Derek Atkins wrote:
> Hi,
>
> I've got an esoteric NM question. I've got two distinct networks that
> share an ethernet fabric (poor man's vlans). I have a F22 server that I
> want to put on both networks. It's currently configured to use DHCP for
> the