Il 05/05/2018 04:25, Durand fabrice via PacketFence-users ha scritto:
So i did the change and the new binary will be available tomorrow there:
http://inverse.ca/downloads/PacketFence/CentOS7/binaries/maintenance/8.0/
Regards
Fabrice
Thanks Fabrice, i'll do some tests ASAP. I need to
So i did the change and the new binary will be available tomorrow there:
http://inverse.ca/downloads/PacketFence/CentOS7/binaries/maintenance/8.0/
Regards
Fabrice
Le 2018-05-04 à 08:40, Fabrice Durand via PacketFence-users a écrit :
Ok i probably know what happen.
Let me do some test on
Ok i probably know what happen.
Let me do some test on my side and i will provide a patch.
Regards
Fabrice
Le 2018-05-03 à 09:27, Cristian Mammoli via PacketFence-users a écrit :
It seems that trying to resolve a domain returns the registration vlan
IP (192.168.112.254) while trying to
It seems that trying to resolve a domain returns the registration vlan
IP (192.168.112.254) while trying to resolve the portal FQDN returns the
portal interface IP (*192.168.114.254*)
Probably the 2nd query is forwarded upstream for some reason
C:\Windows\system32>nslookup www.pippo.com
Weird, it's suppose to return the portal ip.
Can you do this on a laptop:
nslookup nac.apra.it
and on the same time on the packetfence server : journalctl -f | grep dns
And give me the result.
Regards
Fabrice
Le 2018-05-03 à 03:44, Cristian Mammoli via PacketFence-users a écrit :
Indeed
Hello Cristian,
you don't have to allow the portal ip for the registration and isolation
vlan.
Can you share your pf.conf and networks.conf and
/usr/local/pf/var/conf/pfdns.conf
Regards
Fabrice
Le 2018-05-02 à 12:25, Cristian Mammoli via PacketFence-users a écrit :
Ok, then I have a
Ok, then I have a problem:
I created a dns record for nac.apra.it on my corporate dns server that
points to the portal interface (nac.apra.it is
general.hostname+general.domain in pf.conf)
But even from an unregistered device pfdns resolves with this ip address
instead of replying with its
Hello Cristian,
pfdns is suppose to resolv the portal fqdn if the device is unreg or if
there is a violation.
Also if there is a passthrough that match the portal fqdn name then it
will forward the request to another server.
Portal interface is just an interface with the portal on it, it
Hi, isn't pfdns supposed to resolve the portal FQDN from isolation and
registration vlan? I'm using 8.0
ATM for me isn't working:
My pf.conf is:
[general]
#
# general.domain
#
# Domain name of PacketFence system.
domain=apra.it
#
# general.hostname
#
# Hostname of PacketFence system. This is
