Project

General

Profile

Actions
Copy link

Bug #1632

closed

Captive Portal changed behaviour

Added by Davide B almost 14 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Captive Portal
Target version:
-
Start date:
06/30/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:
amd64

Description

Hi,
I've upgraded (maintaining the same configuration) a corporate firewall with a "Transit LAN" with corporate networks and a "Captive LAN" with a DesktopShare (like VNC) PC.

In the 1.2.3 pfsense version a Remote client coming from Transit LAN connects to DesktopShare PC and after authenticate himself with captive portal enabled on "Captive LAN", connect to resources.

In 2.0 version the Remote client cannot connects to DesktopShare PC. The only method to make this connection is to add in "Allowed IP address" a "TO rule" with Remote client IP.

But in this case the DesktopShare Client, after the Remote client control, is able to connect everywhere without captive authentication.

Do you know a workaround?

Actions
Copy link

Also available in: Atom PDF