On 19-6-2017 22:17, lists via PacketFence-users wrote:
Hi,
I just tried upgrading our production network from 5.6 to 7.1, and even
though things seemed to have worked out, after a while we discovered
that some nodes were 'unregistered' after the upgrade. (they were
registrered before the upgrade, on 5.6.1)
Well, it seems that the complaining user was already unregistered on the
5.6 install. She claims things worked before the upgrade to 7.1, but I
don't know.
Seems not related to the pf upgrade, anyway.
One question remains: why (being an unreg device on the Inline Layer 2
network) did she not get the captive portal, but firefox timeout error
instead?
Do I perhaps need an additional listening daemon "portal" on that
network? (we don't have that in our packetfence 5.6 config)
MJ
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
