In reply to my own request, I have read the source code of the project and
discovered the valid options for interfaces in cluster.conf
The valid types are: internal, radius, portal, high-availability
Each type has different valid enforcement parameters:
internal: vlan, dns, inlinel2
radius: no
On 18-9-2017 12:46, lists via PacketFence-users wrote:
Hi,
No response... :-(
Does that mean that the tasks
- person_cleanup
and
- node_cleanup
are working for everybody here? On 7.1?
Anyone?
--
Check out the
Well, here we created our own cleanup tasks, using the database-cleaner.pl perl
script in /usr/local/pf/tools
- Mail original -
> De: "lists via PacketFence-users"
> À: packetfence-users@lists.sourceforge.net
> Cc: "lists"
Dear Sir/Madam,
The following log is the result of: tail -f
/usr/local/pf/logs/packetfence.log
Packetfence error log:
Sep 11 06:45:28 localhost pfqueue: pfqueue(6484) WARN: [mac:14:18:77:ce:0d:f2]
Unable to perform a Fingerbank lookup for device with MAC address
'14:18:77:ce:0d:f2'
Hi Frederic,
On 19-9-2017 10:39, Frederic Hermann via PacketFence-users wrote:
Well, here we created our own cleanup tasks, using the database-cleaner.pl perl
script in /usr/local/pf/tools
Did you also find the 'regular' packetfence GUI person_cleanup &
node_cleanup didn't work..? Or simply
> Did you also find the 'regular' packetfence GUI person_cleanup &
> node_cleanup didn't work..? Or simply never tried those regular gui
> cleanup tools?
Actually we're still using PF 6.5, and our migration to 7.x is due for next
spring, so we didn't had a chance to try those new personnal &
Hi,
we use PF 7.2 and have no problems with Node or User cleanup.
Maybe you should have a look at your logs (maybe increase your log level)
2017-09-19 15:08 GMT+02:00 Frederic Hermann via PacketFence-users <
packetfence-users@lists.sourceforge.net>:
>
> > Did you also find the 'regular'
Yes, I understand about the probes but this phone is randomizing its global MAC
address and is appearing on the PF server
with multiple MAC addresses each and every day.
At the last count some 27 unique MAC addresses all with the same prefix but
different host parts, here is a snapshot of a few
MAC randomization (At least the way Ive seen it work) only randomizes the
MAC when the device is passively probing for networks. It uses the fixed
MAC when it actually connects.
OR.. It uses a random MAC for a specific SSID and doesn't change it while
connected to that SSID.
If its randomizing
Agree with Tim... Unless she's telling the phone to "forget" the network
each and every day...
On Tue, Sep 19, 2017 at 11:04 AM, Tim DeNike via PacketFence-users <
packetfence-users@lists.sourceforge.net> wrote:
> MAC randomization (At least the way Ive seen it work) only randomizes the
> MAC
Hi folks,
We have a new student who cannot seem to get onto our PF controlled wifi since
her mobile phone
keeps randomising its MAC address. It appears this feature is hard coded into
the phones OS and
cannot be disabled. The only way we can see to fix this is to register every
one of the
Got it figured out, just had to do a few datadumpers and dig a bit to find
where to get at the stripped_user_name inside the firewallsso.pm. Here are
my notes in case anyone else needs to do this in pf7+:
sso modules have been rebuilt under golang and require compilation if you
customize them.
12 matches
Mail list logo