im Guessing it might be related to the rfc7710bis / rfc8910 portal support
this means that via dhcp, the client is provided with an URL they can use
to check the status of the device in the portal (whether they are still
jailed or no)
normally this information is served on the same interface as
Good afternoon,
We are having the same problem, in the new version people have captured
random macs, and they redirect to a page with information on how to disable
random macs. Would that really be the best way to solve it? I don't know, I
just know that it generates complaints, tickets in our
Zammit,
No proxy. The management VLAN operates the portal listener behind an
OpenWRT firewall, which forwards 80/443 to Packetfence portal. iPerf
shows no bandwidth issues whatsoever, in our lab, and I we have never seen
any other connection issues, during apt upgrades, inbound portal
Daniel,
The random MAC would seem like an obvious culprit, but it is not.
On an iPhone, if you click on the little "i" for information next to each
connection, you see that the OS uses the same [random] mac per SSID, so it
will never change for a given WiFi network after is has connected. It
Hi Packetfence,
We have been struggling with some newer model mobile devices with our WiFi
captive portal implementation using Packetfence, and have not seen any
change in the behavior on 11.0 thru 12.1 with our current connection
profile.
We do not use an inline configuration, and now we are
Hi all,
I'm testing my PF server, i have declared the routed networks where is placed
my cisco enviroment, i have radius comunication from the cisco with the PF
server, but from the PF server i can't reach the routed subnet of the swithces.
I have the follogin interfaces:
auto lo
iface lo
Hi Mark,
On 10/1/23 00:56, Mark Rupright via PacketFence-users wrote:
I am a new Packetfence user and am currently in the test/design phase of
our deployment. I would like to know how I can configure PF to modify a
username on an incoming authentication request and change it to include
the
Hi Peter,
we've had this issue too, we've ended up disabling the "Use Connector" radio
button on the corresponding switch/switch group. This does seem to work around
the issue, while snmp connection still works fine.
Mit freundlichen Grüßen
i.A. Heiko Matthies
IT
