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

Alan DeKok aland at deployingradius.com
Wed Oct 23 16:40:54 CEST 2019


On Oct 23, 2019, at 10:21 AM, Burger, Wolfgang <wburger at gwdg.de> wrote:
> 
> thank you for your reply and constructive feedback. You´re right, I´ve made a mistake while pasting the outputs together.
> 
> Let me try again please.

  I'm always happy to have people try.

> +- entering group post-auth {...}
> [vlanlog] expand: %{Packet-Type} -> Access-Request
> [vlanlog] expand: %{%{Packet-Type}:-format} -> Access-Request
> [vlanlog] expand: /var/log/freeradius/vlanlog -> /var/log/freeradius/vlanlog

  OK, so it's not expanding %{reply:Tunnel-Private-Group-Id}.  That's odd

> Sending Access-Accept of id 101 to 192.168.1.141 port 1812
> Tunnel-Type:0 = VLAN
> Tunnel-Medium-Type:0 = IEEE-802
> Tunnel-Private-Group-Id:0 = "\0001"

  What's that?  There's no need to add a binary 0x00 in front of the attribute.

  Where is the attribute coming from?  Why not just set

	Tunnel-Private-Group-Id = "1"

 ?

  And TBH, it's 2.1.12.  I can look at debug output, but that's it.  There may be bugs, etc. which cause this problem.  You should upgrade to 2.2.10, which is compatible with the configuration in 2.1.12.  That way you know you have the most recent version, with all of the bug fixes.

  Alan DeKok.




More information about the Freeradius-Users mailing list