Mailing List Archive

XOS - TACACS bug
hello,

this is an example to XOS tacacs request to tacacs server:

08/09/2010 12:33:41.85 <Info:AAA.TACACS.authReqSent>
Slot-1: Sent authentication request for mmarkowski connecting
from ::ffff:91.195.1 to Tacacs server 10.100.15.234.


well, from i corrupted, the IP is in fact 91.195.135.101, however as max
characters in IPv4 is 15, this had been kept when IPv6 support was added.
There is a problem then in creation of access lists defining command for
individual for particular switches.


Anyone able to report it as a BUG ?
Or maybe some workaround to disable IPv6 format of "from" field ?

Regards,
Marcin
_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp
Re: XOS - TACACS bug [ In reply to ]
Hello there,

Are you able to share the XOS version you are using?

<-- From a EXOS 12.2.2.11
08/11/2010 22:02:38.36 <Info:AAA.TACACS.authReqSent> Sent authentication
request for user connecting from ::ffff:203.208. to Tacacs server 203.208.*
[snip]*.*[snip]*.


On Wed, Aug 11, 2010 at 9:40 PM, Marcin Kuczera <marcin@leon.pl> wrote:

> hello,
>
> this is an example to XOS tacacs request to tacacs server:
>
> 08/09/2010 12:33:41.85 <Info:AAA.TACACS.authReqSent>
> Slot-1: Sent authentication request for mmarkowski connecting
> from ::ffff:91.195.1 to Tacacs server 10.100.15.234.
>
>
> well, from i corrupted, the IP is in fact 91.195.135.101, however as max
> characters in IPv4 is 15, this had been kept when IPv6 support was added.
> There is a problem then in creation of access lists defining command for
> individual for particular switches.
>
>
> Anyone able to report it as a BUG ?
> Or maybe some workaround to disable IPv6 format of "from" field ?
>
> Regards,
> Marcin
> _______________________________________________
> extreme-nsp mailing list
> extreme-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/extreme-nsp
>