Re: [CentOS] Cisco AnyConnect Mobility Client for 32- bit CentOS 6

2018-02-22 Thread Nux!
Install the excellent openconnect client from EPEL, I think there is also a 
NetworkManager plugin for it so you can use a UI, though the cli is not too bad.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "H" 
> To: "CentOS mailing list" 
> Sent: Thursday, 22 February, 2018 02:35:33
> Subject: [CentOS] Cisco AnyConnect Mobility Client for 32- bit CentOS 6

> I have the above installed on a couple of 64-bit systems, both CentOS 6 and
> CentOS 7, where the client works fine.
> 
> Now, however, I have installed the 32-bit version of CentOS 6 on a netbook 
> but I
> cannot get the Cisco website installer to recognize the computer/operating
> system, not even displaying any error message.
> 
> Does anyone have the client running on a 32-bit system? I have been told it
> should run on a 32-bit system and did have it running on the same netbook 
> while
> it was still running Vista Home edition, another 32-bit operating system.
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] a few simple questions about upgrading an "official" centos 7 release

2018-02-22 Thread Robert P. J. Day

  again, some fairly trivial(?) questions about working with centos
7.4, given my time immersed in fedora so i want to make sure i'm not
carrying over any bad habits.

  first, is there anything untoward in updating an installed version
of centos 7.4 with a simple "yum update"? i'm well aware of keeping in
mind the goal of stability with centos, so am unsure what the
philosophy is of pulling in new updates as cavalierly as i do with
fedora. currently, "yum list updates" shows me 206 possible updates;
should i have any concern about updating packages coming from the
standard centos repos?

  next, are there any issues replacing yum wihth dnf? i found this
piece:

https://www.vultr.com/docs/use-dnf-to-manage-software-packages-on-centos-7

which suggests it shouldn't be a problem. thoughts?

  finally, any concerns i should have about upgrading the kernel from
3.10 to 4.14 or 4.15, as explained in a number of places like this:

https://www.tecmint.com/install-upgrade-kernel-version-in-centos-7/

  i simply prefer to run a current kernel but i can resist the
temptation if upgrading that on a centos 7.4 system would introduce
more problems than are worth it.

  thoughts?

rday


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7 1708 won't boot after grub2 update

2018-02-22 Thread Pete Biggs

> 
> No gray 7-boot screen. Might be a graphics issue, the card is a Nvidia 1060 
> with no particular drivers loaded except for the default Nouveau package.
> What's weird is that I can't even get a CLI login screen with ctrl-alt-Fx at 
> this point.
> 
> Will continue trouble-shooting and see if I can resolve this properly.
> 

Edit the grub line to boot into single user and remove "rhgb" and
"quiet" so you can see all the messages. See where it stops.

I've seen issues recently with Intel chipset and RAID - a couple of my
machines have paused for a very long time after booting and before
presenting login screens/prompts. It looks as if checking the array
after a non-clean shutdown is sucking so much CPU time that nothing
else happens. (The secondary issue is why it's shutting down without
marking the array as clean!)

P.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7 1708 won't boot after grub2 update

2018-02-22 Thread Sorin Srbu
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Pete Biggs
> Sent: den 22 februari 2018 10:02
> To: centos@centos.org
> Subject: Re: [CentOS] CentOS 7 1708 won't boot after grub2 update
> 
> 
> >
> > No gray 7-boot screen. Might be a graphics issue, the card is a Nvidia
1060
> with no particular drivers loaded except for the default Nouveau package.
> > What's weird is that I can't even get a CLI login screen with
ctrl-alt-Fx at this
> point.
> >
> > Will continue trouble-shooting and see if I can resolve this properly.
> >
> 
> Edit the grub line to boot into single user and remove "rhgb" and
> "quiet" so you can see all the messages. See where it stops.
> 
> I've seen issues recently with Intel chipset and RAID - a couple of my
> machines have paused for a very long time after booting and before
> presenting login screens/prompts. It looks as if checking the array
> after a non-clean shutdown is sucking so much CPU time that nothing
> else happens. (The secondary issue is why it's shutting down without
> marking the array as clean!)

Thanks!

You use xfs on these machines?

--
//Sorin

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7 1708 won't boot after grub2 update

2018-02-22 Thread Pete Biggs

