Huntgroups with NAS-Port-Id or NAS-Port
Jan Hugo Prins
jhp at jhprins.org
Fri Oct 18 14:25:57 CEST 2019
Hello,
In my huntgroups file I would like to split a switch into 2 different
huntgroups.
I found out this would be possible using the NAS-Port-ID option and then
selecting a range of ports, at least that is what the documentation in
the file states.
Testing this, I thing I see the following:
A client detail record looks like this:
Fri Oct 18 13:59:28 2019
Packet-Type = Access-Request
NAS-IP-Address = 192.168.203.126
Fabric-Attach-Switch-Mode = 2
Attr-26.562.183 = 0x00000000
NAS-Port-Type = Ethernet
NAS-Port-Id = "3/1"
Service-Type = Framed-User
Message-Authenticator = 0x.......................
Called-Station-Id = "A4-25-1B-C9-6C-01"
NAS-Port = 257
Framed-MTU = 1490
User-Name = "av140bbpoe20"
Calling-Station-Id = "00-AA-6E-30-73-69"
State = 0x.............................
EAP-Message = 0x...........................................
Event-Timestamp = "Oct 18 2019 13:59:28 CEST"
Huntgroup-Name = "ers5900core"
Timestamp = 1571399968
As you can see:
the NAS-Port-Id looks like a Cisco port number with blade/port.
the NAS-Port looks like the number of the port in the stack.
When I try to put NAS-Port in the huntgroup name I can't seem to define
a range, and if I use the NAS-Port-Id and put the number values of
NAS-Port in it as a range it is not recognized. If I put the value "3/1"
in the huntgroup definition it seems to work, but then I have to create
192 huntgroup lines.
What is the correct solution to fix this?
Thanks,
Jan Hugo Prins
More information about the Freeradius-Users
mailing list