Re: [PacketFence-users] Cluster PF 8.0.1

2018-05-17 Thread Fabrice Durand via PacketFence-users 
No, if you do a cluster of 3 then all the vip are defined in 
cluster.conf and not in pf.conf, so if you still have some vip= 
parameters in pf.conf then remove them.


If you do a cluster of 2 (active/passive) then you have to deal with 
vip= in pf.conf.


Regards

Fabrice



Le 2018-05-17 à 10:00, Jeimerson C. Chaves via PacketFence-users a écrit :

So VIP address is only for the management interface correct? Do we
have to point to that VIP address in the other managements interface?
Something like this:

eth0 in pfence01:
IP: 10.160.26.28
VIP: 10.160.26.20

eth0 in pfence02:
IP: 10.160.26.29
VIP: 10.160.26.20

eth0 in pfence03:
IP: 10.160.26.30
VIP: 10.160.26.20

Kind Regards
Com os melhores cumprimentos.

Jeimerson Chaves

Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros
informáticos com ele transmitidos são confidenciais, podem conter
informação privilegiada e destinam-se ao conhecimento e uso exclusivo
da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos
mesmos ser alterado. Caso tenha recebido este e-mail indevidamente,
queira informar de imediato o remetente e proceder à destruição da
mensagem e de eventuais cópias.

Confidentiality Warning: This e-mail and any files transmitted with it
are confidential and may be privileged and are intended solely for the
use of the individual or entity to whom they are addressed. Their
contents may not be altered. lf you are not the intended recipient of
this communication please notify the sender and delete and destroy all
copies immediately.




2018-05-17 14:31 GMT+01:00 Fabrice Durand via PacketFence-users
:


Le 2018-05-17 à 09:09, Jeimerson C. Chaves via PacketFence-users a écrit :

Hello Fabrice,

In the how to, my interpretation is that we have to define VIP for
every single interface.

It's written nowhere in the documentation and this is probably why you can't
start mysql, so remove all the vip parameter you have in pf.conf and do a
"pfcmd configreload hard"
The cluster.conf looks good.

Regards
Fabrice




In order to create a new cluster, you need to configure
/usr/local/pf/conf/cluster.conf on the first server of your cluster.

You will need to configure it with your server hostname. To get it use
: hostname in a command line.

In the case of this example it will be pf1.example.com.

The CLUSTER section represents the virtual IP addresses of your
cluster that will be shared by your servers.

In this example, eth0 is the management interface, eth1.2 is the
registration interface and eth1.3 is the isolation interface.

On the first server, create a configuration similar to this :

[CLUSTER]
management_ip=192.168.1.10

[CLUSTER interface eth0]
ip=192.168.1.10

[CLUSTER interface eth1.2]
ip=192.168.2.10

[CLUSTER interface eth1.3]
ip=192.168.3.10

[pf1.example.com]
management_ip=192.168.1.5

[pf1.example.com interface eth0]
ip=192.168.1.5

[pf1.example.com interface eth1.2]
ip=192.168.2.5

[pf1.example.com interface eth1.3]
ip=192.168.3.5

[pf2.example.com]
management_ip=192.168.1.6

[pf2.example.com interface eth0]
ip=192.168.1.6

[pf2.example.com interface eth1.2]
ip=192.168.2.6

[pf2.example.com interface eth1.3]
ip=192.168.3.6

[pf3.example.com]
management_ip=192.168.1.7

[pf3.example.com interface eth0]
ip=192.168.1.7

[pf3.example.com interface eth1.2]
ip=192.168.2.7

[pf3.example.com interface eth1.3]
ip=192.168.3.7
Com os melhores cumprimentos.

Jeimerson Chaves

Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros
informáticos com ele transmitidos são confidenciais, podem conter
informação privilegiada e destinam-se ao conhecimento e uso exclusivo
da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos
mesmos ser alterado. Caso tenha recebido este e-mail indevidamente,
queira informar de imediato o remetente e proceder à destruição da
mensagem e de eventuais cópias.

