<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY>
Le jeudi 02 décembre 2010 à 07:38 +0100, Alan DeKok a écrit :
<BLOCKQUOTE TYPE=CITE>
<PRE>
Alexandre Chapellon wrote:
> Am not sure to understand... Once the wifi user entered the network
> (level2: no IP yet), I have an entry for its sessions in my accouting
> database, with username, sessionID, maybe mac_address and so on...
Yes. This often includes NAS IP and port.
> But when the user sends a DHCP request to obtain IP address (gain level3
> access), that request may not contain any reference to the username, but
> to the mac address... that's it?
And often the NAS IP and port.
</PRE>
</BLOCKQUOTE>
NAS IP and Port in the DHCP request? That's option 82 isn't it? If my NAS doesn't support relaying DHCP requests adding option 82 fields (my NASes may be very common wifi access points) is it still safe using such a setup?<BR>
Anyway, it's much more clear now thanks.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
> So the trick would be to get the username from the mac address querying
> the accouting database?
Yes.
> And then? Can I use any ippool module in the freeradius DHCP server? or
> Do I have to use static mapping mac2ip?
The ippool module doesn't do allocation for DHCP. But you could write
a short Perl program to do it.
Alan DeKok.
-
List info/subscribe/unsubscribe? See <A HREF="http://www.freeradius.org/list/users.html">http://www.freeradius.org/list/users.html</A>
</PRE>
</BLOCKQUOTE>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
<A HREF="https://www.twitter.com/manainternet">Follow us on: twitter https://www.twitter.com/manainternet</A>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>