Developers guide

Chapter 7

Optional components 62

[default]

billing_engine = enabled

...

Billing engine parameters are specified in conf/pf.conf or from Configuration � Billing:

[billing]

gateway = authorize_net

authorizenet_posturl = The payment gateway processing URL

authorizenet_login = The merchant's unique API Login ID

authorizenet_trankey = The merchant's unique Transaction Key

It is also possible to configure multiple network access with different prices. For example, you may want

to provide basic Internet access with a decent speed at a specific price and another package with high

speed connection at another price.

To do so, some customizations is needed to the billing module. You’ll need to redefined the

getAvailableTiers method in the lib/pf/billing/custom.pm file. An example is already in place

in the file.

Caution

The use of different billing tiers requires different roles in PacketFence. Make sure to

create these roles first otherwise you will run into problems.

Portal Profiles

In some cases, you may want to present a different captive portal (see below for the available

customizations) according to the SSID, the VLAN, or the switch IP the client connects to. To do so,

PacketFence has the concept of portal profiles which gives you this possibility.

When configured, portal profiles will override default values for which it is configured. When no values are

configured in the profile, PacketFence will take its default ones (according to the "default" portal profile).

Here are the different configuration parameters that can be set for each portal profiles. The only mandatory

parameter is "filter", otherwise, PacketFence won’t be able to correctly apply the portal profile. The

parameters must be set in conf/profiles.conf:

[profilename1]

description = the description of your portal profile

filter = the name of the SSID for which you'd like to apply the profile, or the

VLAN number

billing_engine = either enabled or disabled

sources = comma-separated list of authentications sources (IDs) to use

Portal profiles should be managed from PacketFence’s Web administrative GUI - from the Configuration �

Portal Profiles and Pages section. Adding a portal profile from that interface will correctly copy templates

over - which can then be modified as you wish.