Confidentiality Warning: This e-mail and any files transmitted with it
are confidential and may be privileged and are intended solely for the
use of the individual or entity to whom they are addressed. Their
contents may not be altered. lf you are not the intended recipient of
this communication please notify the sender and delete and destroy all
copies immediately.




2018-05-17 13:39 GMT+01:00 Fabrice Durand via PacketFence-users
:

Hello Jeimerson,

follow exactly what you have in
https://packetfence.org/doc/PacketFence_Clustering_Guide.html .

A quick look show me that you defined VIP on each interfaces, it's only
use
when you do a cluster of 2 with corosync and pacemaker.

So follow the documentation and it should be good.

Regards

Fabrice



Le 2018-05-17 à 06:08, Jeimerson C. Chaves via PacketFence-users a écrit
:

Hi, Fabrice,

Hello, I'm redoing the how to, for the fifteenth time,
As you can see in the screenscreens, you can see that Mysql runs in the
IP
VIP.
It only ran after I made the change in the configuration file.
I am using

Re: [PacketFence-users] Cluster PF 8.0.1

2018-05-17 Thread Jeimerson C. Chaves via PacketFence-users 
So VIP address is only for the management interface correct? Do we
have to point to that VIP address in the other managements interface?
Something like this:

eth0 in pfence01:
IP: 10.160.26.28
VIP: 10.160.26.20

eth0 in pfence02:
IP: 10.160.26.29
VIP: 10.160.26.20

eth0 in pfence03:
IP: 10.160.26.30
VIP: 10.160.26.20

Kind Regards
Com os melhores cumprimentos.

Jeimerson Chaves

Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros
informáticos com ele transmitidos são confidenciais, podem conter
informação privilegiada e destinam-se ao conhecimento e uso exclusivo
da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos
mesmos ser alterado. Caso tenha recebido este e-mail indevidamente,
queira informar de imediato o remetente e proceder à destruição da
mensagem e de eventuais cópias.

Confidentiality Warning: This e-mail and any files transmitted with it
are confidential and may be privileged and are intended solely for the
use of the individual or entity to whom they are addressed. Their
contents may not be altered. lf you are not the intended recipient of
this communication please notify the sender and delete and destroy all
copies immediately.




