Red Hat NETWORK 4.1.0 - Guide de l'utilisateur télécharger pdf (Page 65)

Chapter 7

Optional components 61

Alternatively, you can configure these parameters from the PacketFence Web administrative GUI, in the

Configuration � Provisioning section.

Profile generation

Upon registration, instead of showing the default release page, the user will be showing another version

of the page saying that the wireless profile has been generated with a clickable link on it. To install

the profile, the user simply need to click on that link, and follow the instructions on their device. It is

that simple.

SNMP Traps Limit

PacketFence mainly rely on SNMP traps to communicate with equipment. Due to the fact that traps coming

in from approved (configured) devices are all processed by the daemon, it is possible for someone who

want to generate a certain load on the PacketFence server to force the generation of non-legitimate SNMP

traps or a switch can randomly generate a high quantity of traps sent to PacketFence for an unknown

reason.

Because of that, it is possible to limit the number of SNMP traps coming in from a single switch port and

take action if that limit is reached. For example, if over 100 traps are received by PacketFence from the

same switch port in a minute, the switch port will be shut and a notification email will be sent.

Here’s the default config for the SNMP traps limit feature. As you can see, by default, PacketFence will

log the abnormal activity after 100 traps from the same switch port in a minute. These configurations

are in the conf/pf.conf file:

[vlan]

trap_limit = enabled

trap_limit_threshold = 100

trap_limit_action =

Alternatively, you can configure these parameters from the PacketFence Web administrative GUI, in the

Configuration � SNMP section.

Billing Engine

PacketFence integrates the ability to use a payment gateway to bill users to gain access to the network.

When configured, the user who wants to access the network / Internet is prompted by a page asking for

it’s personnal information as well as it’s credit card information.

At this moment there is only one payment gateway built into PacketFence: Authorize.net.

The configuration to use the feature is fairly simple. The general configuration to enable / disable the

billing engine can be done through the Web administration GUI (Configuration � Portal Profiles and

Pages) or from the conf/profiles.conf file:

1 2 ... 60 61 62 63 64 65 66 67 68 69 70 ... 100 101

Pas de commentaire

Red Hat NETWORK 4.1.0 - Guide de l'utilisateur Page 65