Using "Tunnel-Private-Group-Id" in linelog

Alan DeKok aland at deployingradius.com
Wed Oct 23 16:02:20 CEST 2019


On Oct 23, 2019, at 9:52 AM, Burger, Wolfgang <wburger at gwdg.de> wrote:
> I´m using FreeRADIUS Version 2.1.12 to dynamically set the VLAN-ID on some switches by client-mac-address.
> 
> Works like a charm.

  That's good.  But you should really use 2.2.10.

> I have to modify the logfiles and would like to use linelog.
> 
> This is my linelog config:

  OK, that should work.

> And this is a Request and Reply for a VLAN-Request:
> ..
> [vlanlog] expand: %S: %{reply:Packet-Type} AAA-VLAN-Request for %{User-Name} on %{NAS-Identifier} (%{NAS-IP-Address}) at Port %{NAS-Port-Id}. -> 2019-10-23 14:27:54: Access-Accept AAA-VLAN-Request for 0cc47a96a6af on Switch31 (192.168.1.141) at Port 41.

  Which is NOT the linelog configuration you posted above.

> I would like to include the information in "Tunnel-Private-Group-Id" into the linelog.
> 
> I´ve tried to add %{reply:Tunnel-Private-Group-Id} to the linelog config.

  The configuration you posted above shows you did tat,

> But the result in vlanlog is:
> 
> 2019-10-23 15:42:53: Access-Accept AAA-VLAN-Request for 0cc47a96a6af on Switch31 (192.168.1.141) at Port 41. Put to VLAN

  <sigh>  Post the debug output from when it doesn't work.  Why post the other debug out, from when you *didn't* add the VLAN information?

  If you want us to help you, you have to post the *relevant* debug output.

> How can i include the information in "Tunnel-Private-Group-Id" of Access-Accept into the linelog logfile?

 Configure it and it should work.  If it doesn't, post the debug output from WHERE IT DOESN'T WORK.

  Alan DeKok.




More information about the Freeradius-Users mailing list