> > Edit the grub line to boot into single user and remove "rhgb" and
> > "quiet" so you can see all the messages. See where it stops.
> > 
> > I've seen issues recently with Intel chipset and RAID - a couple of my
> > machines have paused for a very long time after booting and before
> > presenting login screens/prompts. It looks as if checking the array
> > after a non-clean shutdown is sucking so much CPU time that nothing
> > else happens. (The secondary issue is why it's shutting down without
> > marking the array as clean!)
> 
> Thanks!
> 
> You use xfs on these machines?
> 
Yes. 

P.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] a few simple questions about upgrading an "official" centos 7 release

2018-02-22 Thread Liam O'Toole
On 2018-02-22, Robert P. J. Day
 wrote:
>
>   again, some fairly trivial(?) questions about working with centos
>   7.4, given my time immersed in fedora so i want to make sure i'm not
>   carrying over any bad habits.
>
>   first, is there anything untoward in updating an installed version
>   of centos 7.4 with a simple "yum update"? i'm well aware of keeping
>   in mind the goal of stability with centos, so am unsure what the
>   philosophy is of pulling in new updates as cavalierly as i do with
>   fedora. currently, "yum list updates" shows me 206 possible updates;
>   should i have any concern about updating packages coming from the
>   standard centos repos?

No. The updates provided over an x.y series are relatively minor and
generally well tested. It's very different to the version churn
associated with Fedora. The updates also include important security
fixes, and it's not advisable to try to apply those in isolation. But I
would add the usual caveat: if you're doing anything business-critical
with your installation, test the upgrade on comparable hardware first.

>
>   next, are there any issues replacing yum wihth dnf? i found this
> piece:
>
> https://www.vultr.com/docs/use-dnf-to-manage-software-packages-on-centos-7
>
> which suggests it shouldn't be a problem. thoughts?

Being from the EPEL repository, dnf is not supported by CentOS. So I
would avoid using it on a machine which serves a critical function.

>   finally, any concerns i should have about upgrading the kernel from
> 3.10 to 4.14 or 4.15, as explained in a number of places like this:
>
> https://www.tecmint.com/install-upgrade-kernel-version-in-centos-7/
>
>   i simply prefer to run a current kernel but i can resist the
> temptation if upgrading that on a centos 7.4 system would introduce
> more problems than are worth it.
>
>   thoughts?

Again, EL Repo packages are not supported by CentOS. Therefore the above
warnings apply here too.

If, on the other hand, you can afford to tinker with the system and
experiment a bit, then go for it. Oh, and welcome to the CentOS
community.

>
> rday

-- 

Liam

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] a few simple questions about upgrading an "official" centos 7 release

2018-02-22 Thread Pete Biggs

> 
>   finally, any concerns i should have about upgrading the kernel from
> 3.10 to 4.14 or 4.15, as explained in a number of places like this:
> 
> https://www.tecmint.com/install-upgrade-kernel-version-in-centos-7/
> 
>   i simply prefer to run a current kernel but i can resist the
> temptation if upgrading that on a centos 7.4 system would introduce
> more problems than are worth it.
> 
The only reason to use a kernel version that isn't provided with the
distro is if the newer kernel provides features that you **NEED**.

Remember, the whole point of something like CentOS is to provide a
stable, solid OS. This requires a whole bunch of testing of the OS as a
whole - and RHEL (and hence CentOS) does all that testing using kernels
it provides. What's more RH will backport critical kernel updates if
appropriate - so it's not the case that an older kernel is lacking in
security.

I seem to remember you said you were going to teach using these
machines - surely you want those machines to be as stable and as
standard as possible to the machines the students will find in the
wild. I would definitely not encourage students to upgrade kernels -
novices sysadmins don't need an extra level of uncertainty in their
life!

P.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] a few simple questions about upgrading an "official" centos 7 release

2018-02-22 Thread Robert P. J. Day
On Thu, 22 Feb 2018, Pete Biggs wrote:

>
> >
> >   finally, any concerns i should have about upgrading the kernel from
> > 3.10 to 4.14 or 4.15, as explained in a number of places like this:
> >
> > https://www.tecmint.com/install-upgrade-kernel-version-in-centos-7/
> >
> >   i simply prefer to run a current kernel but i can resist the
> > temptation if upgrading that on a centos 7.4 system would introduce
> > more problems than are worth it.
> >
> The only reason to use a kernel version that isn't provided with the
> distro is if the newer kernel provides features that you **NEED**.
>
> Remember, the whole point of something like CentOS is to provide a
> stable, solid OS. This requires a whole bunch of testing of the OS
> as a whole - and RHEL (and hence CentOS) does all that testing using
> kernels it provides. What's more RH will backport critical kernel
> updates if appropriate - so it's not the case that an older kernel
> is lacking in security.
>
> I seem to remember you said you were going to teach using these
> machines - surely you want those machines to be as stable and as
> standard as possible to the machines the students will find in the
> wild. I would definitely not encourage students to upgrade kernels -
> novices sysadmins don't need an extra level of uncertainty in their
> life!

  oh, i appreciate the need for caution; on the other hand, it always
