Management vlan is use for management (admin gui, radius server), registration is use to register (captive portal) and isolation is use to isolate (same config than a reg vlan). After that all the vlan you will define in switch role config will be production vlan (Your own dhcp, dns,gateway).

So in the switch configure the management interface as the radius server, set the role registration to the vlan id you define for registration, set the isolation role to the vlan you define for isolation and set the vlan 1 as the default vlan.

So when you will plug a device on a switch port , the switch will send a radius request to packetfence and is the device is unreg it will return the reg vlan id, you will hit the portal to register and packetfence will deauth your device on the switch port and the switch will send again a radius request then now packetfence will return the vlan 1. It's the simpliest way to explain how it works. You can see in the doc http://www.packetfence.org/downloads/PacketFence/doc/PacketFence_Administration_Guide-5.6.0.pdf and example for the wifi on the page 16 but it's exactly the same logic for the wire.

Regards
Fabrice


Le 2016-01-13 19:12, TOURE Amidou Florian a écrit :
Hello,I want to understand something in the configuration of PacketFence.I have install PacketFence in wmare workstation and it runs perfectly(i have not done any configuration for the moment).I have only configure my vlans.Is my managment vlan the vlan used for the BYOD equipments? If i want to configure a cisco 2960 to work with packetfence how much ethernet interfaces must i create in Vmware workstation?
Is someone can help me please?
Thank you ,this is my pf.conf file
[general]
#
# general.domain
#
# Domain name of PacketFence system.
domain=packetfene.org

[database]
#
# database.pass
#
# Password for the mysql database used by PacketFence.
pass=thegame
#
# database.user
#
# Username of the account with access to the mysql database used by PacketFence.
user=toure

[interface eth0.10]
ip=192.168.1.1
type=management
mask=255.255.255.240

[interface eth0.20]
enforcement=vlan
ip=192.168.1.17
type=internal
mask=255.255.255.240

[interface eth0.40]
enforcement=vlan
ip=192.168.10.1
type=internal
mask=255.255.255.240






------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140


_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to