From: Dan Winship d...@gnome.org
On 07/01/2013 04:14 PM, Dan Winship wrote:
danw, any rationale behind the argument for ignore-carrier?
Servers, by definition, tend to have fixed IP addresses. Therefore, if
you are using DHCP on a server, it's probably for ease of deployment,
not
On Mon, 2013-07-08 at 12:47 -0400, Dan Winship wrote:
On 07/01/2013 04:14 PM, Dan Winship wrote:
danw, any rationale behind the argument for ignore-carrier?
Servers, by definition, tend to have fixed IP addresses. Therefore, if
you are using DHCP on a server, it's probably for ease of
On 07/01/2013 04:14 PM, Dan Winship wrote:
danw, any rationale behind the argument for ignore-carrier?
Servers, by definition, tend to have fixed IP addresses. Therefore, if
you are using DHCP on a server, it's probably for ease of deployment,
not because you want dynamism.
Any response to
Sounds like a useful default for specific class of usage. I, personally,
would prefer the server to react on carrier at least when using DHCP.
So both you and danw didn't say *why*.
It's easy. When moving a server to a new location, I want it to accomodate the
new network, that's why I'm
On Mon, 2013-07-01 at 15:32 -0400, Pavel Simerda wrote:
In my opinion, the default is to treat DHCP connections as fully
dynamic on servers as well as on laptops.
In other words, a vote against ignore-carrier=* being the
default. I think I agree with you - if you're using DHCP,
I'd expect
On 07/01/2013 03:44 PM, Colin Walters wrote:
On Mon, 2013-07-01 at 15:32 -0400, Pavel Simerda wrote:
In my opinion, the default is to treat DHCP connections as fully
dynamic on servers as well as on laptops.
In other words, a vote against ignore-carrier=* being the
default. I think I
So the relevant tweakable options are:
- no-auto-default=[interfaces]
Disables automatically-created DHCP ethernet connections. Everyone
agrees we want no-auto-default=* for servers.
- ignore-carrier=[interfaces]
Disables carrier-detect on the indicated interfaces. There's been some
internal
- Original Message -
From: Colin Walters walt...@verbum.org
To: networkmanager-list@gnome.org
Sent: Wednesday, June 26, 2013 4:25:31 PM
Subject: discuss: NM server defaults
So I filed this downstream:
https://bugzilla.redhat.com/show_bug.cgi?id=978081
I think it might be useful
On Thu, 2013-06-27 at 11:34 -0400, Pavel Simerda wrote:
- Original Message -
From: Colin Walters walt...@verbum.org
To: networkmanager-list@gnome.org
Sent: Wednesday, June 26, 2013 4:25:31 PM
Subject: discuss: NM server defaults
So I filed this downstream:
https
So I filed this downstream:
https://bugzilla.redhat.com/show_bug.cgi?id=978081
But it seems like something worth talking about here. We could easily
maintain nm-server-defaults.conf in the upstream git repo, at least. We
could also add --enable-server-defaults as a build time option, for
OS
10 matches
Mail list logo