2018-05-17 14:31 GMT+01:00 Fabrice Durand via PacketFence-users
:
>
>
> Le 2018-05-17 à 09:09, Jeimerson C. Chaves via PacketFence-users a écrit :
>>
>> Hello Fabrice,
>>
>> In the how to, my interpretation is that we have to define VIP for
>> every single interface.
>
> It's written nowhere in the documentation and this is probably why you can't
> start mysql, so remove all the vip parameter you have in pf.conf and do a
> "pfcmd configreload hard"
> The cluster.conf looks good.
>
> Regards
> Fabrice
>
>
>>
>>
>> In order to create a new cluster, you need to configure
>> /usr/local/pf/conf/cluster.conf on the first server of your cluster.
>>
>> You will need to configure it with your server hostname. To get it use
>> : hostname in a command line.
>>
>> In the case of this example it will be pf1.example.com.
>>
>> The CLUSTER section represents the virtual IP addresses of your
>> cluster that will be shared by your servers.
>>
>> In this example, eth0 is the management interface, eth1.2 is the
>> registration interface and eth1.3 is the isolation interface.
>>
>> On the first server, create a configuration similar to this :
>>
>> [CLUSTER]
>> management_ip=192.168.1.10
>>
>> [CLUSTER interface eth0]
>> ip=192.168.1.10
>>
>> [CLUSTER interface eth1.2]
>> ip=192.168.2.10
>>
>> [CLUSTER interface eth1.3]
>> ip=192.168.3.10
>>
>> [pf1.example.com]
>> management_ip=192.168.1.5
>>
>> [pf1.example.com interface eth0]
>> ip=192.168.1.5
>>
>> [pf1.example.com interface eth1.2]
>> ip=192.168.2.5
>>
>> [pf1.example.com interface eth1.3]
>> ip=192.168.3.5
>>
>> [pf2.example.com]
>> management_ip=192.168.1.6
>>
>> [pf2.example.com interface eth0]
>> ip=192.168.1.6
>>
>> [pf2.example.com interface eth1.2]
>> ip=192.168.2.6
>>
>> [pf2.example.com interface eth1.3]
>> ip=192.168.3.6
>>
>> [pf3.example.com]
>> management_ip=192.168.1.7
>>
>> [pf3.example.com interface eth0]
>> ip=192.168.1.7
>>
>> [pf3.example.com interface eth1.2]
>> ip=192.168.2.7
>>
>> [pf3.example.com interface eth1.3]
>> ip=192.168.3.7
>> Com os melhores cumprimentos.
>>
>> Jeimerson Chaves
>>
>> Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros
>> informáticos com ele transmitidos são confidenciais, podem conter
>> informação privilegiada e destinam-se ao conhecimento e uso exclusivo
>> da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos
>> mesmos ser alterado. Caso tenha recebido este e-mail indevidamente,
>> queira informar de imediato o remetente e proceder à destruição da
>> mensagem e de eventuais cópias.
>>
>> Confidentiality Warning: This e-mail and any files transmitted with it
>> are confidential and may be privileged and are intended solely for the
>> use of the individual or entity to whom they are addressed. Their
>> contents may not be altered. lf you are not the intended recipient of
>> this communication please notify the sender and delete and destroy all
>> copies immediately.
>>
>>
>>
>>
>> 2018-05-17 13:39 GMT+01:00 Fabrice Durand via PacketFence-users
>> :
>>>
>>> Hello Jeimerson,
>>>
>>> follow exactly what you have in
>>> https://packetfence.org/doc/PacketFence_Clustering_Guide.html .
>>>
>>> A quick look show me that you defined VIP on each interfaces, it's only
>>> use
>>> when you do a cluster of 2 with corosync and pacemaker.
>>>
>>> So follow the documentation and it should be good.
>>>
>>> Regards
>>>
>>> Fabrice
>>>
>>>
>>>
>>> Le 2018-05-17 à 06:08, Jeimerson C. Chaves via PacketFence-users a écrit
>>> :
>>>
>>> Hi, Fabrice,
>>>
>>> Hello, I'm redoing the how to, for the fifteenth time,
>>> As you can see in the screenscreens, you can see that Mysql runs in the
>>> IP
>>> VIP.
>>> It only ran after I made the change in the configuration

Re: [PacketFence-users] Cluster PF 8.0.1

2018-05-17 Thread Fabrice Durand via PacketFence-users 



Le 2018-05-17 à 09:09, Jeimerson C. Chaves via PacketFence-users a écrit :

Hello Fabrice,

In the how to, my interpretation is that we have to define VIP for
every single interface.
It's written nowhere in the documentation and this is probably why you 
can't start mysql, so remove all the vip parameter you have in pf.conf 
and do a "pfcmd configreload hard"

The cluster.conf looks good.

Regards
Fabrice




In order to create a new cluster, you need to configure
/usr/local/pf/conf/cluster.conf on the first server of your cluster.

You will need to configure it with your server hostname. To get it use
: hostname in a command line.

In the case of this example it will be pf1.example.com.

The CLUSTER section represents the virtual IP addresses of your
cluster that will be shared by your servers.

In this example, eth0 is the management interface, eth1.2 is the
registration interface and eth1.3 is the isolation interface.

On the first server, create a configuration similar to this :

[CLUSTER]
management_ip=192.168.1.10

[CLUSTER interface eth0]
ip=192.168.1.10

[CLUSTER interface eth1.2]
ip=192.168.2.10

[CLUSTER interface eth1.3]
ip=192.168.3.10

[pf1.example.com]
management_ip=192.168.1.5

[pf1.example.com interface eth0]
ip=192.168.1.5

[pf1.example.com interface eth1.2]
ip=192.168.2.5

[pf1.example.com interface eth1.3]
ip=192.168.3.5

[pf2.example.com]
management_ip=192.168.1.6

[pf2.example.com interface eth0]
ip=192.168.1.6

[pf2.example.com interface eth1.2]
ip=192.168.2.6

[pf2.example.com interface eth1.3]
ip=192.168.3.6

[pf3.example.com]
management_ip=192.168.1.7

