On Mon, 3 Sep 2018 12:54:30 +0200 Arian Sanusi
wrote:
> to put my paint point first, maybe it was not clear: at boot NM does not
> connect at boot to a WiFi. Instead I have to click the applet, wait multiple
> seconds for a scan to finish and then have to choose the wifi manually. NM
> says
to put my paint point first, maybe it was not clear: at boot NM does not
connect at boot to a WiFi. Instead I have to click the applet, wait multiple
seconds for a scan to finish and then have to choose the wifi manually. NM says
it would be connected to my bridge, see attached screenshot.
> I
On 9/2/18 00:43, Michael Biebl wrote:
> On 9/1/18 23:58, Arian Sanusi wrote:
>> I have these interfaces:
>> "bridge": a bridge without any ports connected on start, LXCs connect here.
>> It's configured in /etc/network/interfaces, and I expect NM not to touch it
>> "mlan0": wifi, not in
On 9/1/18 23:58, Arian Sanusi wrote:
> I have these interfaces:
> "bridge": a bridge without any ports connected on start, LXCs connect here.
> It's configured in /etc/network/interfaces, and I expect NM not to touch it
> "mlan0": wifi, not in interfaces, expected to be handled by NM
> "lo": for
I have these interfaces:
"bridge": a bridge without any ports connected on start, LXCs connect here.
It's configured in /etc/network/interfaces, and I expect NM not to touch it
"mlan0": wifi, not in interfaces, expected to be handled by NM
"lo": for completeness sake
"eth0": not alway there
On 9/1/18 12:05, Arian Sanusi wrote:
> Package: network-manager
> Version: 1.12.2-2
> Severity: normal
>
> Dear Maintainer,
>
> I have a bridge configured by ifupdown in /etc/network/interfaces. Even
> though NetworkManager.conf contains:
> [ifupdown]
> managed=false
>
> at boot
6 matches
Mail list logo
