0000332: Wifi and connections to wrong SSID - PacketFence

(0000738)
user4
2008-06-13 14:48

Reminder sent to: maikel

(0001747)
obilodeau (reporter)
2010-11-02 14:47

Just found out about that issue. What was the plan here?

A special remediation page?

(0001750)
maikel (reporter)
2010-11-02 15:55

Think thats the best idea.

If a user connects to the open registration network/guestnetwork, but has access to a protected site. use redir.cgi to inform the user that his/her network is setup in correctly and show the correct network SSID to connect to.

(0001751)
obilodeau (reporter)
2010-11-02 16:17

A lot of new information about the node is available in trunk. Including the SSID. This will allow to very easily do this kind of stuff with the captive portal.

Re-targeting for 1.10.0 as a consequence to avoid duplicated effort.

(0001811)
obilodeau (reporter)
2011-01-18 09:38

This is now possible with latest release.

Several ways it can be accomplished but pulling this out of my head:
- modify pf::vlan::custom to return a specific VLAN based on SSID (with specific subnet info)
- modify redir.cgi to present a special page if a user hits it with an IP in the specific above range

If you want it to be easier, please re-open another feature ticket with what pieces are missing to make it easier.

Issue History
Date Modified	Username	Field	Change
2008-06-13 14:48	user4	New Issue
2008-06-13 14:48	user4	Note Added: 0000738
2008-10-31 14:27	user4	Category	=> 1.8.1
2009-02-02 16:01	user4	Category	1.8.1 => 1.8.2
2009-02-16 16:25	user4	Project	PacketFence => PacketFence 1.9
2010-04-15 17:43	obilodeau	Project	PacketFence 1.9 => PacketFence
2010-11-02 14:47	obilodeau	Note Added: 0001747
2010-11-02 15:55	maikel	Note Added: 0001750
2010-11-02 16:17	obilodeau	Note Added: 0001751
2010-11-02 16:17	obilodeau	Reporter	user4 => maikel
2010-11-02 16:17	obilodeau	Category	=> captive portal
2010-11-02 16:17	obilodeau	Target Version	=> 1.10.0
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-01-18 09:38	obilodeau	Note Added: 0001811
2011-01-18 09:38	obilodeau	Status	new => resolved
2011-01-18 09:38	obilodeau	Fixed in Version	=> 2.0.0
2011-01-18 09:38	obilodeau	Resolution	open => fixed
2011-01-18 09:38	obilodeau	Assigned To	=> obilodeau
2011-01-26 15:42	obilodeau	Status	resolved => closed

Notes
(0000738) user4 2008-06-13 14:48	Reminder sent to: maikel

(0001747) obilodeau (reporter) 2010-11-02 14:47	Just found out about that issue. What was the plan here? A special remediation page?

(0001750) maikel (reporter) 2010-11-02 15:55	Think thats the best idea. If a user connects to the open registration network/guestnetwork, but has access to a protected site. use redir.cgi to inform the user that his/her network is setup in correctly and show the correct network SSID to connect to.

(0001751) obilodeau (reporter) 2010-11-02 16:17	A lot of new information about the node is available in trunk. Including the SSID. This will allow to very easily do this kind of stuff with the captive portal. Re-targeting for 1.10.0 as a consequence to avoid duplicated effort.

(0001811) obilodeau (reporter) 2011-01-18 09:38	This is now possible with latest release. Several ways it can be accomplished but pulling this out of my head: - modify pf::vlan::custom to return a specific VLAN based on SSID (with specific subnet info) - modify redir.cgi to present a special page if a user hits it with an IP in the specific above range If you want it to be easier, please re-open another feature ticket with what pieces are missing to make it easier.

Relationships