Re: [PacketFence-users] ANN: PacketFence v11.1

2021-11-01 Thread ypefti--- via PacketFence-users 
Appreciate your reply, Ludovic!

I had some time during the weekend and dig it deeper and found this guide. Did 
the upgrade of the database and rebooted PF at the end. To my surprise it 
couldn’t be started with and threw me this error:

 

Failed to connect to config service for namespace resource::URI_Filters(), 
retrying

 

I wasn’t really concerned about it and deployed your new ZEN appliance running 
ver 11 of PF and restored the database into it. For the sake of knowing the 
product inside out it would be nice to know the reason of this error but 
overall all is good, thanks again

 

Eugene

 

 

From: Zammit, Ludovic  
Sent: Monday, November 1, 2021 5:13 AM
To: ype...@gmail.com
Cc: packetfence-users@lists.sourceforge.net
Subject: Re: [PacketFence-users] ANN: PacketFence v11.1

 

Hello Eugene,

 

It looks like you have not follow all the steps mentioned here:

 

https://github.com/inverse-inc/packetfence/blob/devel/docs/PacketFence_Upgrade_Guide.asciidoc#upgrading-from-a-version-prior-to-1030

 

Thanks,

 


Ludovic Zammit
Product Support Engineer Principal


  
<https://www.akamai.com/us/en/multimedia/images/custom/2019/logo-no-tag-93x45.png>
 



Cell: +1.613.670.8432

Akamai Technologies - Inverse
145 Broadway
Cambridge, MA 02142




Connect with Us:

 <https://community.akamai.com/>  <http://blogs.akamai.com/>  
<https://twitter.com/akamai>  <http://www.facebook.com/AkamaiTechnologies>  
<http://www.linkedin.com/company/akamai-technologies>  
<http://www.youtube.com/user/akamaitechnologies?feature=results_main> 







On Oct 29, 2021, at 7:54 PM, ypefti--- via PacketFence-users 
mailto:packetfence-users@lists.sourceforge.net> > wrote:

 

Many apologies for spamming but I think I made some progress toward the upgrade.

Upon the successful completion I ran into the error database schema 

 

FATAL - The PacketFence database schema version 'unknown' does not match the 
current installed version '10.3.0'

 

I thought that I don’t need to rebuild it since I was on version 10.2.0

Would appreciate an advice how to rebuild the schema

 

Eugene

 

From: ype...@gmail.com <mailto:ype...@gmail.com>  mailto:ype...@gmail.com> > 
Sent: Friday, October 29, 2021 4:01 PM
To: 'Fabrice Durand' mailto:oeufd...@gmail.com> >; 
packetfence-users@lists.sourceforge.net 
<mailto:packetfence-users@lists.sourceforge.net> 
Cc: packetfence-annou...@lists.sourceforge.net 
<mailto:packetfence-annou...@lists.sourceforge.net> ; 
packetfence-de...@lists.sourceforge.net 
<mailto:packetfence-de...@lists.sourceforge.net> 
Subject: RE: [PacketFence-users] ANN: PacketFence v11.1

 

Essentially it errors on MariaDB-client installation 

 



Package   ArchVersion   
Repository  
  Size



Updating:

MariaDB-clientx86_64  
10.2.37-1.el7.centos  
packetfence   11 M

MariaDB-commonx86_64  
10.2.37-1.el7.centos  
packetfence   81 k

MariaDB-serverx86_64  
10.2.37-1.el7.centos  
packetfence   24 M

fingerbanknoarch  
4.2.1-20200722165131.169595742.0007.v4.2.1.el7
packetfence  115 M

fingerbank-collector  x86_64  
1.3.17-1.el7  
packetfence  4.5 M

lasso x86_64  2.7.0-2.1 
packetfence 
 195 k

lasso-perlx86_64  2.7.0-2.1 
packetfence 
 165 k

packetfence   x86_64  
10.3.0-20210414154410.286398790.0007.v10.3.0.el7  
packetfence   73 M

packetfence-release   noarch  
2.1.0-20210414154410.286398790.0007.v10.3.0.el7   
packetfence  6

Re: [PacketFence-users] ANN: PacketFence v11.1

2021-11-01 Thread Zammit, Ludovic via PacketFence-users 
Hello Eugene,

It looks like you have not follow all the steps mentioned here:

https://github.com/inverse-inc/packetfence/blob/devel/docs/PacketFence_Upgrade_Guide.asciidoc#upgrading-from-a-version-prior-to-1030
 
<https://github.com/inverse-inc/packetfence/blob/devel/docs/PacketFence_Upgrade_Guide.asciidoc#upgrading-from-a-version-prior-to-1030>

Thanks,

Ludovic Zammit
Product Support Engineer Principal