[pf3.example.com interface eth0]
ip=192.168.1.7

[pf3.example.com interface eth1.2]
ip=192.168.2.7

[pf3.example.com interface eth1.3]
ip=192.168.3.7
Com os melhores cumprimentos.

Jeimerson Chaves

Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros
informáticos com ele transmitidos são confidenciais, podem conter
informação privilegiada e destinam-se ao conhecimento e uso exclusivo
da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos
mesmos ser alterado. Caso tenha recebido este e-mail indevidamente,
queira informar de imediato o remetente e proceder à destruição da
mensagem e de eventuais cópias.

Confidentiality Warning: This e-mail and any files transmitted with it
are confidential and may be privileged and are intended solely for the
use of the individual or entity to whom they are addressed. Their
contents may not be altered. lf you are not the intended recipient of
this communication please notify the sender and delete and destroy all
copies immediately.




2018-05-17 13:39 GMT+01:00 Fabrice Durand via PacketFence-users
:

Hello Jeimerson,

follow exactly what you have in
https://packetfence.org/doc/PacketFence_Clustering_Guide.html .

A quick look show me that you defined VIP on each interfaces, it's only use
when you do a cluster of 2 with corosync and pacemaker.

So follow the documentation and it should be good.

Regards

Fabrice



Le 2018-05-17 à 06:08, Jeimerson C. Chaves via PacketFence-users a écrit :

Hi, Fabrice,

Hello, I'm redoing the how to, for the fifteenth time,
As you can see in the screenscreens, you can see that Mysql runs in the IP
VIP.
It only ran after I made the change in the configuration file.
I am using VMware ESXi for the lab.
The in port services 1443 and 9090 do not run in the IP of the
management, only ip VIP.

Thank you in advance.


pf.conf

# Hostname of PacketFence system.  This is concatenated with the
domain in Apache rewriting rules and therefore must be resolvable by
clients.
hostname=pfence001
#
# general.dhcpservers
#
# Comma-delimited list of DHCP servers.  Passthroughs are created to
allow DHCP transactions from even "trapped" nodes.
dhcpservers=127.0.0.1,10.161.16.21

[alerting]
#
# alerting.emailaddr
#
# Email address to which notifications of rogue DHCP servers,
violations with an action of "email", or any other
# PacketFence-related message goes to.
emailaddr=pfence@localhost

[database]
#
# database.pass
#
# Password for the mysql database used by PacketFence. Changing this
parameter after the initial configuration will *not* change it in the
database it self, only in the configuration.
pass=zaq12wsx

[advanced]
#
# advanced.hash_passwords
#
# The algorithm to use to hash the passwords in the local database.
hash_passwords=ntlm

[interface eth0]
ip=10.161.16.28
type=management,portal,radius,high-availability
vip=10.60.60.20
mask=255.255.255.0

[interface eth3]
enforcement=vlan
ip=10.60.60.28
type=internal
vip=10.60.60.20
mask=255.255.255.0

[interface eth4]
enforcement=vlan
ip=10.70.70.28
type=internal
vip=10.70.70.20
mask=255.255.255.0

###

log mariadb_error


May 17 09:51:30 pfence01 mysqld:
May 17 09:51:33 pfence01 mysqld_safe: mysqld from pid file
/var/lib/mysql/pfence01.pid ended
May 17 09:51:34 pfence01 mysqld_safe: Starting mysqld daemon with
databases from /var/lib/mysql
May 17

Re: [PacketFence-users] Cluster PF 8.0.1

2018-05-17 Thread Jeimerson C. Chaves via PacketFence-users 
Hello Fabrice,

In the how to, my interpretation is that we have to define VIP for
every single interface.


In order to create a new cluster, you need to configure
/usr/local/pf/conf/cluster.conf on the first server of your cluster.

You will need to configure it with your server hostname. To get it use
: hostname in a command line.

In the case of this example it will be pf1.example.com.

The CLUSTER section represents the virtual IP addresses of your
cluster that will be shared by your servers.

In this example, eth0 is the management interface, eth1.2 is the
registration interface and eth1.3 is the isolation interface.