struck me that the training room is the *ideal* place for students to
experiment with things they're too nervous or unsure of to try back at
the office. this is typically why, when i'm teaching, i save friday
afternoon for trying things that are typically not covered by standard
courseware.

  so as long as one delivers the proper caution, i see no problem with
something like, "ok, you might never have to do this at your site, but
just in case you ever need to upgrade your kernel, let's try it and
see what happens." so if the need ever arises, at least they can say
they've done it once and know what the end result is supposed to be.

rday
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] RADIUS

2018-02-22 Thread hw

Gordon Messmer wrote:

On 02/14/2018 08:37 AM, hw wrote:
Then what?  How do I make it so that the users are actually able to authenticate? 



Look for documentation on 802.11x authentication for the specific client you 
want to authenticate.


Thanks, I figured it is what I might need to look into.  How about
a client that uses PXE boot?


WiFi is pretty straightforward.  You're probably accustomed to authenticating 
with WPA2 Personal.  With RADIUS, you'll use WPA2 Enterprise.  Users will be 
asked for their RADIUS credentials when you select that  option.


That seems neither useful, nor feasible for customers wanting to use the
wireless network we would set up for them with their cell phones.  Are
cell phones even capable of this kind of authentication?


Ethernet is fairly similar to WPA2 Enterprise for WiFi.  Under GNOME, for 
instance, you can open the Network configuration tool, click on the 
configuration gear for the wired connection, and then select the Security tab.  
Tun on 802.1x Security, and then you'll have the option to select an 
authentication type that matches your switch and RADIUS configuration.  This 
will vary from client platform to client platform, but it's basically the same 
as WiFi authentication:


I´m not using gnome; I recently tried it, and it´s totally bloated,
yet doesn´t even have a usable window manager.

Anyway, there are some clients that can probably authenticate, which
leaves the ones that use PXE boot.  I tried things out with a switch,
and it would basically work.  If it makes sense to go any further with
this and how now needs to be determined ...



https://en.wikipedia.org/wiki/IEEE_802.1X#Supplicants

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] a few simple questions about upgrading an "official" centos 7 release

2018-02-22 Thread hw

Robert P. J. Day wrote:

On Thu, 22 Feb 2018, Pete Biggs wrote:





   finally, any concerns i should have about upgrading the kernel from
3.10 to 4.14 or 4.15, as explained in a number of places like this:

https://www.tecmint.com/install-upgrade-kernel-version-in-centos-7/

   i simply prefer to run a current kernel but i can resist the
temptation if upgrading that on a centos 7.4 system would introduce
more problems than are worth it.


The only reason to use a kernel version that isn't provided with the
distro is if the newer kernel provides features that you **NEED**.

Remember, the whole point of something like CentOS is to provide a
stable, solid OS. This requires a whole bunch of testing of the OS
as a whole - and RHEL (and hence CentOS) does all that testing using
kernels it provides. What's more RH will backport critical kernel
updates if appropriate - so it's not the case that an older kernel
is lacking in security.

I seem to remember you said you were going to teach using these
machines - surely you want those machines to be as stable and as
standard as possible to the machines the students will find in the
wild. I would definitely not encourage students to upgrade kernels -
novices sysadmins don't need an extra level of uncertainty in their
life!


   oh, i appreciate the need for caution; on the other hand, it always
struck me that the training room is the *ideal* place for students to
experiment with things they're too nervous or unsure of to try back at
the office. this is typically why, when i'm teaching, i save friday
afternoon for trying things that are typically not covered by standard
courseware.

   so as long as one delivers the proper caution, i see no problem with
something like, "ok, you might never have to do this at your site, but
just in case you ever need to upgrade your kernel, let's try it and
see what happens." so if the need ever arises, at least they can say
they've done it once and know what the end result is supposed to be.


The students you need to teach things like this are the ones that will
never become good admins.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] a few simple questions about upgrading an "official" centos 7 release

2018-02-22 Thread Robert P. J. Day
On Thu, 22 Feb 2018, hw wrote:

