similar to: NetworkManager fights with DHCP-only backup NIC

On Dec 2, 2014, at 2:10 PM, Les Mikesell <lesmikesell at 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

On Tue, Dec 2, 2014 at 7:52 AM, James B. Byrne <byrnejb at 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 >>

We ship servers to remote sites, which are rarely staffed with techs familiar with Linux. We have them tell us the static IP configuration for the box before we ship it, then we set it up for them here and ship it out to the site, where they just plug it in, turn it on, and walk away. That?s the ideal, anyway. What often happens in reality is either: 1. They give us incorrect static IP info,

On Dec 2, 2014, at 1:36 PM, Les Mikesell <lesmikesell at gmail.com> wrote: > On Tue, Dec 2, 2014 at 2:26 PM, Warren Young <wyml at etr-usa.com> wrote: >> Again, I?m not really after a way to make this work without NetworkManager. > > What part of the breakage that NetworkManager does is good for a > wired, static-addressed server? If you disable NM, the network

> On Dec 1, 2014, at 14:48, Les Mikesell <lesmikesell at gmail.com> wrote: > > On Mon, Dec 1, 2014 at 3:35 PM, Warren Young <wyml at etr-usa.com> wrote: > >> We ship servers to remote sites, which are rarely staffed with techs familiar with Linux. We have them tell us the static IP configuration for the box before we ship it, then we set it up for them here and

On Dec 1, 2014, at 10:27 PM, Rob Kampen <rkampen at reaching-clients.com> wrote: > Have you put > NM_CONTROLLED="no" > in the ifcfg-eth0 script? How is that better than systemctl stop NetworkManager systemctl disable NetworkManager Again, I?m not really after a way to make this work without NetworkManager. We?ve already got that. What I want is a way to tell

On Dec 2, 2014, at 2:34 PM, Les Mikesell <lesmikesell at gmail.com> wrote: > On Tue, Dec 2, 2014 at 3:17 PM, Warren Young <wyml at etr-usa.com> wrote: >> On Dec 2, 2014, at 2:10 PM, Les Mikesell <lesmikesell at gmail.com> wrote: >> >>>> Think 'laptop'. >>> >>> Why would you need a static IP to stick to a laptop? Or have

On Mon, Dec 1, 2014 at 3:35 PM, Warren Young <wyml at etr-usa.com> wrote: > We ship servers to remote sites, which are rarely staffed with techs familiar with Linux. We have them tell us the static IP configuration for the box before we ship it, then we set it up for them here and ship it out to the site, where they just plug it in, turn it on, and walk away. > > That?s the ideal,

On Tue, Dec 2, 2014 at 3:17 PM, Warren Young <wyml at etr-usa.com> wrote: > On Dec 2, 2014, at 2:10 PM, Les Mikesell <lesmikesell at 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

On Tue, Dec 2, 2014 at 2:26 PM, Warren Young <wyml at etr-usa.com> wrote: > On Dec 1, 2014, at 10:27 PM, Rob Kampen <rkampen at reaching-clients.com> wrote: > >> Have you put >> NM_CONTROLLED="no" >> in the ifcfg-eth0 script? > > How is that better than > > systemctl stop NetworkManager > systemctl disable NetworkManager >

On Tue, Dec 2, 2014 at 3:14 PM, Warren Young <wyml at etr-usa.com> wrote: > > >> What part of the breakage that NetworkManager does is good for a >> wired, static-addressed server? > > If you disable NM, the network configuration GUI stops working in EL7. (I didn?t do much with EL6, but I thought its GUI had a fall-back for the non-NM case.) > > We don?t need

On 12/02/2014 10:35 AM, Warren Young wrote: > We ship servers to remote sites, which are rarely staffed with techs familiar with Linux. We have them tell us the static IP configuration for the box before we ship it, then we set it up for them here and ship it out to the site, where they just plug it in, turn it on, and walk away. > > That?s the ideal, anyway. > > What often happens

I have a remote CentOS-5.3 installation that shares traffic with another enterprise. I want to record and measure the actual network traffic that comes into and goes out of that host's net i/f on a monthly basis for billing verification purposes. Does CentOS have a software package to accomplish this? I have run across references to a package called vnstat as a possible answer to my

CentOS-5.5 # uname -a Linux inet05.hamilton.harte-lyne.ca 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 2011 x86_64 x86_64 x86_64 GNU/Linux Can anyone tell me why I am seeing these error message? Specifically, why is TYPE=Bridge giving Unknown connection type 'Bridge'? Jan 13 08:25:31 inet05 nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs

On Wed, February 18, 2015 13:07, Les Mikesell wrote: > On Wed, Feb 18, 2015 at 11:39 AM, James B. Byrne > <byrnejb at harte-lyne.ca> wrote: >> 2. How does one configure the routing table on network startup to >> specifically detail the route particular addresses are supposed to >> take? >> > > Not exactly sure how routing works with aliases on the same

On Mon, March 23, 2015 05:24, Nux! wrote: > I find this very, very sad. > I find it unsavoury. We are recommending that acknowledged newbies subscribe to a service known for repeatedly and persistently violating its members' privacy? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited

On Thu, February 19, 2015 12:33, Les Mikesell wrote: > On Thu, Feb 19, 2015 at 9:48 AM, James B. Byrne > <byrnejb at harte-lyne.ca> wrote: >> >>> I added these directives to the route-eth0:192 file: >>> >>> ADDRESS0=192.168.6.9 >>> NETMASK0=255.255.255.0 >>> GATEWAY0=192.168.6.1 >>> >> >> Which should have been:

OS = CentOS-6.4 Uptime = 4 days, 1:31, httpd-2.2.15 SELinux=enforcing audit2why -l -a = nil report Since upgrading a public web service host from dedicated hardware running CentOS-5.x to a KVM virtual host running CentOS-6.3 I have experienced intermittent ( one every couple of months) halts by the Apache web service. There is never any trace left in any of the logs, there are no SELinux

We use a dual homed CentOS-6.3 host for our Internet gateway router. Its internal nic (eth1) is configured such that the address 192.168.0.1 is one of its aliases. # cat /etc/sysconfig/network-scripts/ifcfg-eth1:192BOOTPROTO=none BROADCAST=192.168.255.255 DEVICE=eth1:192 IPADDR=192.168.0.1 IPV6INIT=no MTU="" NAME="LAN - Non-routable" NETMASK=255.255.0.0 NETWORK=192.168.0.0

On Tue, February 17, 2015 15:20, Les Mikesell wrote: > Are there any tools to help assemble libraries and debuginfo to > examine core dumps that happened on another host where the versions > don't match? Something like mock but build-version specific and with > the debuginfo packages pulled in? > I am not sure that I understand your question so if this answer is totally