On Mon, December 1, 2014 16:48, Les Mikesell wrote:
Is there anyone who has more than a few boxes at more than one location who _doesn't_ have this issue? I'd like to see a FAQ or something by whoever designed the network configuration system about how they planned for it to work (with and without GUI availability). Likewise for what is supposed to happen when you restore a backup onto different hardware.
Think 'laptop'.
On Tue, Dec 2, 2014 at 7:52 AM, James B. Byrne byrnejb@harte-lyne.ca wrote:
On Mon, December 1, 2014 16:48, Les Mikesell wrote:
Is there anyone who has more than a few boxes at more than one location who _doesn't_ have this issue? I'd like to see a FAQ or something by whoever designed the network configuration system about how they planned for it to work (with and without GUI availability). Likewise for what is supposed to happen when you restore a backup onto different hardware.
Think 'laptop'.
Why would you need a static IP to stick to a laptop? Or have multiple NICs on one?
On Dec 2, 2014, at 2:10 PM, Les Mikesell lesmikesell@gmail.com wrote:
Think 'laptop'.
Why would you need a static IP to stick to a laptop? Or have multiple NICs on one?
Wired and WiFi.
If you configure a static IP with the wired Ethernet plugged in, you probably want that static IP to continue being used when you unplug the Ethernet cable and NM switches you over automatically to WiFi. NM does this.
This is why I want a checkbox in the NM GUI: “This is a 4U server, dummy, not a laptop.”
On Tue, Dec 2, 2014 at 3:17 PM, Warren Young wyml@etr-usa.com wrote:
On Dec 2, 2014, at 2:10 PM, Les Mikesell lesmikesell@gmail.com wrote:
Think 'laptop'.
Why would you need a static IP to stick to a laptop? Or have multiple NICs on one?
Wired and WiFi.
If you configure a static IP with the wired Ethernet plugged in, you probably want that static IP to continue being used when you unplug the Ethernet cable and NM switches you over automatically to WiFi. NM does this.
Really? That's insane. Our wired jacks are not on the same subnets as our access points. I'm not sure that's even possible with the Cisco units that have separate controllers.
This is why I want a checkbox in the NM GUI: “This is a 4U server, dummy, not a laptop.”
How about just 'don't be stupid' ?
On Dec 2, 2014, at 2:34 PM, Les Mikesell lesmikesell@gmail.com wrote:
On Tue, Dec 2, 2014 at 3:17 PM, Warren Young wyml@etr-usa.com wrote:
On Dec 2, 2014, at 2:10 PM, Les Mikesell lesmikesell@gmail.com wrote:
Think 'laptop'.
Why would you need a static IP to stick to a laptop? Or have multiple NICs on one?
Wired and WiFi.
If you configure a static IP with the wired Ethernet plugged in, you probably want that static IP to continue being used when you unplug the Ethernet cable and NM switches you over automatically to WiFi. NM does this.
Really? That's insane. Our wired jacks are not on the same subnets as our access points. I'm not sure that's even possible with the Cisco units that have separate controllers.
In such a network, you won’t run static IP configuration on such boxes. You’ll use DHCP.
On my home LAN, this automatic static IP migration is *exactly* what I want on my laptop.
The current NetworkManager design isn’t unequivocally wrong. It’s a sensible default for Fedora. It’s just not the right choice for enterprise Linux servers.
If you want to go and argue that Fedora shouldn’t be driving CentOS, it’s not an impossible position to take, but you have to fill in the blank spot it leaves. What would drive CentOS instead?
This is why I want a checkbox in the NM GUI: “This is a 4U server, dummy, not a laptop.”
How about just 'don't be stupid’ ?
More like “Don’t be clever, NetworkManager, I’m better at it.”
On Tue, Dec 2, 2014 at 5:00 PM, Warren Young wyml@etr-usa.com wrote:
Really? That's insane. Our wired jacks are not on the same subnets as our access points. I'm not sure that's even possible with the Cisco units that have separate controllers.
In such a network, you won’t run static IP configuration on such boxes. You’ll use DHCP.
On my home LAN, this automatic static IP migration is *exactly* what I want on my laptop.
I don't get it. Laptops are portable. Don't you ever go out of your house? If you control everything you can easily tell your dhcp server what IP to give it when you are there.
The current NetworkManager design isn’t unequivocally wrong. It’s a sensible default for Fedora. It’s just not the right choice for enterprise Linux servers.
If you want to go and argue that Fedora shouldn’t be driving CentOS, it’s not an impossible position to take, but you have to fill in the blank spot it leaves. What would drive CentOS instead?
I'd argue that splitting the community into separate groups - one that likes the design of unix/linux and runs large numbers of servers because they like it, and one that would really rather have a windows desktop for their only machine was the wrong thing to do in the first place. And having broken the community, letting the group that doesn't like the product in the first place control the design is probably a bad thing too. Red Hat wasn't that bad back when the people using it contributed directly to its development and were able to use the result.
-
James B. Byrne -
Les Mikesell -
Warren Young