Cell: +1.613.670.8432
Akamai Technologies - Inverse
145 Broadway
Cambridge, MA 02142
Connect with Us: <https://community.akamai.com/>  
<http://blogs.akamai.com/>  <https://twitter.com/akamai>  
<http://www.facebook.com/AkamaiTechnologies>  
<http://www.linkedin.com/company/akamai-technologies>  
<http://www.youtube.com/user/akamaitechnologies?feature=results_main>

> On Oct 29, 2021, at 7:54 PM, ypefti--- via PacketFence-users 
>  wrote:
> 
> Many apologies for spamming but I think I made some progress toward the 
> upgrade.
> Upon the successful completion I ran into the error database schema 
>  
> FATAL - The PacketFence database schema version 'unknown' does not match the 
> current installed version '10.3.0'
>  
> I thought that I don’t need to rebuild it since I was on version 10.2.0
> Would appreciate an advice how to rebuild the schema
>  
> Eugene
>  
> From: ype...@gmail.com <mailto:ype...@gmail.com>  <mailto:ype...@gmail.com>> 
> Sent: Friday, October 29, 2021 4:01 PM
> To: 'Fabrice Durand' mailto:oeufd...@gmail.com>>; 
> packetfence-users@lists.sourceforge.net 
> <mailto:packetfence-users@lists.sourceforge.net>
> Cc: packetfence-annou...@lists.sourceforge.net 
> <mailto:packetfence-annou...@lists.sourceforge.net>; 
> packetfence-de...@lists.sourceforge.net 
> <mailto:packetfence-de...@lists.sourceforge.net>
> Subject: RE: [PacketFence-users] ANN: PacketFence v11.1
>  
> Essentially it errors on MariaDB-client installation 
>  
> 
> Package   ArchVersion 
>   Repository  
>   Size
> 
> Updating:
> MariaDB-clientx86_64  
> 10.2.37-1.el7.centos  
> packetfence   11 M
> MariaDB-commonx86_64  
> 10.2.37-1.el7.centos  
> packetfence   81 k
> MariaDB-serverx86_64  
> 10.2.37-1.el7.centos  
> packetfence   24 M
> fingerbanknoarch  
> 4.2.1-20200722165131.169595742.0007.v4.2.1.el7
> packetfence  115 M
> fingerbank-collector  x86_64  
> 1.3.17-1.el7  
> packetfence  4.5 M
> lasso x86_64  
> 2.7.0-2.1 
> packetfence  195 k
> lasso-perlx86_64  
> 2.7.0-2.1 
> packetfence  165 k
> packetfence   x86_64  
> 10.3.0-20210414154410.286398790.0007.v10.3.0.el7  
> packetfence   73 M
> packetfence-release   noarch  
> 2.1.0-20210414154410.286398790.0007.v10.3.0.el7   
> packetfence  6.1 k
> Installing for dependencies:
> MariaDB-compatx86_64  
> 10.2.37-1.el7.centos  
> packetfence  2.2 M
> perl-Crypt-PBKDF2 noarch  
> 0.150900-1.el7
> packetfence   37 k
> perl-Digest-SHA3  x86_64  
> 0.24-1.el7
> packetfence

Re: [PacketFence-users] ANN: PacketFence v11.1

2021-10-29 Thread ypefti--- via PacketFence-users 
Many apologies for spamming but I think I made some progress toward the upgrade.

Upon the successful completion I ran into the error database schema 

 

FATAL - The PacketFence database schema version 'unknown' does not match the 
current installed version '10.3.0'

 

I thought that I don’t need to rebuild it since I was on version 10.2.0

Would appreciate an advice how to rebuild the schema

 

Eugene

 

From: ype...@gmail.com  
Sent: Friday, October 29, 2021 4:01 PM
To: 'Fabrice Durand' ; 
packetfence-users@lists.sourceforge.net
Cc: packetfence-annou...@lists.sourceforge.net; 
packetfence-de...@lists.sourceforge.net
Subject: RE: [PacketFence-users] ANN: PacketFence v11.1

 

Essentially it errors on MariaDB-client installation 

 



Package   ArchVersion   
Repository  
  Size



Updating:

MariaDB-clientx86_64  
10.2.37-1.el7.centos  
packetfence   11 M

MariaDB-commonx86_64  
10.2.37-1.el7.centos  
packetfence   81 k

MariaDB-serverx86_64  
10.2.37-1.el7.centos  
packetfence   24 M

fingerbanknoarch  
4.2.1-20200722165131.169595742.0007.v4.2.1.el7
packetfence  115 M

fingerbank-collector  x86_64  
1.3.17-1.el7  
packetfence  4.5 M

lasso x86_64  2.7.0-2.1 
packetfence 
 195 k

lasso-perlx86_64  2.7.0-2.1 
packetfence 
 165 k

packetfence   x86_64  
10.3.0-20210414154410.286398790.0007.v10.3.0.el7  
packetfence   73 M

packetfence-release   noarch  
2.1.0-20210414154410.286398790.0007.v10.3.0.el7   
packetfence  6.1 k

Installing for dependencies:

