Concerning the problem of detecting when a client leaves the area, I
wonder if somehow one could use OpenBSD 4.0's new ip roaming
functionality in combination with the new rssi strength values on ath
cards to figure out when client "might* be close to leaving the area?
While on the subject of wireless client roaming with hostapd, do the
Access Points have to be on a wired network for IAPP to work
correctly? Would it be acceptable to deploy a second wireless
interface in each AP (5.8 ghz lets say) and communicate IAPP via
that?( as well as handle back haul to the main AP's) i was thinking of
having the ap's approx 1.5 miles apart so a wired lan solution for
IAPP is not really a option.
with carp is it possible to have a redundant or load balanced hostAP solution?
or
can Trunk(4) load balance the wireless nics in hostap mode?
Thank you for all the feedback it is VERY helpful
Sam Fourman Jr.
Sam Fourman Jr.
On 9/30/06, Joachim Schipper <[EMAIL PROTECTED]> wrote:
On Sat, Sep 30, 2006 at 03:42:38AM -0500, Sam Fourman Jr. wrote:
> I am looking for ways to Authenticate Wireless users(Windows Xp , Mac
> OSX) that connect to a wireless AP (several using OpenBSD's new
> Roaming in hostapd) running OpenBSD 4.0
>
> the way i understand it if I use authpf that requires a user to
> maintain a SSH session.
>
> is there some reasonably secure solution(for an Exclusively OpenBSD
> 4.0 on the back end network) that would maybe allow users to login
> via a web page portal? LDAP RADIUS maybe?
This has been discussed already, over and over; most of that is in the
archives.
A Java SSH applet was considered an acceptable solution last time.
OpenBSD supports several RADIUS servers, but that's just an
authentication backend. The problem is that one should somehow detect
when some client leaves.
Joachim
