#packetfence
Live, measured metrics for the hashtag #packetfence from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #packetfence
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 04:58 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 04:58 UTCNo related tags with measured usage found for #packetfence.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 04:58 UTCEverything below is measured over the latest 10 public posts (spanning ~13737 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0.3
Top of the latest posts
Having a history with #packetfence as our radius server and am currently doing a #proofofconcept with the help of of #aruba with their #clearpass product, just quietly from my initial impressions... packetfence seems easier to configure and
Yes! #OpenWRT + #Packetfence: On an unencrypted registration SSID authorized a client through a portal page. Then showed the client via dpsk (dynamic pre-shared key) provisioner login data for the encrypted SSID to connect to a network with
Setting up a new #packetfence I tried to setup a portal for a registration vlan and failed miserably. The portal didn't show. The solution turned out to be quiet simple: a dns misconfiguration that seems to be part of the default configurat
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/packetfence