Wrong type of Attribute ERX-Inner-Tag-Protocol-Id is octets should be string
Hi! Our Juniper MX does not understand the Attribute ERX-Inner-Tag-Protocol-Id. I put ERX-Inner-Tag-Protocol-Id := 0x88a8 in our Database, but the MX logged: Inner-Vlan-Tag-Protocol-Id (Juniper-ERX-VSA), Err:"Attribute value is invalid" Decoded-val:0(0x0) authd_radius_parse_message: Error parsing common avps Framework - module(radius) return: MALFORMED DATA When I change the type from octets to string it works like a charm: -ATTRIBUTE ERX-Inner-Tag-Protocol-Id 211 octets +ATTRIBUTE ERX-Inner-Tag-Protocol-Id 211 string Their documentation states: hexadecimal string: - range = 0x600 through 0xffff. - 0x8100 = Inner VLAN tag for designated L2BSA subscribers Could you please change the dictionary.erx to use string instead of octets? TIA, Daniel Finger
On Aug 18, 2020, at 8:13 AM, Daniel Finger <daniel.finger@ewetel.de> wrote:
Our Juniper MX does not understand the Attribute ERX-Inner-Tag-Protocol-Id.
I put ERX-Inner-Tag-Protocol-Id := 0x88a8 in our Database, but the MX logged: Inner-Vlan-Tag-Protocol-Id (Juniper-ERX-VSA), Err:"Attribute value is invalid" Decoded-val:0(0x0) authd_radius_parse_message: Error parsing common avps Framework - module(radius) return: MALFORMED DATA
When I change the type from octets to string it works like a charm:
-ATTRIBUTE ERX-Inner-Tag-Protocol-Id 211 octets +ATTRIBUTE ERX-Inner-Tag-Protocol-Id 211 string
Their documentation states:
hexadecimal string: - range = 0x600 through 0xffff. - 0x8100 = Inner VLAN tag for designated L2BSA subscribers
That's pretty dumb, TBH. But whatever.
Could you please change the dictionary.erx to use string instead of octets?
OK. I've pushed a fix. Alan DeKok.
participants (2)
-
Alan DeKok -
Daniel Finger