Re: Switching to NetworkManager dhcp=internal

2016-10-12 Thread Björn Esser 

Am 12.10.2016 um 20:14 schrieb stan:

On Wed, 12 Oct 2016 13:37:40 -0400
Colin Walters  wrote:


Hey, so as part of the discussion about NetworkManager vs
systemd-networkd, one thing that happened is networkd started
exposing its DHCP code as a shared library, and NetworkManager
learned to use it if one specifies

```
[main]
dhcp=internal
```

in /etc/NetworkManager/NetworkManager.conf.

Did this.  Then turned off the ethernet link and restarted
NetworkManager to pick up the change.  Turned on the ethernet link.


The networkd DHCP code has gotten a fair amount of testing
in server environments, but I suspect it could use more battle
testing in two things:

1) Desktop systems with a wider variety of DHCP environments
   home routers

Success, seems to be working fine (I haven't noticed any problems).
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Looks fine here, too, using Cinnamon, MATE and Gnome 3 Desktops on 
Fedora 25.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Switching to NetworkManager dhcp=internal

2016-10-12 Thread stan 
On Wed, 12 Oct 2016 13:37:40 -0400
Colin Walters  wrote:

> Hey, so as part of the discussion about NetworkManager vs
> systemd-networkd, one thing that happened is networkd started
> exposing its DHCP code as a shared library, and NetworkManager
> learned to use it if one specifies
> 
> ```
> [main]
> dhcp=internal
> ```
> 
> in /etc/NetworkManager/NetworkManager.conf.

Did this.  Then turned off the ethernet link and restarted
NetworkManager to pick up the change.  Turned on the ethernet link.

> The networkd DHCP code has gotten a fair amount of testing
> in server environments, but I suspect it could use more battle
> testing in two things:
> 
> 1) Desktop systems with a wider variety of DHCP environments
>   home routers

Success, seems to be working fine (I haven't noticed any problems).
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Switching to NetworkManager dhcp=internal

2016-10-12 Thread Matthew Miller 
On Wed, Oct 12, 2016 at 01:37:40PM -0400, Colin Walters wrote:
> And anyways, I don't see a reason not to do this across the board,
> hence this thread.

+1


> The networkd DHCP code has gotten a fair amount of testing
> in server environments, but I suspect it could use more battle
> testing in two things:
> 1) Desktop systems with a wider variety of DHCP environments (from
>   home routers, enterprise environments with unusual DHCP servers)

For one very small data point: I changed my laptop to use internal as
soon as I discovered it was an option (I dunno when exactly; more than
a year ago I think) and have not ever experienced any trouble. in > 2)
Cases where one wants to propagate various config options

-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Switching to NetworkManager dhcp=internal

2016-10-12 Thread Colin Walters 
Hey, so as part of the discussion about NetworkManager vs systemd-networkd,
one thing that happened is networkd started exposing its DHCP code as
a shared library, and NetworkManager learned to use it if one specifies

```
[main]
dhcp=internal
```

in /etc/NetworkManager/NetworkManager.conf.  I have an open PR
to start doing this for Atomic Host:

https://pagure.io/fedora-atomic/pull-request/23

However, we still have to lug around the RPM because of the
hard Requires in NetworkManager.spec:

https://bugzilla.redhat.com/show_bug.cgi?id=1204226

Since at the moment, Fedora editions come from the same pool
of binary RPMs, we don't have a real mechanism for me to ignore
that dependency just for Atomic Host.

And anyways, I don't see a reason not to do this across the board,
hence this thread.

The networkd DHCP code has gotten a fair amount of testing
in server environments, but I suspect it could use more battle
testing in two things:

1) Desktop systems with a wider variety of DHCP environments (from
  home routers, enterprise environments with unusual DHCP servers)
2) Cases where one wants to propagate various config options
  from the DHCP server; see e.g. 
https://bugzilla.gnome.org/show_bug.cgi?id=746911

Anyways, let's get some more testing of this; if you have a few minutes
and you feel your DHCP situation is unusual, try frobbing the config option,
and report any failures in https://bugzilla.redhat.com/show_bug.cgi?id=1204226

If things seem OK I can do a Change page.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org