Hi Bill
I haven't installed pf10 yet. But I think the key item is the fact that the
registration vlan DNS is not resolving to the correct PF address. Do you
have any nic or vlan configured with that IP?
You mention replacing the fqdn for that of the registration vlan. Is that
provisioned on your
Diego,
Ran some packet captures on Monday and every time the end-system was looking
for the IP of the packetfence host – DNS lookup – it was returned as a
192.0.2.1. This is some sort of internal IP that PF is using for the portal,
as it is the default response no matter what is requested. I
