Apologies. The default is dhclient, apparently.
Any help diagnosing this would be good, though.
-Original Message-
From: "dpr...@deepplum.com"
Sent: Tuesday, January 2, 2018 4:28pm
To: "Mleman"
Cc: networkmanager-list@gnome.org
Subject: Re: Internal dhcp unable to acquire IP from certa
I am having a similar problem with NM's internal dhcp client on Fedora 27. I
don't have the problem on various Macbook Pros or other servers. The Fedora
client is a desktop machine that implements a bridged config - br0 is the
interface, eth0 is the slave - I don't know if that matters, but NM
Hi Thomas,
On Tue, Jan 2, 2018 at 10:19 AM, Thomas Haller wrote:
> On Fri, 2017-12-29 at 23:27 +0100, Belisko Marek wrote:
>> Hi,
>>
>> I'm trying to use networkmanager with some embedded project and I
>> would like to avoid autoconnect to wifi after device bootup when
>> system-connection is set
Thomas,
thank you for your reply. I will report to the distro maintainers
regarding their compilation defaults.
As for the non-working DHCP handshake, I did as advised and generated a
log with level=TRACE and pasted it on https://pastebin.com/qTbDWJb1
Some details:
Log was generated on Man
On Sun, 2017-12-24 at 14:52 +0100, Iñigo Martínez wrote:
> The install directories of those targets that match the default
> install directories have been removed because they are redundant.
>
> This also allows a simple meson build files and it is unnecessary
> to create some paths.
Hi,
both p
On Fri, 2017-12-29 at 23:27 +0100, Belisko Marek wrote:
> Hi,
>
> I'm trying to use networkmanager with some embedded project and I
> would like to avoid autoconnect to wifi after device bootup when
> system-connection is set previously. I tried to look for config files
> but seems I cannot find s
Hi,
On Sat, 2017-12-30 at 17:27 +0100, Mleman wrote:
> NetworkManager 1.10 introduced a breaking change by making
> dhcp=internal
> the default instead of dhclient. Many distros pushed out NM 1.10
> obviously without being aware of that change. Lots of users are
> reporting issues with their wi
On Tue, 2018-01-02 at 00:01 +0100, Sander Smid-Merlijn wrote:
> Hi,
>
> I'm new to this mainling list so forgive me if I'm asking things that
> have been answered here before. To connect to my companies network I
> use
> the openfortivpn which implements Fortigate SSL VPN solution. There
> is a
>
On Thu, 2017-12-28 at 10:35 +, Guillaume Betous wrote:
> Hi,
>
> I have an openvpn setup which works fine on command-line. I have a
> single file which contains inline keys.
>
> When I try to import it on network-manager (not sure of the version,
> but I run Ubuntu 17.10), I have an error wit
On Thu, 2017-12-28 at 15:00 +0100, Manuel Schölling wrote:
> Hi,
>
> I am currently developing a wireguard VPN plugin [1] for
> NetworkManager.
> I am wondering how the device configuration works for VPN devices.
>
> You can get the IP settings using
> nm_connection_get_setting_ip4_config(). It i
NetworkManager 1.10 introduced a breaking change by making dhcp=internal
the default instead of dhclient. Many distros pushed out NM 1.10
obviously without being aware of that change. Lots of users are
reporting issues with their wifi connection etc. in support forums and
lots of guesswork is h
11 matches
Mail list logo