MariaDB-compatx86_64  
10.2.37-1.el7.centos  
packetfence  2.2 M

perl-Crypt-PBKDF2 noarch  
0.150900-1.el7
packetfence   37 k

perl-Digest-SHA3  x86_64  
0.24-1.el7
packetfence   32 k

 



 

Transaction check error:

  file /usr/lib64/libmysqlclient.so.18.0.0 from install of 
MariaDB-compat-10.2.37-1.el7.centos.x86_64 conflicts with file from package 
MariaDB-shared-10.1.21-1.el7.centos.x86_64

  file /usr/lib64/libmysqlclient_r.so.18 from install of 
MariaDB-compat-10.2.37-1.el7.centos.x86_64 conflicts with file from package 
MariaDB-shared-10.1.21-1.el7.centos.x86_64

  file /usr/lib64/libmysqlclient_r.so.18.0.0 from install of 
MariaDB-compat-10.2.37-1.el7.centos.x86_64 conflicts with file from package 
MariaDB-shared-10.1.21-1.el7.centos.x86_64

 

From: Fabrice Durand mailto:oeufd...@gmail.com> > 
Sent: Friday, October 29, 2021 3:51 PM
To: packetfence-users@lists.sourceforge.net 
<mailto:packetfence-users@lists.sourceforge.net> 
Cc: packetfence-annou...@lists.sourceforge.net 
<mailto:packetfence-annou...@lists.sourceforge.net> ; 
packetfence-de...@lists.sourceforge.net 
<mailto:packetfence-de...@lists.sourceforge.net> ; ype...@gmail.com 
<mailto:ype...@gmail.com> 
Subject: Re: [PacketFence-users] ANN: PacketFence v11.1

 

Redhat8 or Debian11

 

Le ven. 29 oct. 2021, 18 h 30, ypefti--- via PacketFence-users 
mailto:packetfence-users@lists.sourceforge.net> > a écrit :

Good news, thanks, Ludovic.

I grasped for this opportunity to try to upgrade ours to the new release while 
we are not in production mode now.

Followed the official docu

Re: [PacketFence-users] ANN: PacketFence v11.1