> Robert P. J. Day wrote:

  ... snip ...

> >oh, i appreciate the need for caution; on the other hand, it
> > always struck me that the training room is the *ideal* place for
> > students to experiment with things they're too nervous or unsure
> > of to try back at the office. this is typically why, when i'm
> > teaching, i save friday afternoon for trying things that are
> > typically not covered by standard courseware.
> >
> >so as long as one delivers the proper caution, i see no problem
> > with something like, "ok, you might never have to do this at your
> > site, but just in case you ever need to upgrade your kernel, let's
> > try it and see what happens." so if the need ever arises, at least
> > they can say they've done it once and know what the end result is
> > supposed to be.
>
> The students you need to teach things like this are the ones that
> will never become good admins.

  uh, that's kind of a condescending attitude to take towards students
who simply want to learn. are you this way with everyone?

rday
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] RADIUS

2018-02-22 Thread John Hodrien

On Thu, 22 Feb 2018, hw wrote:


That seems neither useful, nor feasible for customers wanting to use the
wireless network we would set up for them with their cell phones.  Are cell
phones even capable of this kind of authentication?


Yes, entirely capable.  WPA2-Enterprise isn't some freakish and unusual
solution.

https://www.eduroam.org/

I configure wireless once on my device (phone/tablet/laptop) and then can
travel to institutions all round the world and use their networks seamlessly.
How useless and infeasible indeed.


Anyway, there are some clients that can probably authenticate, which leaves
the ones that use PXE boot.  I tried things out with a switch, and it would
basically work.  If it makes sense to go any further with this and how now
needs to be determined ...


A client that can't authenticate gets the network it's provided with by being
unauthenticated.  If an unauthenticated client can't have any network access,
that's what they get.  Presumably you could drop an unauthenticated machine
into a different VLAN.

jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] a few simple questions about upgrading an "official" centos 7 release

2018-02-22 Thread hw

Robert P. J. Day wrote:

On Thu, 22 Feb 2018, hw wrote:


Robert P. J. Day wrote:


   ... snip ...


oh, i appreciate the need for caution; on the other hand, it
always struck me that the training room is the *ideal* place for
students to experiment with things they're too nervous or unsure
of to try back at the office. this is typically why, when i'm
teaching, i save friday afternoon for trying things that are
typically not covered by standard courseware.

so as long as one delivers the proper caution, i see no problem
with something like, "ok, you might never have to do this at your
site, but just in case you ever need to upgrade your kernel, let's
try it and see what happens." so if the need ever arises, at least
they can say they've done it once and know what the end result is
supposed to be.


The students you need to teach things like this are the ones that
will never become good admins.


   uh, that's kind of a condescending attitude to take towards students
who simply want to learn. are you this way with everyone?


Yes, and there´s nothing condescending about this.  A student who is too
chicken to try out basic things, be it within dedicated testing environments
or, if need be, otherwise, will not become a good admin and is probably
not a person well suited to bearing the responsibility that will be bestowed
upon them, partly due to a lack of good judgement.

I think that is something you should teach your students --- in the hope that
their attitude may change.  Isn´t that your intention to begin with?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Cisco AnyConnect Mobility Client for 32- bit CentOS 6

2018-02-22 Thread H
On February 22, 2018 2:01:25 AM EST, Sorin Srbu  wrote:
>> -Original Message-
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of H
>> Sent: den 22 februari 2018 03:36
>> To: Centos Mailing List 
>> Subject: [CentOS] Cisco AnyConnect Mobility Client for 32- bit CentOS
>6
>> 
>> I have the above installed on a couple of 64-bit systems, both CentOS
>6
>and
>> CentOS 7, where the client works fine.
>> 
>> Now, however, I have installed the 32-bit version of CentOS 6 on a
>netbook
>> but I cannot get the Cisco website installer to recognize the
>> computer/operating system, not even displaying any error message.
>> 
>> Does anyone have the client running on a 32-bit system? I have been
>told
>it
>> should run on a 32-bit system and did have it running on the same
>netbook
>> while it was still running Vista Home edition, another 32-bit
>operating
>system.
>
>I use that VPN-client at home on a CentOS 7 x64-system.
>I recall trying to get it to work a few years back while running CentOS
>6
>32b, but never managed. 
>Opted to install CentOS 6 x64 instead.
>
>Can the netbook handle 64b CentOS?
>--
>//Sorin
>___
>CentOS mailing list
>CentOS@centos.org
>https://lists.centos.org/mailman/listinfo/centos

