0001005: 802.1x and unauthenticated VLAN - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001005

PacketFence

captive portal

public

2010-06-07 17:58

2012-10-19 14:51

Reporter

obilodeau

Assigned To

Priority

normal

Severity

feature

Reproducibility

N/A

Status

resolved

Resolution

fixed

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0001005: 802.1x and unauthenticated VLAN

Description

This auth combinaison is a way to handle guests without a full-blown NAC like PacketFence. If the client is unable to provide proper credentials, then a specific VLAN is used as a last mean to give access. It is not the same as Cisco's Guest-VLAN feature.

The variant with MAB means that non-capable 802.1x go straight to MAB while 802.1x capable devices that fail to provide valid credential (or successful EAP exchanges) are put in the unauthenticated VLAN. With this in mind, you can clearly see that you can use the captive portal also to remediate misbehaving 802.1x clients (including guests from other 802.1x networks) into a proper config.

So, if configured properly, a registered 802.1x user that is in isolation VLAN would need to be presented with 802.1x instructions (including offering a download of a client) and could be logged.

Modifying the captive portal to support that is trivial but it might not be something that everyone wants so it needs to be considered appropriately.

Tags

802.1x

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

Notes
(0003201) fgaudreault (viewer) 2012-10-19 14:51	Custom use case. Using Inline for that VLAN would work.

Issue History
Date Modified	Username	Field	Change
2010-06-07 17:58	obilodeau	New Issue
2010-06-07 17:58	obilodeau	Status	new => assigned
2010-06-07 17:58	obilodeau	Assigned To	=> obilodeau
2010-06-07 18:00	obilodeau	Tag Attached: 802.1x
2010-11-19 14:25	obilodeau	Target Version	1.10.0 => 2.0.0
2011-01-18 09:30	obilodeau	Target Version	2.0.0 => 2.1.0
2011-03-03 15:16	obilodeau	Target Version	2.1.0 => +1
2011-03-03 15:18	obilodeau	Target Version	+1 => +2
2012-10-19 14:51	fgaudreault	Note Added: 0003201
2012-10-19 14:51	fgaudreault	Status	assigned => resolved
2012-10-19 14:51	fgaudreault	Resolution	open => fixed
2012-10-19 14:51	fgaudreault	Assigned To	obilodeau =>
2012-10-19 14:51	fgaudreault	Target Version	long-term =>