2021-10-29 Thread Fabrice Durand via PacketFence-users 
r
> FAILED
> -] 3.8 MB/s | 505 MB  00:00:14 ETA
>
>
> http://mirror.esecuredata.com/centos/7.9.2009/updates/x86_64/Packages/perl-5.16.3-299.el7_9.x86_64.rpm:
> [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
>
> Trying other mirror.
>
> (142/201):
> perl-ExtUtils-Install-1.58-299.el7_9.noarch.rpm
> |  75 kB  00:00:00
>
> (
>
> samba-4.10.16-15.el7_9.x86_64. FAILED
>   =-   ] 3.2 MB/s | 516 MB  00:00:13 ETA
>
>
> http://mirror.esecuredata.com/centos/7.9.2009/updates/x86_64/Packages/samba-4.10.16-15.el7_9.x86_64.rpm:
> [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
>
> Trying other mirror.
>
> (165/201):
> samba-common-4.10.16-15.el7_9.noarch.rpm
> | 215 kB  00:00:00
>
> (166/201):
> samba-common-libs-4.10.16-15.el7_9.x86_64.rpm
> | 182 kB  00:00:00
>
> samba-winbind-4.10.16-15.el7_9
> FAILED
>
>
> http://mirror.esecuredata.com/centos/7.9.2009/updates/x86_64/Packages/samba-winbind-4.10.16-15.el7_9.x86_64.rpm:
> [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
>
> Trying other mirror.
>
> util-linux-2.23.2-65.el7_9.1.x
> FAILED
> =======  ] 2.4 MB/s | 539 MB  00:00:08 ETA
>
>
> http://mirror.esecuredata.com/centos/7.9.2009/updates/x86_64/Packages/util-linux-2.23.2-65.el7_9.1.x86_64.rpm:
> [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
>
> Trying other mirror.
>
> Error downloading packages:
>
>   perl-Crypt-PBKDF2-0.150900-1.el7.noarch: [Errno 256] No more mirrors to
> try.
>
>
>
> Eugene
>
>
>
> *From:* Ludovic Marcotte via PacketFence-users <
> packetfence-users@lists.sourceforge.net>
> *Sent:* Friday, October 29, 2021 10:44 AM
> *To:* packetfence-annou...@lists.sourceforge.net;
> packetfence-de...@lists.sourceforge.net;
> packetfence-users@lists.sourceforge.net
> *Cc:* Ludovic Marcotte 
> *Subject:* [PacketFence-users] ANN: PacketFence v11.1
>
>
>
> The Inverse team is pleased to announce the immediate availability of
> PacketFence v11.1. This is a major release with new features, enhancements
> and bug fixes. This release is considered ready for production use and
> upgrading from previous versions is strongly advised.
> What is PacketFence?
>
> PacketFence is a fully supported, trusted, Free and Open Source Network
> Access Control (NAC) solution. Boasting an impressive feature set,
> PacketFence can be used to effectively secure small to very large
> heterogeneous networks.
>
> Among the features provided by PacketFence, there are:
>
>- powerful BYOD (Bring Your Own Device) capabilities
>- multiple enforcement methods including Role-Based Access Control
>(RBAC) and hotspot-style
>- built-in network behaviour anomaly detection
>- state-of-the art devices identification with Fingerbank
>- compliance checks for endpoints present on your network
>- integration with various vulnerability scanners, intrusion detection
>solutions, security agents and firewalls
>- bandwidth accounting for all devices
>
> A complete overview of the solution is available from the official
> website: https://packetfence.org/about.html
> Changes Since Previous Release
>
> *New Features*
>
>- Support for Akamai MFA in VPN/CLI RADIUS authentication and on the
>captive portal
>- Support for TOTP MFA in VPN/CLI RADIUS authentication and on the
>captive portal
>- Automation of upgrades for standalone installations (#6583)
>
> *Enhancements*
>
>- MikroTik DHCP MAC authentication support
>- Allow to use the sAMAccountName from the searchattributes in MSCHAP
>machine authentication (#6586)
>- Improve the Data Access Layer to work in MariaDB's default sql_mode
>- New command pfcmd mariadb [mariadb options]
>- Deauth request can be made on the previous equipment the device was
>connected
>- Allow the bulk import of config items to be async
>- Remove unused/deprecated sources (AuthorizeNet, Instagram, Twitter,
>Pinterest, and Mirapay) (#6560)
>- Automation of supported equipment page on PacketFence website (#6611)
>- Use Venom 1.0.0 through Ansible to run integration tests (#6573)
>- Import script will migrate the networks configuration if the new IP
>is in the same subnet (#6636)
>- EAP-TLS integration tests using manual deployment and SCEP protocol
>(#6647)
>- Added a monit check to ensure winbindd is still connected (11.1 - AD
>failover doesn’t work #6655)
>- Improve ZEN builds (#6663)
>
> *Bug Fixes*
>
>- Match the realm mor

Re: [PacketFence-users] ANN: PacketFence v11.1

2021-10-29 Thread ypefti--- via PacketFence-users 
And yet another error on the second attempt to run the upgrade, I’m currently 
on ver 10.2.0

 

Install2 Packages (+19 Dependent packages)

Upgrade  180 Packages

 

Total size: 558 M

Is this ok [y/d/N]: y

Downloading packages:

Running transaction check

Running transaction test

 

Transaction check error:

  file /usr/lib64/libmysqlclient.so.18.0.0 from install of 
MariaDB-compat-10.2.37-1.el7.centos.x86_64 conflicts with file from package 
MariaDB-shared-10.1.21-1.el7.centos.x86_64

 file /usr/lib64/libmysqlclient_r.so.18 from install of 
MariaDB-compat-10.2.37-1.el7.centos.x86_64 conflicts with file from package 
MariaDB-shared-10.1.21-1.el7.centos.x86_64

  file /usr/lib64/libmysqlclient_r.so.18.0.0 from install of 
MariaDB-compat-10.2.37-1.el7.centos.x86_64 conflicts with file from package 
MariaDB-shared-10.1.21-1.el7.centos.x86_64

 

Error Summary

 

 

 

From: ype...@gmail.com  
Sent: Friday, October 29, 2021 3:16 PM
To: packetfence-users@lists.sourceforge.net; 
packetfence-annou...@lists.sourceforge.net; 
packetfence-de...@lists.sourceforge.net
Cc: 'Ludovic Marcotte' 
Subject: RE: [PacketFence-users] ANN: PacketFence v11.1

 

Good news, thanks, Ludovic.

I grasped for this opportunity to try to upgrade ours to the new release while 
we are not in production mode now.

Followed the official document for CentOS/Redhat based systems. 

Set it up for an update with yum and ran into these errors while downloading 
dependencies.

How can I safely disregard them to proceed with the upgrade ?

 

Total download size: 558 M

Is this ok [y/d/N]: y

Downloading packages:

No Presto metadata available for packetfence

No Presto metadata available for base

No Presto metadata available for updates

(1/201): MariaDB-common-10.2.37-1.el7.centos.x86_64.rpm 
   |  81 kB  00:00:00 

(2/201): MariaDB-compat-10.2.37-1.el7.centos.x86_64.rpm 
   | 2.2 MB  00:00:00 

(3/201): ImageMagick-perl-6.9.10.68-6.el7_9.x86_64.rpm  
   | 154 kB  00:00:00 

(4/201): MariaDB-client-10.2.37-1.el7.centos.x86_64.rpm 
   |  11 MB  00:00:01 

(5/201): MariaDB-server-10.2.37-1.el7.centos.x86_64.rpm 
   |  24 MB  00:00:01 

(6/201): ImageMagick-6.9.10.68-6.el7_9.x86_64.rpm   
   | 2.3 MB  00:00:05 

(7/201): NetworkManager-1.18.8-2.el7_9.x86_64.rpm   
   | 1.9 MB  00:00:05 

(8/201): NetworkManager-team-1.18.8-2.el7_9.x86_64.rpm  
   | 165 kB  00:00:00 

(9/201): apr-1.4.8-7.el7.x86_64.rpm 
   | 104 kB  00:00:00 

(10/201): OpenEXR-libs-1.7.1-8.el7.x86_64.rpm   
   | 217 kB  00:00:00 

(11/201): NetworkManager-tui-1.18.8-2.el7_9.x86_64.rpm  
   | 329 kB  00:00:01 

(12/201): bc-1.06.95-13.el7.x86_64.rpm  
   | 115 kB  00:00:00 

(13/201): centos-release-7-9.2009.1.el7.centos.x86_64.rpm   
   |  27 kB  00:00:00 

(14/201): ca-certificates-2021.2.50-72.el7_9.noarch.rpm 
   | 379 kB  00:00:00 

coreutils-8.22-24.el7_9.2.x86_ FAILED   
] 2.4 MB/s |  44 MB  00:03:31 ETA 

http://muug.ca/mirror/centos/7.9.2009/updates/x86_64/Packages/coreutils-8.22-24.el7_9.2.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

iproute-4.11.0-30.el7.x86_64.r FAILED  
-]  20 MB/s | 214 MB  00:00:17 ETA 

http://mirror.esecuredata.com/centos/7.9.2009/os/x86_64/Packages/iproute-4.11.0-30.el7.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

 

net-snmp-perl-5.7.2-49.el7_9.1 FAILED  

http://centos.mirror.iweb.ca/7.9.2009/updates/x86_64/Packages/net-snmp-perl-5.7.2-49.el7_9.1.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

(134/201): openldap-2.4.44-24.el7_9.x86_64.rpm  
   | 356 kB  00:00:00 

openssl-1.0.2k-22.el7_9.x86_64 FAILED  
 ] 7.1 MB/s

Re: [PacketFence-users] ANN: PacketFence v11.1

2021-10-29 Thread ypefti--- via PacketFence-users 
Redhat or rather CentOS - CentOS Linux release 7.9.2009 (Core)

 

From: Fabrice Durand  
Sent: Friday, October 29, 2021 3:51 PM
To: packetfence-users@lists.sourceforge.net
Cc: packetfence-annou...@lists.sourceforge.net; 
packetfence-de...@lists.sourceforge.net; ype...@gmail.com
Subject: Re: [PacketFence-users] ANN: PacketFence v11.1

 

Redhat8 or Debian11

 

Le ven. 29 oct. 2021, 18 h 30, ypefti--- via PacketFence-users 
mailto:packetfence-users@lists.sourceforge.net> > a écrit :

Good news, thanks, Ludovic.

I grasped for this opportunity to try to upgrade ours to the new release while 
we are not in production mode now.

Followed the official document for CentOS/Redhat based systems. 

Set it up for an update with yum and ran into these errors while downloading 
dependencies.

How can I safely disregard them to proceed with the upgrade ?

 

Total download size: 558 M

Is this ok [y/d/N]: y

Downloading packages:

No Presto metadata available for packetfence

No Presto metadata available for base

No Presto metadata available for updates

(1/201): MariaDB-common-10.2.37-1.el7.centos.x86_64.rpm 
   |  81 kB  00:00:00 

(2/201): MariaDB-compat-10.2.37-1.el7.centos.x86_64.rpm 
   | 2.2 MB  00:00:00 

(3/201): ImageMagick-perl-6.9.10.68-6.el7_9.x86_64.rpm  
   | 154 kB  00:00:00 

(4/201): MariaDB-client-10.2.37-1.el7.centos.x86_64.rpm 
   |  11 MB  00:00:01 

(5/201): MariaDB-server-10.2.37-1.el7.centos.x86_64.rpm 
   |  24 MB  00:00:01 

(6/201): ImageMagick-6.9.10.68-6.el7_9.x86_64.rpm   
   | 2.3 MB  00:00:05 

(7/201): NetworkManager-1.18.8-2.el7_9.x86_64.rpm   
   | 1.9 MB  00:00:05 

(8/201): NetworkManager-team-1.18.8-2.el7_9.x86_64.rpm  
   | 165 kB  00:00:00 

(9/201): apr-1.4.8-7.el7.x86_64.rpm 
   | 104 kB  00:00:00 

(10/201): OpenEXR-libs-1.7.1-8.el7.x86_64.rpm   
   | 217 kB  00:00:00 

(11/201): NetworkManager-tui-1.18.8-2.el7_9.x86_64.rpm  
   | 329 kB  00:00:01 

(12/201): bc-1.06.95-13.el7.x86_64.rpm  
   | 115 kB  00:00:00 

(13/201): centos-release-7-9.2009.1.el7.centos.x86_64.rpm   
   |  27 kB  00:00:00 

(14/201): ca-certificates-2021.2.50-72.el7_9.noarch.rpm 
   | 379 kB  00:00:00 

coreutils-8.22-24.el7_9.2.x86_ FAILED   
] 2.4 MB/s |  44 MB  00:03:31 ETA 

http://muug.ca/mirror/centos/7.9.2009/updates/x86_64/Packages/coreutils-8.22-24.el7_9.2.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

iproute-4.11.0-30.el7.x86_64.r FAILED  
-]  20 MB/s | 214 MB  00:00:17 ETA 

http://mirror.esecuredata.com/centos/7.9.2009/os/x86_64/Packages/iproute-4.11.0-30.el7.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

net-snmp-perl-5.7.2-49.el7_9.1 FAILED  

http://centos.mirror.iweb.ca/7.9.2009/updates/x86_64/Packages/net-snmp-perl-5.7.2-49.el7_9.1.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

(134/201): openldap-2.4.44-24.el7_9.x86_64.rpm  
   | 356 kB  00:00:00 

openssl-1.0.2k-22.el7_9.x86_64 FAILED  
 ] 7.1 MB/s | 358 MB  00:00:28 ETA 

http://mirror.esecuredata.com/centos/7.9.2009/updates/x86_64/Packages/openssl-1.0.2k-22.el7_9.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

(135/201): 
packetfence-release-2.1.0-20210414154410.286398790.0007.v10.3.0.el7.noarch.rpm  
| 6.1 kB  00:00:00 

(136/201): pcre-devel-8.32-17.el7.x86_64.rpm
   | 480 kB  00:00:00 

(137/201): openssl-libs-1.0.2k-22.el7_9.x86_64.rpm  
   | 1.2 MB  00:00:

Re: [PacketFence-users] ANN: PacketFence v11.1

2021-10-29 Thread ypefti--- via PacketFence-users 
Essentially it errors on MariaDB-client installation 

 



Package   ArchVersion   
Repository  
  Size



Updating:

MariaDB-clientx86_64  
10.2.37-1.el7.centos  
packetfence   11 M

MariaDB-commonx86_64  
10.2.37-1.el7.centos  
packetfence   81 k

MariaDB-serverx86_64  
10.2.37-1.el7.centos  
packetfence   24 M

fingerbanknoarch  
4.2.1-20200722165131.169595742.0007.v4.2.1.el7
packetfence  115 M

fingerbank-collector  x86_64  
1.3.17-1.el7  
packetfence  4.5 M

lasso x86_64  2.7.0-2.1 
packetfence 
 195 k

lasso-perlx86_64  2.7.0-2.1 
packetfence 
 165 k

packetfence   x86_64  
10.3.0-20210414154410.286398790.0007.v10.3.0.el7  
packetfence   73 M

packetfence-release   noarch  
2.1.0-20210414154410.286398790.0007.v10.3.0.el7   
packetfence  6.1 k

Installing for dependencies:

MariaDB-compatx86_64  
10.2.37-1.el7.centos  
packetfence  2.2 M

perl-Crypt-PBKDF2 noarch  
0.150900-1.el7
packetfence   37 k

perl-Digest-SHA3  x86_64  
0.24-1.el7
packetfence   32 k

 



 

Transaction check error:

  file /usr/lib64/libmysqlclient.so.18.0.0 from install of 
MariaDB-compat-10.2.37-1.el7.centos.x86_64 conflicts with file from package 
MariaDB-shared-10.1.21-1.el7.centos.x86_64

  file /usr/lib64/libmysqlclient_r.so.18 from install of 
MariaDB-compat-10.2.37-1.el7.centos.x86_64 conflicts with file from package 
MariaDB-shared-10.1.21-1.el7.centos.x86_64

  file /usr/lib64/libmysqlclient_r.so.18.0.0 from install of 
MariaDB-compat-10.2.37-1.el7.centos.x86_64 conflicts with file from package 
MariaDB-shared-10.1.21-1.el7.centos.x86_64

 

From: Fabrice Durand  
Sent: Friday, October 29, 2021 3:51 PM
To: packetfence-users@lists.sourceforge.net
Cc: packetfence-annou...@lists.sourceforge.net; 
packetfence-de...@lists.sourceforge.net; ype...@gmail.com
Subject: Re: [PacketFence-users] ANN: PacketFence v11.1

 

Redhat8 or Debian11

 

Le ven. 29 oct. 2021, 18 h 30, ypefti--- via PacketFence-users 
mailto:packetfence-users@lists.sourceforge.net> > a écrit :

Good news, thanks, Ludovic.

I grasped for this opportunity to try to upgrade ours to the new release while 
we are not in production mode now.

Followed the official document for CentOS/Redhat based systems. 

Set it up for an update with yum and ran into these errors while downloading 
dependencies.

How can I safely disregard them to proceed with the upgrade ?

 

Total download size: 558 M

Is this ok [y/d/N]: y

Downloading packages:

No Presto metadata available for packetfence

No Presto metadata available for base

No Presto metadata available for updates

(1/201): MariaDB-common-10.2.37-1.el7.centos.x86_64.rpm 
   |  81 kB  00:00:00 

(2/201): MariaDB-compat-10.2.37-1.el7.centos.x86_64.rpm 
   | 2.2 MB  00:00:00 

(3/201): ImageMagick-perl-6.9.10.68-6.el7_9.x86_64.rpm  
   | 154 kB  00:00:00 

(4/201): MariaDB-client-10.2.37-1.el7.centos.x86_

Re: [PacketFence-users] ANN: PacketFence v11.1

2021-10-29 Thread ypefti--- via PacketFence-users 
x-firmware-20200421-80.git78c0348.el7_9.noarch.rpm   
   |  80 MB  00:00:21 

perl-Crypt-PBKDF2-0.150900-1.e FAILED  

http://inverse.ca/downloads/PacketFence/RHEL7/x86_64/RPMS/perl-Crypt-PBKDF2-0.150900-1.el7.noarch.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

(140/201): perl-ExtUtils-CBuilder-0.28.2.6-299.el7_9.noarch.rpm 
   |  68 kB  00:00:00 

(141/201): perl-Digest-SHA3-0.24-1.el7.x86_64.rpm   
   |  32 kB  00:00:00 

perl-5.16.3-299.el7_9.x86_64.r FAILED  
-] 3.8 MB/s | 505 MB  00:00:14 ETA 

http://mirror.esecuredata.com/centos/7.9.2009/updates/x86_64/Packages/perl-5.16.3-299.el7_9.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

(142/201): perl-ExtUtils-Install-1.58-299.el7_9.noarch.rpm  
   |  75 kB  00:00:00 

( 

samba-4.10.16-15.el7_9.x86_64. FAILED  
=-   ] 3.2 MB/s | 516 MB  00:00:13 ETA 

http://mirror.esecuredata.com/centos/7.9.2009/updates/x86_64/Packages/samba-4.10.16-15.el7_9.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

(165/201): samba-common-4.10.16-15.el7_9.noarch.rpm 
   | 215 kB  00:00:00 

(166/201): samba-common-libs-4.10.16-15.el7_9.x86_64.rpm
   | 182 kB  00:00:00 

samba-winbind-4.10.16-15.el7_9 FAILED  

http://mirror.esecuredata.com/centos/7.9.2009/updates/x86_64/Packages/samba-winbind-4.10.16-15.el7_9.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

util-linux-2.23.2-65.el7_9.1.x FAILED  
===  ] 2.4 MB/s | 539 MB  00:00:08 ETA 

http://mirror.esecuredata.com/centos/7.9.2009/updates/x86_64/Packages/util-linux-2.23.2-65.el7_9.1.x86_64.rpm:
 [Errno 14] curl#56 - "Recv failure: Connection reset by peer"

Trying other mirror.

Error downloading packages:

  perl-Crypt-PBKDF2-0.150900-1.el7.noarch: [Errno 256] No more mirrors to try.

 

Eugene

 

From: Ludovic Marcotte via PacketFence-users 
 
Sent: Friday, October 29, 2021 10:44 AM
To: packetfence-annou...@lists.sourceforge.net; 
packetfence-de...@lists.sourceforge.net; packetfence-users@lists.sourceforge.net
Cc: Ludovic Marcotte 
Subject: [PacketFence-users] ANN: PacketFence v11.1

 

The Inverse team is pleased to announce the immediate availability of 
PacketFence v11.1. This is a major release with new features, enhancements and 
bug fixes. This release is considered ready for production use and upgrading 
from previous versions is strongly advised.


What is PacketFence?


PacketFence is a fully supported, trusted, Free and Open Source Network Access 
Control (NAC) solution. Boasting an impressive feature set, PacketFence can be 
used to effectively secure small to very large heterogeneous networks.

Among the features provided by PacketFence, there are:

*   powerful BYOD (Bring Your Own Device) capabilities
*   multiple enforcement methods including Role-Based Access Control (RBAC) 
and hotspot-style
*   built-in network behaviour anomaly detection
*   state-of-the art devices identification with Fingerbank
*   compliance checks for endpoints present on your network
*   integration with various vulnerability scanners, intrusion detection 
solutions, security agents and firewalls
*   bandwidth accounting for all devices

A complete overview of the solution is available from the official website:  
<https://packetfence.org/about.html> https://packetfence.org/about.html


Changes Since Previous Release


New Features

*   Support for Akamai MFA in VPN/CLI RADIUS authentication and on the 
captive portal
*   Support for TOTP MFA in VPN/CLI RADIUS authentication and on the 
captive portal
*   Automation of upgrades for standalone installations (#6583)

Enhancements

*   MikroTik DHCP MAC authentication support
*   Allow to use the sAMAccountName from the searchattributes in MSCHAP 
machine authentication (#6586)
*   Improve the Data Access Layer to work in MariaDB's default sql_mode
*   New command pfcmd mariadb [mariadb options]
*   Deauth request can be made on the previous equipment the device was 
connected
*   Allow the bulk import of config items to be async
*   Remove unused/deprecated sources (AuthorizeNet, Instagram, Twitter, 
Pinterest, and Mirapay) (#6560)
*   Automation of supported equipment page on PacketFence webs

[PacketFence-users] ANN: PacketFence v11.1

2021-10-29 Thread Ludovic Marcotte via PacketFence-users 
The Inverse team is pleased to announce the immediate availability of 
PacketFence v11.1. This is a major release with new features, enhancements and 
bug fixes. This release is considered ready for production use and upgrading 
from previous versions is strongly advised.
What is PacketFence?
PacketFence is a fully supported, trusted, Free and Open Source Network Access 
Control (NAC) solution. Boasting an impressive feature set, PacketFence can be 
used to effectively secure small to very large heterogeneous networks.

Among the features provided by PacketFence, there are:
powerful BYOD (Bring Your Own Device) capabilities
multiple enforcement methods including Role-Based Access Control (RBAC) and 
hotspot-style
built-in network behaviour anomaly detection
state-of-the art devices identification with Fingerbank
compliance checks for endpoints present on your network
integration with various vulnerability scanners, intrusion detection solutions, 
security agents and firewalls
bandwidth accounting for all devices
A complete overview of the solution is available from the official website: 
https://packetfence.org/about.html
Changes Since Previous Release
New Features
Support for Akamai MFA in VPN/CLI RADIUS authentication and on the captive 
portal
Support for TOTP MFA in VPN/CLI RADIUS authentication and on the captive portal
Automation of upgrades for standalone installations (#6583)
Enhancements
MikroTik DHCP MAC authentication support
Allow to use the sAMAccountName from the searchattributes in MSCHAP machine 
authentication (#6586)
Improve the Data Access Layer to work in MariaDB's default sql_mode
New command pfcmd mariadb [mariadb options]
Deauth request can be made on the previous equipment the device was connected
Allow the bulk import of config items to be async
Remove unused/deprecated sources (AuthorizeNet, Instagram, Twitter, Pinterest, 
and Mirapay) (#6560)
Automation of supported equipment page on PacketFence website (#6611)
Use Venom 1.0.0 through Ansible to run integration tests (#6573)
Import script will migrate the networks configuration if the new IP is in the 
same subnet (#6636)
EAP-TLS integration tests using manual deployment and SCEP protocol (#6647)
Added a monit check to ensure winbindd is still connected (11.1 - AD failover 
doesn’t work #6655)
Improve ZEN builds (#6663)
Bug Fixes
Match the realm more strictly when its not a regex in EAP-TTLS PAP
Populate the LDAP config for enabled LDAP EAP-TTLS PAP realms
Only call oauth2 in authorize for the realms that have an Azure AD EAP-TTLS PAP 
configuration
Use source username in LDAP module for EAP-TTLS PAP instead of always using 
sAMAccoutName
Support LDAP certificate client auth for LDAP EAP-TTLS PAP authentication
Allow to use Google Workspace LDAP sources in EAP-TTLS PAP authentication
Add script for removing WMI scan (#6569)
Fix Let's Encrypt renewal process restarting services even if they are disabled 
(#6606)
Removes the deprecated NTLM background job fields and components (#6552)
Ignore 'Mark as sponsor' administration rules when finding the access level of 
a VPN/CLI user (#6349)
Reducing time balance only when registered
See https://github.com/inverse-inc/packetfence/compare/v11.0.0...v11.1.0 for 
the complete change log.

See the Upgrade guide for notes about upgrading: 
https://packetfence.org/doc/PacketFence_Upgrade_Guide.html
Getting PacketFence
PacketFence is free software and is distributed under the GNU GPL. As such, you 
are free to download and try it by either getting the new release or by getting 
the sources: https://packetfence.org/download.html

Documentation about the installation and configuration of PacketFence is also 
available: https://packetfence.org/support/index.html#/documentation
How Can I Help?
PacketFence is a collaborative effort in order to create the best Free and Open 
Source NAC solution. There are multiple ways you can contribute to the project:
Documentation reviews, enhancements and translations
Feature requests or by sharing your ideas
Participate in the discussion on mailing lists 
(https://packetfence.org/support/index.html#/community)
Patches for bugs or enhancements
Provide new translations of remediation pages
Getting Support
For any questions, do not hesitate to contact us by writing to 
supp...@inverse.ca

You can also fill our online form (https://inverse.ca/#contact) and a 
representative from Inverse will contact you.

Inverse offers professional services to organizations willing to secure their 
wired and wireless networks with the PacketFence solution.

___
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users