Hi,
> it this a bug or it should be like that ( Client-IP-Address same as
> NAS-IP-Address. ) ?
what makes you think they would be different? the client is your
NAS, yes?
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
orion wrote:
...
> the Client-IP-Address is the same as NAS-IP-Address.
So?
> it this a bug or it should be like that ( Client-IP-Address same as
> NAS-IP-Address. ) ?
It's the same as 1.1.7. Yes, it's fine.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/li
grabed the latest and installed.
now it says
rlm_acct_unique: Hashing 'NAS-Port = 9,Client-IP-Address =
192.168.2.225,NAS-IP-Address
= 192.168.2.225,Acct-Session-Id = "8160",User-Name = "orioni"'
rlm_acct_unique: Acct-Unique-Session-ID = "59cf7442060b83a6".
the Client-IP-Address is the same
orion wrote:
> after replacing the rlm_acct_unique.c my debug tells :
>
> rad_recv: Accounting-Request packet from host 192.168.2.225
> ...Client-IP-Address
> now it says "INVALID-TOKEN".
OK. Grab the latest version from CVS. I've fixed a typo.
Alan DeKok.
-
List info/subscribe/unsubscri
after replacing the rlm_acct_unique.c my debug tells :
rad_recv: Accounting-Request packet from host 192.168.2.225 port 1025,
id=94, length=137
Service-Type = Framed-User
Framed-Protocol = PPP
NAS-Port = 48
NAS-Port-Type = Ethernet
User-Name = "user"
orion wrote:
> hi to all.
> im using FR 2.0.0 with default config.
> in debug mode i get
>
> *rlm_acct_unique*: *WARNING*: *Attribute* *Client *-*IP*-*Address* was
> not found in
> request, unique ID MAY be inconsistent
Good point. The way that attribute is handled was changed in 2.0.
I've
so your saying me to put anything that is being sent on that empty slot ?
On 11/01/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> FR 2.0.0 is more fussy - there is no Client-IP-Address in
> the accounting request. therefore it cannot use it in the hash
> (you will see the blank e
Hi,
FR 2.0.0 is more fussy - there is no Client-IP-Address in
the accounting request. therefore it cannot use it in the hash
(you will see the blank entry on the line following 44 (,,)
simply change the rlm_acct_uniq has to use something that IS being sent...eg
Framed-IP-Address
alan
-
List i
here the debug
rad_recv: Accounting-Request packet from host 192.168.2.225 port 1025,
id=89, length=137
Service-Type = Framed-User
Framed-Protocol = PPP
NAS-Port = 44
NAS-Port-Type = Ethernet
User-Name = "user"
Calling-Station-Id = "00:D0:59:D9:13:61
hi to all.
im using FR 2.0.0 with default config.
in debug mode i get
*rlm_acct_unique*: *WARNING*: *Attribute* *Client*-*IP*-*Address* was not
found in
request, unique ID MAY be inconsistent
in 1.1.7 was ok.
My nas is the same ( mikrotik routerboard )
with the same config that was with 1.1.7
-
10 matches
Mail list logo