Re: (ASCEND) radius menus without ascend-menu-item

[basher@alpha.ces.cwru.edu (Tim Basher)]

> Does anyone know if TAOS will accept the standard radius "menu" attribute?

Since there is no such thing a "standard" RADIUS "menu" attribute, I think
it can be said without ambiguity - "no".  I have checked all the "standard"
documents including drafts - rfc2138.txt, rfc2139.txt, draft-ietf-radius-*
and there is no such thing as "menu".  If you think this is incorrect,
please cite a reference to an IETF document.

> Yes, I know about the `Ascend-Menu-Item' attribute, but I need this to
> inter-operate with other access servers, and a propriatary solution is
> unacceptable.

There is no standard method, so you must use one or more proprietary solution.
Keep in mind that you can use both an `Ascend-Menu-Item' and a `Menu' and
whatever else you want - to quote from RFC 2138 - "A RADIUS client MAY
ignore Attributes with an unknown Type."

  DiagUser   Password = "Validate"
        Ascend-Menu-Item = "show ip stats;Display IP Stats",
        Ascend-Menu-Item = "ping 1.2.3.4;Ping server",
        Ascend-Menu-Item = "show arp;Display ARP Table",
        Menu = "whateverformat",
        Menu = "whateverformat",
        Menu = "whateverformat"

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

• Prev by Date: RE: (ASCEND) Monitoring Access Control (RADIUS)
• Next by Date: Re: (ASCEND) Ascend Pipeline 75 with non-fixed remote address
• Prev by thread: (ASCEND) radius menus without ascend-menu-item
• Next by thread: (ASCEND) guesses as to when 6.1.X (where x > 7) coming?
• Index(es):
  • Main
  • Thread