On the first server, create a configuration similar to this :

[CLUSTER]
management_ip=192.168.1.10

[CLUSTER interface eth0]
ip=192.168.1.10

[CLUSTER interface eth1.2]
ip=192.168.2.10

[CLUSTER interface eth1.3]
ip=192.168.3.10

[pf1.example.com]
management_ip=192.168.1.5

[pf1.example.com interface eth0]
ip=192.168.1.5

[pf1.example.com interface eth1.2]
ip=192.168.2.5

[pf1.example.com interface eth1.3]
ip=192.168.3.5

[pf2.example.com]
management_ip=192.168.1.6

[pf2.example.com interface eth0]
ip=192.168.1.6

[pf2.example.com interface eth1.2]
ip=192.168.2.6

[pf2.example.com interface eth1.3]
ip=192.168.3.6

[pf3.example.com]
management_ip=192.168.1.7

[pf3.example.com interface eth0]
ip=192.168.1.7

[pf3.example.com interface eth1.2]
ip=192.168.2.7

[pf3.example.com interface eth1.3]
ip=192.168.3.7
Com os melhores cumprimentos.

Jeimerson Chaves

Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros
informáticos com ele transmitidos são confidenciais, podem conter
informação privilegiada e destinam-se ao conhecimento e uso exclusivo
da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos
mesmos ser alterado. Caso tenha recebido este e-mail indevidamente,
queira informar de imediato o remetente e proceder à destruição da
mensagem e de eventuais cópias.

Confidentiality Warning: This e-mail and any files transmitted with it
are confidential and may be privileged and are intended solely for the
use of the individual or entity to whom they are addressed. Their
contents may not be altered. lf you are not the intended recipient of
this communication please notify the sender and delete and destroy all
copies immediately.




