Alex Jaliashvili wrote:
> The problem was in using "old" attributes:
> DHCP-Agent-Circuit-Id := "%{request:DHCP-Agent-Circuit-Id}"
> DHCP-Agent-Remote-Id := "%{request:DHCP-Agent-Remote-Id}"
Uh... no. The dictionary.dhcp that is included with 2.1.10 has the
*same* definition for those attribute
equest-List = DHCP-Domain-Name
DHCP-Parameter-Request-List = DHCP-Domain-Name-Server
DHCP-Parameter-Request-List = DHCP-Hostname
DHCP-Agent-Circuit-Id = 0x000401e30420
- Original Message -
From: "Alan DeKok"
To: "FreeRadius users mailing list"
Alex wrote:
> Thanks Alan,
>
> but git pull said that local sources are up to date.
Or... git pull origin v2.1.x:v2.1.x
> dhcp.c has this changes:
> http://github.com/alandekok/freeradius-server/commit/7d44b0a545a50012aaa60ba996cc976d15745d08
Yes, that should be it.
> dictionary.dhcp is fr
Radius users mailing list"
Sent: Tuesday, July 20, 2010 01:54
Subject: Re: DHCP reply with opt82
Alex wrote:
FreeRADIUS Version 2.1.10 (from git sources).
I'm using dhcp feature of freeradius to assign static ips to computers
dynamically.
$ git pull
$ (cd src/lib;make) &&
Alex wrote:
> FreeRADIUS Version 2.1.10 (from git sources).
> I'm using dhcp feature of freeradius to assign static ips to computers
> dynamically.
$ git pull
$ (cd src/lib;make) && (cd src/main;make)
> but both this two values (0x000401e30420 and 0x00060000) are
> assigned to DHCP-Relay-
Hello.
FreeRADIUS Version 2.1.10 (from git sources).
I'm using dhcp feature of freeradius to assign static ips to computers
dynamically.
Sometimes its needed to reply to dhcp packets with same opt82 as in
request. For example, cisco uses opt82 from replied packet to know from
which port request h
6 matches
Mail list logo