In fact it doesn't work anymore: https://github.com/inverse-inc/packetfence/issues/8170
The dirty fix is to edit that file and do the manual change (/usr/local/pf/sbin/pfacct-docker-wrapper) Le jeu. 13 juin 2024 à 12:16, Zammit, Ludovic via PacketFence-users < packetfence-users@lists.sourceforge.net> a écrit : > Hello Nate, > > Tag the interface as radius in PF network, pfacct should listen on it. > > Thanks, > > *Ludovic Zammit* > *Product Support Engineer Principal Lead* > *Cell:* +1.613.670.8432 > Akamai Technologies - Inverse > 145 Broadway > Cambridge, MA 02142 > Connect with Us: <https://community.akamai.com> <http://blogs.akamai.com> > <https://twitter.com/akamai> <http://www.facebook.com/AkamaiTechnologies> > <http://www.linkedin.com/company/akamai-technologies> > <http://www.youtube.com/user/akamaitechnologies?feature=results_main> > > On Jun 12, 2024, at 8:56 AM, Nate Tremmel via PacketFence-users < > packetfence-users@lists.sourceforge.net> wrote: > > How can I change pfacct to bind to a different interface ip or to 0.0.0.0? > It’s only on my management interface and my radius stuff needs to be on a > different interface due to routing. > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > > https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/packetfence-users__;!!GjvTz_vk!VbVE8b_netpKzs-GAvOltuO3FHUYyqMZHN6x5FHOUEODhqcrqTFlqrhtC1ts2dYLRdIV3ElLvOFGSNFtxmmuHe-vZuC0FL4sqC-Njg$ > > > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/packetfence-users >
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