2018-05-17 13:39 GMT+01:00 Fabrice Durand via PacketFence-users
:
> Hello Jeimerson,
>
> follow exactly what you have in
> https://packetfence.org/doc/PacketFence_Clustering_Guide.html .
>
> A quick look show me that you defined VIP on each interfaces, it's only use
> when you do a cluster of 2 with corosync and pacemaker.
>
> So follow the documentation and it should be good.
>
> Regards
>
> Fabrice
>
>
>
> Le 2018-05-17 à 06:08, Jeimerson C. Chaves via PacketFence-users a écrit :
>
> Hi, Fabrice,
>
> Hello, I'm redoing the how to, for the fifteenth time,
> As you can see in the screenscreens, you can see that Mysql runs in the IP
> VIP.
> It only ran after I made the change in the configuration file.
> I am using VMware ESXi for the lab.
> The in port services 1443 and 9090 do not run in the IP of the
> management, only ip VIP.
>
> Thank you in advance.
>
>
> pf.conf
>
> # Hostname of PacketFence system.  This is concatenated with the
> domain in Apache rewriting rules and therefore must be resolvable by
> clients.
> hostname=pfence001
> #
> # general.dhcpservers
> #
> # Comma-delimited list of DHCP servers.  Passthroughs are created to
> allow DHCP transactions from even "trapped" nodes.
> dhcpservers=127.0.0.1,10.161.16.21
>
> [alerting]
> #
> # alerting.emailaddr
> #
> # Email address to which notifications of rogue DHCP servers,
> violations with an action of "email", or any other
> # PacketFence-related message goes to.
> emailaddr=pfence@localhost
>
> [database]
> #
> # database.pass
> #
> # Password for the mysql database used by PacketFence. Changing this
> parameter after the initial configuration will *not* change it in the
> database it self, only in the configuration.
> pass=zaq12wsx
>
> [advanced]
> #
> # advanced.hash_passwords
> #
> # The algorithm to use to hash the passwords in the local database.
> hash_passwords=ntlm
>
> [interface eth0]
> ip=10.161.16.28
> type=management,portal,radius,high-availability
> vip=10.60.60.20
> mask=255.255.255.0
>
> [interface eth3]
> enforcement=vlan
> ip=10.60.60.28
> type=internal
> vip=10.60.60.20
> mask=255.255.255.0
>
> [interface eth4]
> enforcement=vlan
> ip=10.70.70.28
> type=internal
> vip=10.70.70.20
> mask=255.255.255.0
>
> ###
>
> log mariadb_error
>
>
> May 17 09:51:30 pfence01 mysqld:
> May 17 09:51:33 pfence01 mysqld_safe: mysqld from pid file
> /var/lib/mysql/pfence01.pid ended
> May 17 09:51:34 pfence01 mysqld_safe: Starting mysqld daemon with
> databases from /var/lib/mysql
> May 17 09:51:34 pfence01 mysqld: 2018-05-17  9:51:34 14000406528
> [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a
>

[PacketFence-users] Captive Portal Self-Deregistration

2018-05-17 Thread Trinklein, Jason R via PacketFence-users 
Hi All,

When a client device passes our captive portal, is there a URL we can use for 
the client to deregister the device earlier than the deregistration date/time? 
This is necessary for loaned devices on our campus to prevent prior user’s 
registrations from being used by new users.

Thanks,
--
Jason Trinklein
Wireless Engineering Manager
College of Charleston
81 St. Philip Street | Office 311D | Charleston, SC 29403
trinkle...@cofc.edu | (843) 300–8009
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Re: [PacketFence-users] Network Devices lost

2018-05-17 Thread Fabrice Durand via PacketFence-users 

It's probably a javascript issue.

Check the javascript console or try to clear the cache of your browser.

Regards

Fabrice



Le 2018-05-17 à 07:20, Jeimerson C. Chaves via PacketFence-users a écrit :

Hello,

Again, I am disturbing, but when configuring the registration
interface, it disappears, as it can be verified.
Thank you.


Com os melhores cumprimentos.

Jeimerson Chaves

Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros
informáticos com ele transmitidos são confidenciais, podem conter
informação privilegiada e destinam-se ao conhecimento e uso exclusivo
da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos
mesmos ser alterado. Caso tenha recebido este e-mail indevidamente,
queira informar de imediato o remetente e proceder à destruição da
mensagem e de eventuais cópias.

Confidentiality Warning: This e-mail and any files transmitted with it
are confidential and may be privileged and are intended solely for the
use of the individual or entity to whom they are addressed. Their
contents may not be altered. lf you are not the intended recipient of
this communication please notify the sender and delete and destroy all
copies immediately.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


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


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Re: [PacketFence-users] Network Devices lost

2018-05-17 Thread Jeimerson C. Chaves via PacketFence-users 
Have in pf.conf

End lost in eth4.
Com os melhores cumprimentos.

Jeimerson Chaves

Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros
informáticos com ele transmitidos são confidenciais, podem conter
informação privilegiada e destinam-se ao conhecimento e uso exclusivo
da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos
mesmos ser alterado. Caso tenha recebido este e-mail indevidamente,
queira informar de imediato o remetente e proceder à destruição da
mensagem e de eventuais cópias.

Confidentiality Warning: This e-mail and any files transmitted with it
are confidential and may be privileged and are intended solely for the
use of the individual or entity to whom they are addressed. Their
contents may not be altered. lf you are not the intended recipient of
this communication please notify the sender and delete and destroy all
copies immediately.




2018-05-17 12:20 GMT+01:00 Jeimerson C. Chaves :
> Hello,
>
> Again, I am disturbing, but when configuring the registration
> interface, it disappears, as it can be verified.
> Thank you.
>
>
> Com os melhores cumprimentos.
>
> Jeimerson Chaves
>
> Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros
> informáticos com ele transmitidos são confidenciais, podem conter
> informação privilegiada e destinam-se ao conhecimento e uso exclusivo
> da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos
> mesmos ser alterado. Caso tenha recebido este e-mail indevidamente,
> queira informar de imediato o remetente e proceder à destruição da
> mensagem e de eventuais cópias.
>
> Confidentiality Warning: This e-mail and any files transmitted with it
> are confidential and may be privileged and are intended solely for the
> use of the individual or entity to whom they are addressed. Their
> contents may not be altered. lf you are not the intended recipient of
> this communication please notify the sender and delete and destroy all
> copies immediately.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users