This doesn’t sound like the issue I have, seeing as the preregistration doesn’t
work outside of the registration network (NAT to Public IP). I sign in with
username and password and then the portal times out on the public IP.
> On May 13, 2024, at 10:07 AM, Diego Garcia del Rio wrote:
>
>
so.. after troubleshooting a bit more.. somehow pfdns is not
responding the the 66.x ip for the fqdn of the portal. If you ask
pfdns for google.com or any other (while captive) it will reply with
the 66.x ip .. but for the fqdn of the portal itself, it fails.
see here for more details
can you check which ip is being returned once you're outside the
registration network? (Im asuming you're using dns / fqdn to access
the portal after login)
from what i understand you're using inline enforcement, is that correct?
On Mon, May 13, 2024 at 12:36 PM Nate Tremmel wrote:
>
> This
I used the OVA and it seems to work. I might have run apt upgrade before and it
stopped working then but since it’s working I’m not going to make any changes.
> On May 7, 2024, at 2:10 PM, Diego Garcia del Rio wrote:
>
> I was having similar issues on a fresh install of packetfence 13.1 on
>
Specifically seems to be tied to trying to set preregistration using the
default connection profile.
> On May 8, 2024, at 10:33 AM, Nate Tremmel wrote:
>
> I used the OVA and it seems to work. I might have run apt upgrade before and
> it stopped working then but since it’s working I’m not
I was having similar issues on a fresh install of packetfence 13.1 on
rocky linux using the RPMs.
I had trouble creating the isolation and registration sub-interfaces
(vlans), with the config not sticking on the configurator.. as such,
the haproxy-portal config was not having the correct
I’m running Packetfence 13.1 from ISO and have a registration VLAN. I am using
Merakis APs with radius role by VLAN. My test computer joins the network, get
a registration VLAN IP from the packet fence server, and it tries to open the
fqdn of the packetfence server and get a connection timed
