Hi Alan, despite the note in radiusd.conf: ... # It also adds the %{Client-IP-Address} attribute to the request. preprocess ... it looks like that the attribute is not added:
DEBUG rlm_acct_unique: WARNING: Attribute Client-IP-Address was not found in request, unique ID MAY be inconsistent DEBUG
and I do not find it in detail file neither(where I would need it for radrelaying). Apparently the attribute is available since I've written following dummy instance of attr_rewrite module to add the attribute to detail file: ...from modules{}: attr_rewrite add_clientip { attribute = Client-IP-Address searchin = packet searchfor = ".*" replacewith = "%{Client-IP-Address}" new_attribute = yes max_matches = 1 append = no } and in accounting{} I have: ... # add Client-IP-Address (fix) add_clientip # create detail file for radrelay(1.X binary) radrelay-detail I've compiled --without-udpfromto option - not sure whether it might have any impact. Is there something screwed with my config or the Client-IP-Address attribute is really missing? Thanks for reply. Milan Holub holub (at) thenet (dot) ch -------------------------------------- TheNet-Internet Services AG, im Bernertechnopark, Morgenstr. 129 CH-3018, Bern, Switzerland 031 998 4333, Fax 031 998 4330 http://www.thenet.ch http://wlan.thenet.ch --------------------------------------
it looks like that the attribute is not added:
DEBUG rlm_acct_unique: WARNING: Attribute Client-IP-Address was not found in request, unique ID MAY be inconsistent DEBUG
Yep I noticed this too, trying to create unique accounting strings with Client-IP-Address / Packet-Src-IP-Address... Just doesn't work. -- Arran
Arran Cudbard-Bell wrote:
Yep I noticed this too, trying to create unique accounting strings with Client-IP-Address / Packet-Src-IP-Address...
The acct_unique module was written before the whole dynamic expansion was finished. As a result, it's not integrated into the rest of the server. It could be replaced by an accounting "hints" file, as: DEFAULT Acct-Unique-Id = `%{md5:%{foo} %{bar}}` That requires an "md5" handler to be written, which isn't too hard. It should probably be done before 2.0.0, and the "acct_unique" module should be marked as deprecated. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Alan DeKok wrote:
Arran Cudbard-Bell wrote:
Yep I noticed this too, trying to create unique accounting strings with Client-IP-Address / Packet-Src-IP-Address...
The acct_unique module was written before the whole dynamic expansion was finished. As a result, it's not integrated into the rest of the server.
It could be replaced by an accounting "hints" file, as:
DEFAULT Acct-Unique-Id = `%{md5:%{foo} %{bar}}`
That requires an "md5" handler to be written, which isn't too hard.
It should probably be done before 2.0.0, and the "acct_unique" module should be marked as deprecated.
Yes thats a much better way of doing it, then people can hash other arbitrary strings with md5 . Hmm hints, fall-through functionality would still be very useful ;)
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Milan Holub wrote:
despite the note in radiusd.conf: ... # It also adds the %{Client-IP-Address} attribute to the request. preprocess
This no longer happens. That documentation should be removed.
it looks like that the attribute is not added:
DEBUG rlm_acct_unique: WARNING: Attribute Client-IP-Address was not found in request, unique ID MAY be inconsistent DEBUG
That should be updated to use Packet-Src-IP-Address, or Packet-Src-IPv6-Address
and I do not find it in detail file neither(where I would need it for radrelaying).
The detail module should be updated to write src/dst IP's to the detail file, along with src/dst ports. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
On Thu 17 May 2007, Alan DeKok wrote:
Milan Holub wrote:
despite the note in radiusd.conf: ... # It also adds the %{Client-IP-Address} attribute to the request. preprocess
This no longer happens. That documentation should be removed.
it looks like that the attribute is not added:
DEBUG
rlm_acct_unique: WARNING: Attribute Client-IP-Address was not found in request, unique ID MAY be inconsistent
DEBUG
That should be updated to use Packet-Src-IP-Address, or Packet-Src-IPv6-Address
and I do not find it in detail file neither(where I would need it for radrelaying).
The detail module should be updated to write src/dst IP's to the detail file, along with src/dst ports.
Hmm.. Just a reminder to the list that this still seems to be an open issue. -- Peter Nixon http://peternixon.net/
participants (4)
-
Alan DeKok -
Arran Cudbard-Bell -
Milan Holub -
Peter Nixon