Bug #3352: CaptivePortal: new device/different user getting an authorised already IP cannot be authenticated - pfSense - pfSense bugtracker

Actions

Copy link

Bug #3352

closed

CaptivePortal: new device/different user getting an authorised already IP cannot be authenticated

Added by Luigi Capriotti about 11 years ago. Updated over 9 years ago.

Status:

Rejected

Priority:

Normal

Assignee:

Category:

Captive Portal

Target version:

Start date:

12/05/2013

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.1

Affected Architecture:

All

Description

When the DHCP lease time is shorter than the idle/hard timeout of the captive portal the following situation may happen:

- a device with IP 192.168.1.115 gets authorised and related CP entry is created
- the DHCP lease expires, the CP entry associated to 192.168.1.115 is still within its validity
- another device/user connects and gets IP 192.168.1.115
- the user tries to authenticate to the CP, login is successful but CP does not authorises the new MAC but rather refresh the existing CP entry associated to the previous user:

CONCURRENT LOGIN - REUSING IP 192.168.1.115 WITH DIFFERENT MAC ADDRESS 84.xx.xx.xx.xx.55:user1,84.xx.xx.xx.xx.55,192.168.1.115

- if that CP entry is manually deleted the second device/user is successfully associated with its MAC/username and CP authorises the device.

Attached a screenshot with the log entries for the specific example

Files

2013-12-05 12_12_47-Doc1.docx [Compatibility Mode] - Word.png (55.4 KB) 2013-12-05 12_12_47-Doc1.docx [Compatibility Mode] - Word.png

test case screenshot

Luigi Capriotti, 12/05/2013 08:58 AM