Re: SL 6.3 doesn't no network present until user logs in on GUI
On Thu, Dec 27, 2012 at 8:37 PM, Nico Kadel-Garcia nka...@gmail.com wrote: On Thu, Dec 27, 2012 at 10:05 AM, Tom H tomh0...@gmail.com wrote: NM in F-17/F-18 understands ifcfg files defining bonds, bridges, vlans. I've installed an X-less F-18 and uninstalled NM without a hitch so it's still uninstallable (but I didn't try to do so with GNOME or another DE installed), so it *SHOULD* still be uninstallable in EL-7. Since you're so enamored with NM, I look forward to your reaction to firewalld when you move to EL-7. :) Since F-18 is only in beta, not released yet, I'll reserve judgment until it's actually published. So far, from F-17, I'm afraid the switch to SL 7 is going to pretty painful. The switch to systemd instead of initscripts, and the switch from /bin and /sbin to /usr/bin and /usr/sbin for numerous core utilities are going to create a serious burden for people doing cross-platform work. Revising the network component layout is going to be even more delightful, The need for more sophisticated tools and discard of some of the complex old hackery is understandable, it's just going to be hard. The main/only reason that F-18 hasn't been released yet is the new-look installer so we can be quite sure that the NM behavior won't change by the time that F-18's published. Although the move to /usr and systemd are big plumbing changes, I suspect that the redesigned installer and gnome-shell will have a bigger impact on users. systemd's looking quite good; F-18'll be the fourth Fedora release with systemd by default. Oracle beat Fedora to the move to /usr with Solaris 11 so if you're working cross-platform, SL-7 will be the second exception when it's released... If I'm understanding you correctly, you're calling the scripts in /etc/sysconfig/network-scripts/ hackery and I agree. But it's good hackery. As a multi-distro user, I wish that all distributions used the same hackery...
Re: SL 6.3 doesn't no network present until user logs in on GUI
[ I think I accidentally took this thread private..., fixing that ] On Dec 28, 2012, at 5:40, Tom H tomh0...@gmail.com wrote: On Thu, Dec 27, 2012 at 8:37 PM, Nico Kadel-Garcia nka...@gmail.com wrote: On Thu, Dec 27, 2012 at 10:05 AM, Tom H tomh0...@gmail.com wrote: NM in F-17/F-18 understands ifcfg files defining bonds, bridges, vlans. I've installed an X-less F-18 and uninstalled NM without a hitch so it's still uninstallable (but I didn't try to do so with GNOME or another DE installed), so it *SHOULD* still be uninstallable in EL-7. Since you're so enamored with NM, I look forward to your reaction to firewalld when you move to EL-7. :) Since F-18 is only in beta, not released yet, I'll reserve judgment until it's actually published. So far, from F-17, I'm afraid the switch to SL 7 is going to pretty painful. The switch to systemd instead of initscripts, and the switch from /bin and /sbin to /usr/bin and /usr/sbin for numerous core utilities are going to create a serious burden for people doing cross-platform work. Revising the network component layout is going to be even more delightful, The need for more sophisticated tools and discard of some of the complex old hackery is understandable, it's just going to be hard. The main/only reason that F-18 hasn't been released yet is the new-look installer so we can be quite sure that the NM behavior won't change by the time that F-18's published. Although the move to /usr and systemd are big plumbing changes, I suspect that the redesigned installer and gnome-shell will have a bigger impact on users. systemd's looking quite good; F-18'll be the fourth Fedora release with systemd by default. I'm a system: it affects several software projects I work with on multiple releases, such as Subversion. Oracle beat Fedora to the move to /usr with Solaris 11 so if you're working cross-platform, SL-7 will be the second exception when it's released... Heh. I no longer count Solaris, I dumped it way back when they renamed it from SunOS and Red Hat was just becoming stable enough for real work. If I'm understanding you correctly, you're calling the scripts in /etc/sysconfig/network-scripts/ hackery and I agree. But it's good hackery. As a multi-distro user, I wish that all distributions used the same hackery... Amen. But I wish our favorite upstream vendor would use the same hackery, instead of mangling the content differently with different front ends, all of which generate distinct content in different formats and remangle it when using even the same front end twice in a row.
Re: SL 6.3 doesn't no network present until user logs in on GUI
On Fri, Dec 14, 2012 at 10:33 PM, Nico Kadel-Garcia nka...@gmail.com wrote: On Thu, Dec 13, 2012 at 2:58 PM, Konstantin Olchanski olcha...@triumf.ca wrote: On Wed, Dec 12, 2012 at 09:19:05PM -0500, Nico Kadel-Garcia wrote: Since it's packaged as the default from the upstream vendor distribution, and since the system-config-network tool from the upstream vendor provides no ability to access or manipulate this feature or numerous others, ... Complaint rejected. RTFM the Deployment Guide, section Networking. It tells you to use nm-connection-editor. It even explains all this business of system and user network connections. https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/part-Networking.html You've apparently read the document. I'll withdraw the complaint that there is no way to turn it off. But having to install and activate NetworkManager, and run the X applications to turn off this misfeature is. well, it's not our favorite upstream vendor's proudest moment. It's particularly problematical on limited environment features such as KVM servers where you *should not* be running graphical logins because they suck resources away from more critical applications. P.S. system-config-network is gone, but of late, it was simpler to vi /etc/sysconfig/network-scripts/ifcfg-ethX, and Look Ma! Vi those files directly still works, even with the NetworkManager! Unfortunately, ifcfg-eth* is not a reliable convention. KVM bridges, for example, may be named almost any arbitrary suffix. Pair bonded devices and wireless devices and PPP connections add other possibilities: it adds up to confusion. NM in F-17/F-18 understands ifcfg files defining bonds, bridges, vlans. I've installed an X-less F-18 and uninstalled NM without a hitch so it's still uninstallable (but I didn't try to do so with GNOME or another DE installed), so it *SHOULD* still be uninstallable in EL-7. Since you're so enamored with NM, I look forward to your reaction to firewalld when you move to EL-7. :)
Re: SL 6.3 doesn't no network present until user logs in on GUI
On Thu, Dec 27, 2012 at 10:05 AM, Tom H tomh0...@gmail.com wrote: NM in F-17/F-18 understands ifcfg files defining bonds, bridges, vlans. I've installed an X-less F-18 and uninstalled NM without a hitch so it's still uninstallable (but I didn't try to do so with GNOME or another DE installed), so it *SHOULD* still be uninstallable in EL-7. Since you're so enamored with NM, I look forward to your reaction to firewalld when you move to EL-7. :) Since F-18 is only in beta, not released yet, I'll reserve judgment until it's actually published. So far, from F-17, I'm afraid the switch to SL 7 is going to pretty painful. The switch to systemd instead of initscripts, and the switch from /bin and /sbin to /usr/bin and /usr/sbin for numerous core utilities are going to create a serious burden for people doing cross-platform work. Revising the network component layout is going to be even more delightful, The need for more sophisticated tools and discard of some of the complex old hackery is understandable, it's just gong to be hard.
Re: SL 6.3 doesn't no network present until user logs in on GUI
On Thu, Dec 13, 2012 at 5:45 PM, Konstantin Olchanski olcha...@triumf.ca wrote: On Thu, Dec 13, 2012 at 05:15:58PM -0500, Tom H wrote: I don't use the GUI ... Yes, right. New way of thinking, if you are not using a GUI you are some kind of luddite. Not using a GUI at all on SL or TUV doesn't mean that I don't use any GUI on other distributions or OSs. Specifically for networking, I don't use the NM GUI (or system-config-network). It's simpler to use /etc/sysconfig/network-scripts/ or /etc/NetworkManager/system-connections/.
Re: SL 6.3 doesn't no network present until user logs in on GUI
On 12/12/2012 08:54 AM, Winnie Lacesso wrote: Do I grok this aright - you set up an SL workstation to do network stuff in the background, i.e: dhcp renewal, ntp, wee-hours automatic security updates, possibly other things (overnight backups? rsync of data to central server?); but if no one's logged onto the console, those all just stop working bcs NM has shut off the network? TUV thinks this is a good idea?!astonish It seems badly thought, if someone's not logged on overnight, no security updates. Or does yum rerun its wee-hours cron if someone logs in at the console during daytime? Enterprise Linux != Server-only Linux. Workstation users may very well be on a network where the physical connection is per-user authenticated with something like 802.1x NAC. This isn't just for wireless. I can think of numerous use cases where an ethernet-connected workstation should not have a valid connection unless someone is logged in and has passed 802.1x auth. And I do use EL as a workstation, both in wired and wireless modes, with laptop and desktop hardware. Using it right now, in fact. The server case is trivially handled during installation; there is a fairly obvious Networking button on the screen during the installation, and kickstart can likewise set up networking if you can't or won't use the GUI installer (either on local console or remote with VNC). Kickstart installs are the best ones when latency is horrible and even ssh or remote serial consoles are sluggish. There are use cases that NM isn't the best for; the bridged connection case is one of them. Those cases are being worked on. In the meantime, NM_CONTROLLED=no in the normal and documented locations works fine. Nuking NM from high orbit is no longer necessary...
Re: SL 6.3 doesn't no network present until user logs in on GUI
On Wed, Dec 12, 2012 at 09:19:05PM -0500, Nico Kadel-Garcia wrote: Since it's packaged as the default from the upstream vendor distribution, and since the system-config-network tool from the upstream vendor provides no ability to access or manipulate this feature or numerous others, ... Complaint rejected. RTFM the Deployment Guide, section Networking. It tells you to use nm-connection-editor. It even explains all this business of system and user network connections. https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/part-Networking.html P.S. system-config-network is gone, but of late, it was simpler to vi /etc/sysconfig/network-scripts/ifcfg-ethX, and Look Ma! Vi those files directly still works, even with the NetworkManager! -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: SL 6.3 doesn't no network present until user logs in on GUI
On Thu, Dec 13, 2012 at 05:15:58PM -0500, Tom H wrote: I don't use the GUI ... Yes, right. New way of thinking, if you are not using a GUI you are some kind of luddite. No matter that I am in Canada and I need to manage a machine in Japan hidden behind 25 firewalls. Ping time is 200 ms, ssh is barely usable, forget about X11 tunneling and good luck getting a VNC connection through the 25 firewalls. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: SL 6.3 doesn't no network present until user logs in on GUI
Konstantin Olchanski wrote: This disables the super-clever extra-useful network manager feature where it enables networking when a user logs in into the console and helpfully disables the networking when a user logs out from the console. Do I grok this aright - you set up an SL workstation to do network stuff in the background, i.e: dhcp renewal, ntp, wee-hours automatic security updates, possibly other things (overnight backups? rsync of data to central server?); but if no one's logged onto the console, those all just stop working bcs NM has shut off the network? TUV thinks this is a good idea?! astonish It seems badly thought, if someone's not logged on overnight, no security updates. Or does yum rerun its wee-hours cron if someone logs in at the console during daytime?
Re: SL 6.3 doesn't no network present until user logs in on GUI
On Wed, Dec 12, 2012 at 01:54:21PM +, Winnie Lacesso wrote: Konstantin Olchanski wrote: This disables the super-clever extra-useful network manager feature where it enables networking when a user logs in into the console and helpfully disables the networking when a user logs out from the console. Do I grok this aright - you set up an SL workstation to do network stuff in the background, i.e: dhcp renewal, ntp, wee-hours automatic security updates, possibly other things (overnight backups? rsync of data to central server?); but if no one's logged onto the console, those all just stop working bcs NM has shut off the network? TUV thinks this is a good idea?! astonish It seems badly thought, if someone's not logged on overnight, no security updates. Or does yum rerun its wee-hours cron if someone logs in at the console during daytime? I do not think this comes from TUV. It comes from the NetworkManager croud, which I think is the same as the GNOME croud, or at least they think the same way - my laptop^H^H^H^H^H^Htablet is the only use-case that matters. The normal SL setup (after the installer) is to have available to all users enabled on all system network interfaces and then none of this nonsense happens, the network functions normally (always enabled). But I have seen this problem - after the installer, available to all users is off and you see the silly behaviour. I discount it as an installer malfunction. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: SL 6.3 doesn't no network present until user logs in on GUI.
On Mon, Dec 10, 2012 at 3:49 PM, Lamar Owen lo...@pari.edu wrote: Well, I had expected this behavior for the longest, actually, simply from my long-ago reading of the 'ifup' man page. It's not explicitly stated, but given the two files listed and the wording, it is, to my mind at least, somewhat obvious that /etc/sysconfig/network is sourced along with the device file and since they are essentially setting environment variables, one could set things in either place. Other than in the source for the scripts, the order of sourcing isn't really known, but I would suspect /etc/sysconfig/network is sourced firts. But, rather than dig down and go against the flow' I have just chosen to learn and work with the NM system, even on servers, since that is upstream's direction. And while the docs aren't 100% complete, the file /usr/share/doc/initscripts-*/sysconfig.txt is still the best reference out there, other than the source, of course. The Official Upstream documents mention NM_CONTROLLED in: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-networkscripts-interfaces_network-bridge.html which is talking about network bridging, and that is also on a device-by-device basis, as upstream's assumption is that you're going to use NM on all the other interfaces. You probably looked at the ifup script and not its man page because the latter's pretty bare. /usr/share/doc/initscripts-*/sysconfig.txt is more or less complete but I've found it lacking from time to time - and then it catches up. For example, in initscripts-9.03.31 (and perhaps in an earlier version too) it documents NM_CONTROLLED.
Re: SL 6.3 doesn't no network present until user logs in on GUI.
On Sun, Dec 9, 2012 at 7:28 PM, Nico Kadel-Garcia nka...@gmail.com wrote: On Sun, Dec 9, 2012 at 6:38 PM, Tom H tomh0...@gmail.com wrote: On Sun, Dec 9, 2012 at 5:21 PM, Nico Kadel-Garcia nka...@gmail.com wrote: You can put NM_MANAGER=no in /etc/sysconfig/network, along with NO_ZEROCONF=yes to aovid generating those default, irritating 169.254.* IP addresses at network startup time. NM_MANAGER=no in /etc/sysconfig/network? You must mean NM_CONTROLLED. Are you sure that you can set it in /etc/sysconfig/network? Yes, quite right. It's already been a day If you look at the /ets/sysconfig/network-scripts maze of twisty little scripts, all different, you'll see that most of the ifup, ifdown, and similar executable scripts actually source /etc/sysconfig/network somewhere in their actual operation. So yes, /etc/sysconfig/network actuall works to shut down NetworkManager without having to maintain and edit individual components. Unfortunately, if you don't read the source code, you won't know about this sort of thing. I've never seen any documentation about setting NM_CONTROLLED in /etc/sysconfig/network but there seem to be a few things about /etc/sysconfig that aren't documented... I've forgotten why but I read those scripts in the past, got the info that I was looking for, and hoped that I'd never have to read them again... I guess that I'll have to go through them one more time to look up some variables. :( I thought that it was meant to be used in /etc/sysconfig/network-scripts/ifcfg-*. It's like turning off the circuit breakers. You're not relying on the local switch for individual channels, and it's much safer in case you re-arrange the network in the future (by adding network ports, replacing a network card, or cloning a virtual machine). ACK, thanks. (I've never had a problem removing NM from an X-less box.) And on a machine that's a pure LAMP stack, DNS server, or other pure server that can work. AFAIK, you might have a problem removing NM from a recent Fedora running GNOME because there was some talk of making it a dependency. I might install F-18 this weekend and, if I do, I'll check. Anyway, NM's going to become the default and unique Fedora/EL networking setup in the future because some Fedora/RH developer's going to say, at some point, maintaining both NM and the '/etc/sysconfig/network-scripts/' doesn't make sense and the powers that be'll agree. NM 0.9.6 can handle bonding/bridging/vlan-ing so an EL-8 target wouldn't surprise me...
Re: SL 6.3 doesn't no network present until user logs in on GUI.
On 12/09/2012 07:28 PM, Nico Kadel-Garcia wrote: If you look at the /ets/sysconfig/network-scripts maze of twisty little scripts, all different, you'll see that most of the ifup, ifdown, and similar executable scripts actually source /etc/sysconfig/network somewhere in their actual operation. So yes, /etc/sysconfig/network actuall works to shut down NetworkManager without having to maintain and edit individual components. Unfortunately, if you don't read the source code, you won't know about this sort of thing. Well, I had expected this behavior for the longest, actually, simply from my long-ago reading of the 'ifup' man page. It's not explicitly stated, but given the two files listed and the wording, it is, to my mind at least, somewhat obvious that /etc/sysconfig/network is sourced along with the device file and since they are essentially setting environment variables, one could set things in either place. Other than in the source for the scripts, the order of sourcing isn't really known, but I would suspect /etc/sysconfig/network is sourced firts. But, rather than dig down and go against the flow' I have just chosen to learn and work with the NM system, even on servers, since that is upstream's direction. And while the docs aren't 100% complete, the file /usr/share/doc/initscripts-*/sysconfig.txt is still the best reference out there, other than the source, of course. The Official Upstream documents mention NM_CONTROLLED in: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-networkscripts-interfaces_network-bridge.html which is talking about network bridging, and that is also on a device-by-device basis, as upstream's assumption is that you're going to use NM on all the other interfaces.
Re: SL 6.3 doesn't no network present until user logs in on GUI.
On Sun, Dec 09, 2012 at 09:53:34AM -0600, Jos? Pablo M?ndez Soto wrote: I noticed that my virtual machine with GUI, that I built from the SL-63-x86_64-2012-08-02-Install-DVD.iso, won't reply to pings or open SSH sessions until a user logs in. Open network manager - edit connections or run nm-connection-editor, open each connection and tick the available to all users check-box. This disables the super-clever extra-useful network manager feature where it enables networking when a user logs in into the console and helpfully disables the networking when a user logs out from the console. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
RE: SL 6.3 doesn't no network present until user logs in on GUI.
Konstantin, I've been struggling with 6.2 and 6.3 on a dell Optiplex (so it is 32 bit) I'm sure this is why the networking just doesn't work right. Thank you. I will check it out Carl Friedberg www.comets.com carl.friedb...@comets.com http://about.me/carl.friedberg -Original Message- From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Konstantin Olchanski Sent: Monday, December 10, 2012 6:16 PM To: Jos? Pablo M?ndez Soto Cc: SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV Subject: Re: SL 6.3 doesn't no network present until user logs in on GUI. On Sun, Dec 09, 2012 at 09:53:34AM -0600, Jos? Pablo M?ndez Soto wrote: I noticed that my virtual machine with GUI, that I built from the SL-63-x86_64-2012-08-02-Install-DVD.iso, won't reply to pings or open SSH sessions until a user logs in. Open network manager - edit connections or run nm-connection-editor, open each connection and tick the available to all users check-box. This disables the super-clever extra-useful network manager feature where it enables networking when a user logs in into the console and helpfully disables the networking when a user logs out from the console. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
SL 6.3 doesn't no network present until user logs in on GUI.
Hello, I am playing around with SL instead of CentOS so to know which one behaves better or just to have a criteria on how they both differ, being RedHat re-distros. I noticed that my virtual machine with GUI, that I built from the SL-63-x86_64-2012-08-02-Install-DVD.iso, won't reply to pings or open SSH sessions until a user logs in. I tried the same on a CentOS 6.2 built similarly, and no matter if there are users or no users logged in, it always have networking and you can SSH into it. Any idea about this difference? Can it be changed in SL so to initiate connections before a GUI log in? Thanks, *José Pablo Méndez *
Re: SL 6.3 doesn't no network present until user logs in on GUI.
2012/12/9 José Pablo Méndez Soto aux...@gmail.com: Hello, I am playing around with SL instead of CentOS so to know which one behaves better or just to have a criteria on how they both differ, being RedHat re-distros. I noticed that my virtual machine with GUI, that I built from the SL-63-x86_64-2012-08-02-Install-DVD.iso, won't reply to pings or open SSH sessions until a user logs in. I tried the same on a CentOS 6.2 built similarly, and no matter if there are users or no users logged in, it always have networking and you can SSH into it. Any idea about this difference? Can it be changed in SL so to initiate connections before a GUI log in? On RHEL 6 and clones, network is managed by network-manager by default. You need to disable network manager and configure interfaces on traditional way. Take look at NM_MANAGED on /etc/sysconfig/network-scripts/ifcfg* -- Eero
Re: SL 6.3 doesn't no network present until user logs in on GUI.
On 9 December 2012 17:05, Eero Volotinen eero.voloti...@iki.fi wrote: 2012/12/9 José Pablo Méndez Soto aux...@gmail.com: I noticed that my virtual machine with GUI, that I built from the SL-63-x86_64-2012-08-02-Install-DVD.iso, won't reply to pings or open SSH sessions until a user logs in. I tried the same on a CentOS 6.2 built similarly, and no matter if there are users or no users logged in, it always have networking and you can SSH into it. Any idea about this difference? Can it be changed in SL so to initiate connections before a GUI log in? Have you check the boxes “Connect Automatically” and “Available to all users” on the network options / properties? On RHEL 6 and clones, network is managed by network-manager by default. You need to disable network manager and configure interfaces on traditional way. I don't think so. I have some SL PCs with NetworkManager, and I can reboot them remotely and remote login (ssh) with no problem. Regards, -Tito.
Re: SL 6.3 doesn't no network present until user logs in on GUI.
Ok guys thanks for putting me in good direction. The thing is, if you don't select the Available to all users check box in the Network Manager Applet, there *won't be a file under /etc/sysconfig/*for the desired network adapter, and therefore, there will be no networking before any of the users log in. Putting a file inside that directory will help, but I guess the recommended way would be to select the check box Thanks a lot. *José Pablo Méndez * On Sun, Dec 9, 2012 at 12:12 PM, MT Julianto mtjulia...@gmail.com wrote: On 9 December 2012 17:05, Eero Volotinen eero.voloti...@iki.fi wrote: 2012/12/9 José Pablo Méndez Soto aux...@gmail.com: I noticed that my virtual machine with GUI, that I built from the SL-63-x86_64-2012-08-02-Install-DVD.iso, won't reply to pings or open SSH sessions until a user logs in. I tried the same on a CentOS 6.2 built similarly, and no matter if there are users or no users logged in, it always have networking and you can SSH into it. Any idea about this difference? Can it be changed in SL so to initiate connections before a GUI log in? Have you check the boxes “Connect Automatically” and “Available to all users” on the network options / properties? On RHEL 6 and clones, network is managed by network-manager by default. You need to disable network manager and configure interfaces on traditional way. I don't think so. I have some SL PCs with NetworkManager, and I can reboot them remotely and remote login (ssh) with no problem. Regards, -Tito.
Re: SL 6.3 doesn't no network present until user logs in on GUI.
On Sun, Dec 9, 2012 at 11:05 AM, Eero Volotinen eero.voloti...@iki.fi wrote: 2012/12/9 José Pablo Méndez Soto aux...@gmail.com: Hello, I am playing around with SL instead of CentOS so to know which one behaves better or just to have a criteria on how they both differ, being RedHat re-distros. I noticed that my virtual machine with GUI, that I built from the SL-63-x86_64-2012-08-02-Install-DVD.iso, won't reply to pings or open SSH sessions until a user logs in. I tried the same on a CentOS 6.2 built similarly, and no matter if there are users or no users logged in, it always have networking and you can SSH into it. Any idea about this difference? Can it be changed in SL so to initiate connections before a GUI log in? On RHEL 6 and clones, network is managed by network-manager by default. You need to disable network manager and configure interfaces on traditional way. Take look at NM_MANAGED on /etc/sysconfig/network-scripts/ifcfg* NetworkManager is *not the friend* of anyone running a server. It's unfortunately difficult to rip out by the roots, because other components depend on it. And the system-config-network tool has no way to gracefully turn it off, you have to use a text editor. You can put NM_MANAGER=no in /etc/sysconfig/network, along with NO_ZEROCONF=yes to aovid generating those default, irritating 169.254.* IP addresses at network startup time. Eero
Re: SL 6.3 doesn't no network present until user logs in on GUI.
NetworkManager is *not the friend* of anyone running a server. It's unfortunately difficult to rip out by the roots, I've had pretty good luck with a 'yum remove NetworkManager'. The only thing I've found depending on it has been NetworkManager-gnome, and that's no big loss. Maybe I'm missing removing something, but that seems to work. - Bluejay Adametz, CFII, AP, AA-5B N45210 A pessimist sees the difficulty in every opportunity; an optimist sees the opportunity in every difficulty. - Winston Churchill -- NOTICE: This message, including any attachments, is only for the use of the intended recipient(s) and may contain confidential and privileged information, or information otherwise protected from disclosure by law. If the reader of this message is not the intended recipient, you are hereby notified that any use, disclosure, copying, dissemination or distribution of this message or any of its attachments is strictly prohibited. If you received this message in error, please contact the sender immediately by reply email and destroy this message, including all attachments, and any copies thereof.
Re: SL 6.3 doesn't no network present until user logs in on GUI.
On Sun, Dec 9, 2012 at 5:49 PM, Bluejay Adametz blue...@fujifilm.com wrote: NetworkManager is *not the friend* of anyone running a server. It's unfortunately difficult to rip out by the roots, I've had pretty good luck with a 'yum remove NetworkManager'. The only thing I've found depending on it has been NetworkManager-gnome, and that's no big loss. Maybe I'm missing removing something, but that seems to work. - Bluejay Adametz, CFII, AP, AA-5B N45210 A pessimist sees the difficulty in every opportunity; an optimist sees the opportunity in every difficulty. - Winston Churchill The difficulty comes in if you need more sophisticated tools, such as VPN's or cobbler or start running KVM servers. I can't predict which toolkit will list NetworkManager as a dependency, and if you're in a dev server environment, it gets even trickier. That's why it''s useful to put NM_CONTROLLED=no in /etc/sysconfig/network becomes handy.
Re: SL 6.3 doesn't no network present until user logs in on GUI.
On Sun, Dec 9, 2012 at 5:21 PM, Nico Kadel-Garcia nka...@gmail.com wrote: On Sun, Dec 9, 2012 at 11:05 AM, Eero Volotinen eero.voloti...@iki.fi wrote: 2012/12/9 José Pablo Méndez Soto aux...@gmail.com: Hello, I am playing around with SL instead of CentOS so to know which one behaves better or just to have a criteria on how they both differ, being RedHat re-distros. I noticed that my virtual machine with GUI, that I built from the SL-63-x86_64-2012-08-02-Install-DVD.iso, won't reply to pings or open SSH sessions until a user logs in. I tried the same on a CentOS 6.2 built similarly, and no matter if there are users or no users logged in, it always have networking and you can SSH into it. Any idea about this difference? Can it be changed in SL so to initiate connections before a GUI log in? On RHEL 6 and clones, network is managed by network-manager by default. You need to disable network manager and configure interfaces on traditional way. Take look at NM_MANAGED on /etc/sysconfig/network-scripts/ifcfg* NetworkManager is *not the friend* of anyone running a server. It's unfortunately difficult to rip out by the roots, because other components depend on it. And the system-config-network tool has no way to gracefully turn it off, you have to use a text editor. You can put NM_MANAGER=no in /etc/sysconfig/network, along with NO_ZEROCONF=yes to aovid generating those default, irritating 169.254.* IP addresses at network startup time. NM_MANAGER=no in /etc/sysconfig/network? You must mean NM_CONTROLLED. Are you sure that you can set it in /etc/sysconfig/network? I thought that it was meant to be used in /etc/sysconfig/network-scripts/ifcfg-*. (I've never had a problem removing NM from an X-less box.)
Re: SL 6.3 doesn't no network present until user logs in on GUI.
On Sun, Dec 9, 2012 at 6:38 PM, Tom H tomh0...@gmail.com wrote: On Sun, Dec 9, 2012 at 5:21 PM, Nico Kadel-Garcia nka...@gmail.com wrote: On Sun, Dec 9, 2012 at 11:05 AM, Eero Volotinen eero.voloti...@iki.fi wrote: 2012/12/9 José Pablo Méndez Soto aux...@gmail.com: Hello, I am playing around with SL instead of CentOS so to know which one behaves better or just to have a criteria on how they both differ, being RedHat re-distros. I noticed that my virtual machine with GUI, that I built from the SL-63-x86_64-2012-08-02-Install-DVD.iso, won't reply to pings or open SSH sessions until a user logs in. I tried the same on a CentOS 6.2 built similarly, and no matter if there are users or no users logged in, it always have networking and you can SSH into it. Any idea about this difference? Can it be changed in SL so to initiate connections before a GUI log in? On RHEL 6 and clones, network is managed by network-manager by default. You need to disable network manager and configure interfaces on traditional way. Take look at NM_MANAGED on /etc/sysconfig/network-scripts/ifcfg* NetworkManager is *not the friend* of anyone running a server. It's unfortunately difficult to rip out by the roots, because other components depend on it. And the system-config-network tool has no way to gracefully turn it off, you have to use a text editor. You can put NM_MANAGER=no in /etc/sysconfig/network, along with NO_ZEROCONF=yes to aovid generating those default, irritating 169.254.* IP addresses at network startup time. NM_MANAGER=no in /etc/sysconfig/network? You must mean NM_CONTROLLED. Are you sure that you can set it in /etc/sysconfig/network? Yes, quite right. It's already been a day If you look at the /ets/sysconfig/network-scripts maze of twisty little scripts, all different, you'll see that most of the ifup, ifdown, and similar executable scripts actually source /etc/sysconfig/network somewhere in their actual operation. So yes, /etc/sysconfig/network actuall works to shut down NetworkManager without having to maintain and edit individual components. Unfortunately, if you don't read the source code, you won't know about this sort of thing. I thought that it was meant to be used in /etc/sysconfig/network-scripts/ifcfg-*. It's like turning off the circuit breakers. You're not relying on the local switch for individual channels, and it's much safer in case you re-arrange the network in the future (by adding network ports, replacing a network card, or cloning a virtual machine). (I've never had a problem removing NM from an X-less box.) And on a machine that's a pure LAMP stack, DNS server, or other pure server that can work.