It's a 32-bit computer.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Cisco AnyConnect Mobility Client for 32- bit CentOS 6

2018-02-22 Thread H
On February 22, 2018 3:46:25 AM EST, Nux!  wrote:
>Install the excellent openconnect client from EPEL, I think there is
>also a NetworkManager plugin for it so you can use a UI, though the cli
>is not too bad.
>
>--
>Sent from the Delta quadrant using Borg technology!
>
>Nux!
>www.nux.ro
>
>- Original Message -
>> From: "H" 
>> To: "CentOS mailing list" 
>> Sent: Thursday, 22 February, 2018 02:35:33
>> Subject: [CentOS] Cisco AnyConnect Mobility Client for 32- bit CentOS
>6
>
>> I have the above installed on a couple of 64-bit systems, both CentOS
>6 and
>> CentOS 7, where the client works fine.
>> 
>> Now, however, I have installed the 32-bit version of CentOS 6 on a
>netbook but I
>> cannot get the Cisco website installer to recognize the
>computer/operating
>> system, not even displaying any error message.
>> 
>> Does anyone have the client running on a 32-bit system? I have been
>told it
>> should run on a 32-bit system and did have it running on the same
>netbook while
>> it was still running Vista Home edition, another 32-bit operating
>system.
>> 
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>___
>CentOS mailing list
>CentOS@centos.org
>https://lists.centos.org/mailman/listinfo/centos

Thank you, the client works nicely! It needs to be run as root and then a 
regular user gets the benefit of the VPN connection.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Ubiquiti Model UAP-AC-PRO

2018-02-22 Thread Paul Schoonderwoerd
>Everyone,
>
>Have any of you installed ubiguiti wireless routers on your network?
>
>It looks like the setup requires the use of software;  they have some
>packages that are ready made for Ubuntu and Debian, but not RedHat
>
>https://www.ubnt.com/download/unifi/unifi-ap-ac-pro[1]
_>_
>Have any of you tried or succeeded in installation this on Centos 7.4?
>
>Greg Ennis
To install just the one access point, just download their app on your phone and 
configure 
it. Very easy.

For a full Ubiquity network you can install the software on a Linux machine or 
buy the 
Cloud key, same software running on a small RaspberryPi like box (needs POE 
connection). 
Makes managing the components much much easier.

Paul Schoonderwoerd
Pollux IT


[1] https://www.ubnt.com/download/unifi/unifi-ap-ac-pro
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] RADIUS

2018-02-22 Thread Gordon Messmer

On 02/22/2018 03:22 AM, hw wrote:

Gordon Messmer wrote:
Look for documentation on 802.11x authentication for the specific 
client you want to authenticate.


Thanks, I figured it is what I might need to look into.  How about
a client that uses PXE boot?


Provide PXE (dhcp, dns, tftp) on an unauthenticated VLAN.  Your original 
email suggested that you'd want users to auth before a system would 
boot, but that's probably not possible.  If you want to authenticate 
users via username and password using RADIUS, then there has to be an OS 
running to provide an interface in which they provide credentials.  It's 
not really clear how else you'd imagine that working.


WiFi is pretty straightforward.  You're probably accustomed to 
authenticating with WPA2 Personal.  With RADIUS, you'll use WPA2 
Enterprise.  Users will be asked for their RADIUS credentials when 
you select that  option.


That seems neither useful, nor feasible for customers wanting to use the
wireless network we would set up for them with their cell phones. Are
cell phones even capable of this kind of authentication?


Well, I guess I'm confused because having explained where you'd find the 
interface in which users will provide their RADIUS username and 
password, you think this process is unfeasible.  Perhaps you could 
explain what you're looking for, more precisely?


Ethernet is fairly similar to WPA2 Enterprise for WiFi.  Under GNOME, 
for instance, you can open the Network configuration tool, click on 
the configuration gear for the wired connection, and then select the 
Security tab.  Tun on 802.1x Security, and then you'll have the 
option to select an authentication type that matches your switch and 
RADIUS configuration.  This will vary from client platform to client 
platform, but it's basically the same as WiFi authentication:


I´m not using gnome; I recently tried it, and it´s totally bloated,
yet doesn´t even have a usable window manager.


OK.  I'm not sure how your opinion of GNOME is really relevant.  I'm 
describing it because it's an example that's probably within reach for 
both you and me, given that you and I are communicating via a GNU/Linux 
focused mailing list.


I'm sorry my voluntary attempt to help you out wasn't to your liking.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos