Hi Alain,
> Also, the proxy isn't returning an IP address:
>> Wed Jan 20 10:01:07 2010 : Info: [main_pool] Could not find Pool-Name
>> attribute.
>> Wed Jan 20 10:01:07 2010 : Info: ++[main_pool] returns noop
That log is taken from test for static IP
Here is the log for user who get IP address from pool :
rad_recv: Access-Request packet from host 10.65.8.100 port 65401, id=2,
length=56
User-Name = "tevfikceydeliler"
User-Password = "172932808506"
+- entering group authorize {...}
++[preprocess] returns ok
expand: /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d
-> /var/log/freeradius/radacct/10.65.8.100/detail-20100121
[detail] /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands
to /var/log/freeradius/radacct/10.65.8.100/detail-20100121
expand: %t -> Thu Jan 21 13:39:39 2010
++[detail] returns ok
++[chap] returns noop
++[mschap] returns noop
[suffix] No '@' in User-Name = "tevfikceydeliler", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
[eap] No EAP-Message, not doing EAP
++[eap] returns noop
++[unix] returns notfound
[files] users: Matched entry tevfikceydeliler at line 216
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
++[pap] returns noop
+- entering group pre-proxy {...}
expand: /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d
-> /var/log/freeradius/radacct/10.65.8.100/detail-20100121
[detail] /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands
to /var/log/freeradius/radacct/10.65.8.100/detail-20100121
expand: %t -> Thu Jan 21 13:39:39 2010
++[detail] returns ok
Sending Access-Request of id 236 to 10.1.1.51 port 1812
User-Name = "tevfikceydeliler"
User-Password = "172932808506"
NAS-IP-Address = 10.65.8.100
Proxy-State = 0x32
Proxying request 1 to home server 10.1.1.51 port 1812
Sending Access-Request of id 236 to 10.1.1.51 port 1812
User-Name = "tevfikceydeliler"
User-Password = "172932808506"
NAS-IP-Address = 10.65.8.100
Proxy-State = 0x32
Going to the next request
Waking up in 0.9 seconds.
OK ############################> rad_recv: Access-Accept packet from host
10.1.1.51 port 1812, id=236, length=23
Proxy-State = 0x32
+- entering group post-proxy {...}
[eap] No pre-existing handler found
++[eap] returns noop
Found Auth-Type = Accept
Auth-Type = Accept, accepting the user
+- entering group post-auth {...}
OK ############################>++[main_pool] returns noop
expand: %{NAS-IP-Address} %{NAS-Port} -> 10.65.8.100
OK ############################>[birmas] MD5 on 'key' directive maps to:
b6201c0efddb958ed955eb3c8b0d920a
[birmas] Searching for an entry for key: 'b6201c0efddb958ed955eb3c8b0d920a'
[birmas] Found a stale entry for ip: 172.30.64.95
[birmas] num: 0
rlm_ippool: Allocating ip to key: 'b6201c0efddb958ed955eb3c8b0d920a'
[birmas] num: 1
[birmas] Allocated ip 172.30.64.86 to client key:
b6201c0efddb958ed955eb3c8b0d920a
++[birmas] returns ok
expand: /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d
-> /var/log/freeradius/radacct/10.65.8.100/detail-20100121
[detail] /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands
to /var/log/freeradius/radacct/10.65.8.100/detail-20100121
expand: %t -> Thu Jan 21 13:39:39 2010
++[detail] returns ok
++[exec] returns noop
OK ############################>Sending Access-Accept of id 2 to 10.65.8.100
port 65401
OK ############################> Framed-IP-Address = 172.30.64.86
OK ############################> Framed-IP-Netmask = 255.255.240.0
Finished request 1.
Going to the next request
Waking up in 4.9 seconds.
Cleaning up request 1 ID 2 with timestamp +44
Ready to process requests.
There is no manual about how to set user for static ip address. Mostly
configurations use password. But i use OTP (realm) as password.
What is changed when user moved from pool so static ip?
Tevfik Ceydeliler
Bu elektronik postada bulunan tum fikir ve gorusler ve ekindeki dosyalar sadece
adres sahip/sahiplerine ait olup, Yasar Toplulugu Sirketleri bu mesajin icerigi
ile ilgili olarak hic bir hukuksal sorumlulugu kabul etmez. Eger gonderilmesi
dusunulen kisi veya kurulus degilseniz, lutfen gonderen kisiyi derhal haberdar
ediniz ve mesaji sisteminizden siliniz.The information contained in this e-mail
and any files transmitted with it are intended solely for the use of the
individual or entity to whom they are addressed and Yasar Group Companies do
not accept legal responsibility for the contents. If you are not the intended
recipient, please immediately notify the sender and delete it from your system.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
