Re: [PacketFence-users] R: R: R: R: R: R: network-access-detection

2017-08-17 Thread Durand fabrice via PacketFence-users
Hello Alessandro, A) first try to replace the network detection ip to 192.95.20.194. Next if you use fqdn instead of an ip address then you have to keep in mind that even if the packetfence's dns server return a ttl of 15s the browser have his own dns cache (like 1 minutes). So if the

[PacketFence-users] R: R: R: R: R: R: network-access-detection

2017-08-17 Thread Alessandro Canella via PacketFence-users
first solved (thanks for DNS help…) A) I’ve discovered that network access gif after login is accessible ONLY via DNS call (DNS_SERVER_NAME.net/common/network-access-detection.gif works, SERVER_MANAGEMENT_IP/common/network-access-detection.gif didn't) seems an apache misconfig. I've

[PacketFence-users] R: R: R: R: R: R: network-access-detection

2017-08-17 Thread Alessandro Canella via PacketFence-users
resolv.conf is empty, I assume (ok that’s wrong, I’d understand…..) that NS are controlled by another .conf in PF setup… about NAT and route…. I’d have 10/15 networks on the other side… and seems all fine… I will check asap.. Da: Fabrice Durand via PacketFence-users