Hello John, I will be honest there, using the mailing to achieve that is a bit far fetch because it requires a lot of configuration here and there. Maybe getting a small time bank from Akamai would be better.
That being said, you could use PacketFence to authenticate user on the network and once they did not pay the bill you unregister them that show the captive portal to register and pay the bill. This means that the whole authentication will be managed by PacketFence. Either the Wireless SSID or the switch ports. You could also leverage an API call to unregister them from a 3rd party server like the bill system. Thanks, Ludovic Zammit Product Support Engineer Principal 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 Nov 4, 2021, at 11:46 AM, John Gammon via PacketFence-users > <packetfence-users@lists.sourceforge.net> wrote: > > All, > > I am a newbie attempting config PF 11.0.0 for our purposes. > > Our design is as follows: > - router handles the VLANs (agnostic to server or end points) > - domain is pf.forkeddeerconnect.com > - subnet range for pfdhcp is 147.159.8.0/22 > - entry into the VLAN determined by not paying bill (package management puts > user into server) > - all DNS queries need to redirect to internal httpd index.xhtml webpage for > single direction: PAY YOUR BILL! > * Bill portal address is 208.72.73.60. > * This addr needs to be only address to allow out of this "isolation > environment." > > I have the PF server up and functional. Reached some limitations in getting > this moving forward. I have one device [linux laptop] connected directly to > the server for testing. I have installed isc-dns-bind9 and isc-dhcp-server > for address pools and resolution. But this may be overkill. I am unsure at > this point. > > I do not think authentication of anyone/device is necessary. If a user ends > up in this environment, they are supposed to pay their bill to get out. I do > not believe I need any authentication of hardware, but may be incorrect in my > view on this point. This is a designed isolation environment established to > redirect all dns requests to the internal webserver and singular index.xhtml > page...and allow them to their manage account portal. > > Any help is welcome. > > R, > > John > Network Engineer, FDC/FDEC > john.gam...@forkeddeer.com > > John Gammon > > Network Engineer > > Office 731-903-4282 > > john.gam...@forkeddeer.com<mailto:%20john.gam...@forkeddeer.com> > > [fdec logo] > > 1135 North Church Street > > PO Box 67 > > Halls, TN 38040 > > https://urldefense.com/v3/__http://www.forkeddeer.com__;!!GjvTz_vk!Cnyx3QHnuE7zdxVoHtkPd2ukjVdh3tPmS2JEXIxYG_OwrzxMd6JxV9pL6P09lk9o$ > > > > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/packetfence-users__;!!GjvTz_vk!Cnyx3QHnuE7zdxVoHtkPd2ukjVdh3tPmS2JEXIxYG_OwrzxMd6JxV9pL6LJnQb59$ >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
