[rbak-nsp] Radius Attribute for adding tag to route - RB-Route-Tag

[David Freedman]

Actually, this is probably the case

"We were applying tag 500 and was translated into 892350464."

892350464 = 0x35303000 = ASCII 0x35(5) 0x30(0) 0x30(0) 0x00(NUL)
  

"We¹ve tried using ŒRB-Route-Tag="122"¹ but this results in the Redback
(SE100) applying ŒTag 825373195¹."

825373195 = 0x3132320 = ASCII 0x31(1) 0x32(2) 0x32(2) 0x0(NUL)

Dave.



On 29/11/2011 23:58, "Blake Willis" <blake at ibrowse.com> wrote:

>BTW, the issues you report with seemingly random numbers for the tag value
>sounds to me a lot like a problem of "integer" vs. "string" in your radius
>dictionary for the given attribute.  I recall hitting something like this
>in the past where the box was expecting one & barfed when sent the other,
>&
>I had to turn on debugging both on my radius & on the smartedge in order
>to
>find it.
>
>This is also one of the reasons that I try to use standard attributes
>whenever possible rather than VSAs, as Ericsson isn't the only vendor
>that's shipped documentation with the wrong data type for a VSA...
>
>HTH.  Best of luck.
>
>---
> Blake Willis
> Network Architect
> iBrowse
>
>_______________________________________________
>redback-nsp mailing list
>redback-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/redback-nsp